Choosing a Project Approach for Salesforce

Implementing Salesforce solutions is a complex undertaking that requires a blend of information technology and business skills. The endeavour's success hinges on coordinating highly skilled people to perform critical tasks in the correct order to achieve the project outcomes. The project's planning, resource engagement, and risk mitigation are all contingent on the project manager's experience and expertise and the sponsor's ability to set the direction and overcome obstacles. Without the requisite experience, the project plan will lack a good foundation, potentially leading to time and cost overruns, ultimately failing to deliver the intended benefits.

​Each project is unique, and delays can be caused by many things, from poor planning and inaccurate estimates to ineffective task execution and resource conflicts. Many Salesforce projects avoid the traditional waterfall planning approach because the project appears to take too long. Instead, some organisations take an agile approach to deliver working Salesforce solutions faster. Both methodologies have their strengths and weaknesses, but they will only work if they are set up and managed correctly.

The Critical Chain approach, rooted in constraints theory, is valuable in project environments. It focuses on identifying and eliminating obstacles and limitations that impede project progress. This methodology, developed by Eliyahu Goldratt (refer to 'Theory of Constraint'), requires the same planning rigour as waterfall projects. However, it differentiates itself from the waterfall approach by employing buffers to safeguard the critical path. While the Critical Chain approach offers similar vigour as the agile methodology, it mitigates the confusion that you often find on larger agile projects.

There isn't a one-method-fits-all project approach for Salesforce projects; any of the three approaches discussed can work well for a Salesforce implementation. It is crucial to consider which methodology the project team is most comfortable and experienced with. If working with other project teams and third parties, agree to use the same methodology to avoid the added overhead and risks of working with multiple methods.

Do not let jargon like 'out-of-the-box' features, custom configurations and declarative tools like Flow Builder lure you into thinking that implementing Salesforce is easy. In fact, due to the vast array of features and configuration options available in the Salesforce platform, your project team will need the rigour and discipline of traditional software projects to implement Salesforce solutions as specified, on time and within budget. Ensure the approach is applied correctly and governed by whichever project methodology you choose.

To find out more about delivering Salesforce projects effectively and with fewer risks, contact us at Caleidoscope Associates.