Too often, projects start without clearly knowing the work required. Even high-level requirements are not enough to gauge the depth and complexities of most projects. Low-level requirements bring more clarity, but experience has shown that it is often not enough. Also, the longer the project, the more likely requirements will change to match changing business needs. So, how do you ensure projects are completed on time and within budget?
According to Project Management Body of Knowledge, scope management includes the processes to ensure projects include all the work required, and only the work required, to complete the project successfully.
Traditional project methodology forces the definition of the project scope to determine cost and schedule. With so many unknowns, this becomes a challenge and is based on experience and rough-guess estimates. As the project progresses, new requirements arise and existing requirements become clearer.
Agile methodology eliminates unknowns by starting with a fixed cost and schedule, allowing for flexibility of scope based on the client priorities. Clients (internal or external) re- evaluate requirements and priorities with every incrementally delivery.
Requirements can be changed, removed and added as long as the work remains within the mutually agreed cost and schedule. This becomes a win-win for both the client and the project team. The project team gets early feedback on deliverables, and wasted time on unwanted features is eliminated. This client involvement ensures project deliverables contain requirements that provide the most value.
Agile is able to provide customer-driven scope and value-driven deliverables, resulting in positive ROI in a constantly changing environment.
How is Agile changing your projects?
Pingback: links for 2010-01-07