Avoiding 5 Common Salesforce Project Pitfalls
Anyone who has worked on a big project knows that there will be issues. In my experience, many of them can be avoided by using a standardized process from discovery to roll-out. Whether you’re rolling out a Sales Cloud implementation for 10 users or designing a custom application that will be used by thousands of people, following a proper implementation process is critical to success. By understanding the goals and needs of your project and setting proper expectations and deadlines, we can ensure project success by utilizing a simple project framework. In this blog post, we will discuss some of the common project pitfalls and how they can be avoided.
Scope Creep: Scope creep is changing a project’s definition and required outcomes while development is occurring. This is the #1 cause of missed deadlines and cost overruns and it’s a result of improper discovery sessions. It takes an experienced and knowledgeable architect to work with a business to discover all of the needs of a project before development begins.
Poor Communication: My team has daily touch points to discuss what was worked on the previous day and what is being worked on for the day. This keeps the project team up to date internally so that the project lead can make sure the customer is kept updated on progress and issues that have popped up. There is too often a disconnect between the developers and the customer. While it can often save costs to work directly with a developer, it is useful to use a consulting firm that has the resources to manage, direct, and execute a project’s needs.
Internal Bureaucracy: Before starting a project, determine who the decision maker is and give him control. Someone needs executive decision making capabilities in order to keep a project moving forward. This isn’t to say that this person will make all the decisions himself and not ask for input from the necessary business users, but it’s vital that someone be the final decision maker. Every department is going to have disconnected business priorities, so it is important to make sure that someone gets the final say.
Lack of Timely QA and Verification: Rolling out prototypes frequently for review is key to ongoing QA and needs verification. By creating multiple revisions and testing each of them in a timely manner, we can ensure that nothing is missed.
Not Planning for Issues: In a perfect world, a project will go off without a hitch. Unfortunately, this is not a perfect world. Inevitably, there will be problems. Planning extra time for these issues is key to meeting deadlines.
As you can see, these common issues fall on both the business, and the partner. By utilizing a Salesforce partner like Hackd, you can help your business avoid these pitfalls and help guide your project to success.
Chris Starleaf - Business Analyst