Choosing a Project Approach for Salesforce
Salesforce programmes succeed or fail less because of the methodology chosen and more because of how accountability, decision-making, and risk are structured around that methodology.
For CIOs and programme sponsors, the choice of project approach is not a delivery preference. It is a governance decision that shapes commercial exposure, delivery confidence, and the organisation’s ability to intervene when things start to drift.
This article explores why the project approach matters in Salesforce programmes and how sponsors can avoid common traps that arise when methodology is selected without sufficient regard for risk, organisational maturity, and delivery reality.
Why project approach matters more than methodology
Salesforce implementations are often described as fast-moving and configurable, which can create a false sense of simplicity. In practice, they are complex software programmes involving multiple teams, vendors, integrations, data migration, security considerations, and organisational change.
When delivery issues emerge, they are rarely caused by choosing Agile, Waterfall, or any other named approach. They arise when the chosen model does not provide sufficient structure for:
Common failure patterns in Salesforce delivery models
Several patterns recur across Salesforce programmes where the project approach is poorly matched to the situation.
In some cases, Agile delivery models are adopted to accelerate progress, but without the governance, role clarity, or backlog discipline required to manage complex dependencies. This can lead to incremental delivery without strategic direction, late discovery of integration or data issues, and erosion of sponsor confidence.
In other cases, highly structured plans are created, but assumptions are locked in too early. When reality diverges from the plan, change becomes expensive and politically difficult, even when adjustment would clearly improve outcomes.
Problems also arise when multiple delivery partners or internal teams operate under different approaches. Misaligned cadences, reporting, and decision forums increase coordination overhead and obscure true progress and risk.
Matching approach to risk and organisational maturity
There is no single project approach that suits all Salesforce programmes. What matters is whether the approach chosen reflects:
Governance is the real differentiator
Regardless of the delivery model selected, Salesforce programmes require the same underlying disciplines found in well-run software initiatives.
These include clear sponsorship, defined decision rights, rigorous planning, realistic estimation, and active risk management. Where these are absent, no methodology will compensate.
Where they are present, different delivery approaches can work effectively, provided they are applied consistently and supported by appropriate oversight.
Bringing it together
Choosing a project approach for Salesforce is not about selecting the right framework. It is about creating the conditions for informed decision-making, controlled change, and sustained delivery confidence.
When project approaches fail, it is usually because governance is weak, incentives are misaligned, or early assumptions are left unchallenged.
Decisions about delivery models, roles, and controls are commonly clarified through independent Salesforce Project Assurance, where delivery risk, governance effectiveness, and organisational readiness are reviewed together before problems become embedded.
For CIOs and programme sponsors, the choice of project approach is not a delivery preference. It is a governance decision that shapes commercial exposure, delivery confidence, and the organisation’s ability to intervene when things start to drift.
This article explores why the project approach matters in Salesforce programmes and how sponsors can avoid common traps that arise when methodology is selected without sufficient regard for risk, organisational maturity, and delivery reality.
Why project approach matters more than methodology
Salesforce implementations are often described as fast-moving and configurable, which can create a false sense of simplicity. In practice, they are complex software programmes involving multiple teams, vendors, integrations, data migration, security considerations, and organisational change.
When delivery issues emerge, they are rarely caused by choosing Agile, Waterfall, or any other named approach. They arise when the chosen model does not provide sufficient structure for:
- Clear ownership of outcomes
- Timely and informed decision-making
- Management of interdependencies and constraints
- Control of scope, cost, and delivery risk
Common failure patterns in Salesforce delivery models
Several patterns recur across Salesforce programmes where the project approach is poorly matched to the situation.
In some cases, Agile delivery models are adopted to accelerate progress, but without the governance, role clarity, or backlog discipline required to manage complex dependencies. This can lead to incremental delivery without strategic direction, late discovery of integration or data issues, and erosion of sponsor confidence.
In other cases, highly structured plans are created, but assumptions are locked in too early. When reality diverges from the plan, change becomes expensive and politically difficult, even when adjustment would clearly improve outcomes.
Problems also arise when multiple delivery partners or internal teams operate under different approaches. Misaligned cadences, reporting, and decision forums increase coordination overhead and obscure true progress and risk.
Matching approach to risk and organisational maturity
There is no single project approach that suits all Salesforce programmes. What matters is whether the approach chosen reflects:
- The scale and complexity of the solution
- The number of vendors and internal teams involved
- The organisation’s experience with Salesforce delivery
- The tolerance for change, experimentation, and rework
- The commercial and regulatory constraints in play
Governance is the real differentiator
Regardless of the delivery model selected, Salesforce programmes require the same underlying disciplines found in well-run software initiatives.
These include clear sponsorship, defined decision rights, rigorous planning, realistic estimation, and active risk management. Where these are absent, no methodology will compensate.
Where they are present, different delivery approaches can work effectively, provided they are applied consistently and supported by appropriate oversight.
Bringing it together
Choosing a project approach for Salesforce is not about selecting the right framework. It is about creating the conditions for informed decision-making, controlled change, and sustained delivery confidence.
When project approaches fail, it is usually because governance is weak, incentives are misaligned, or early assumptions are left unchallenged.
Decisions about delivery models, roles, and controls are commonly clarified through independent Salesforce Project Assurance, where delivery risk, governance effectiveness, and organisational readiness are reviewed together before problems become embedded.