By Eugene le Roux, FSAIRAC, and Eamonn Ryan
Project management, by its very nature, is a complex endeavor fraught with potential pitfalls. This is Part 4 of a four-part series.
A developed system is delivered late, incurring penalties. Image by Rawpixel/Freepik.com
- The problem: A developed system is delivered late, incurring penalties. The contractor argues that every mandatory design review led to the client adding additional requirements, effectively “shifting the goalposts.”
- Analysis: This is the quintessential example of scope creep, a common project management malady that erodes timelines, budgets, and morale.
- Root cause: Often originates from an inadequately defined initial project scope, a lack of formal change control, or a client’s evolving understanding of their needs without appreciating the impact on the project. The contractor may also be at fault for not diligently enforcing change control.
- Diffusion strategy: The most effective defense against scope creep is a rigorous Change Control Process, formally agreed upon and strictly adhered to by both parties from day one:
- Detailed statement of work (SOW): The initial SOW must be as detailed and unambiguous as possible, clearly defining what is in scope and, crucially, what is out of scope.
- Formal change request (CR) mechanism: Any new requirement, no matter how small, must be submitted as a formal change request.
- Impact analysis: For every CR, the contractor must conduct a thorough impact analysis, detailing the effects on:
- Scope: What new features or tasks are added.
- Schedule: How the timeline will be extended.
- Cost: Any additional expenses incurred.
- Resources: Any new resources required.
- Client approval and re-baselining: The impact analysis is presented to the client. The client must formally approve the CR, understanding and accepting the associated changes to schedule and cost. The project baseline (scope, schedule, budget) is then formally re-baselined to reflect the approved changes.
- Project manager’s role: The project manager must be assertive in enforcing this process, educating the client on the implications of changes, and ensuring no “informal” additions are accepted.
Without a disciplined change control process, projects are almost guaranteed to suffer from delays and budget overruns, leading to disputes over penalties.
Conclusion: foundations for project success
These problematic situations, while diverse, share common threads: the critical need for clear, unambiguous contracts and Statements of Work; robust, well-defined processes; transparent and continuous communication; and strong, accountable leadership. By proactively addressing these foundational elements, project stakeholders can transform potential conflicts into opportunities for collaboration, ensuring projects are delivered successfully, on time, and within budget, fostering long-term, trusting relationships.
