Change is good

Two words project managers do not like to hear are scope creep. However, for project managers working with the agile methodology, it does not have to be that scary. This article explores how agile project managers can relieve the fear of scope creep. Because the agile approach is iterative, the next move--an iteration, or "sprint," as it is called in the agile methodology known as Scrum--is decided. Three key opportunities for the agile project team to address scope creep are presented. Every iteration in agile adds more clarity to the project's scope; changing the scope does not mean more is added to the scope. The article discusses how an insurance and banking business handles iterations. The team meets to discuss the entire backlog of work requests including change requirements. Changes in scope are monitored continuously. Whether a project manager is working with traditional or agile project management techniques, scope creep may need to be controlled. A sidebar on scope creep accompanies this article.
registered user content locked

Log in or join PMI to gain access

or Register

Advertisement

Advertisement

Related Content

Advertisement

Publishing or acceptance of an advertisement is neither a guarantee nor endorsement of the advertiser's product or service. View advertising policy.