ipl-logo

Agile Project Scope Creep

1150 Words5 Pages

Today we know that using an Agile Method is not for every type of project. For projects where change is not so frequent, a traditional model maybe more useful. But where projects are expected to face a lot of change, i.e. scope creep, an Agile Method would be more of an appropriate option. There is nothing we can do to control or stop the requirements from changing. This is why planning and allowing time to make changes for these specific requirements in a project is critical. Now a days, the scope of a project will always change and this should be viewed as a positive aspect towards the project as it will add business value and increase customer satisfaction.
The only difference in how we react to scope creep in Agile is how the change …show more content…

The tasks that are due are made very clear by the product owner at the planning meeting. This may help reduce risk in scope creep as sprints include daily stand up meetings. Stand up meetings give team members the chance to discuss any obstacles or challenges they have faced. During these meetings the project manager or scrum master can interfere to make changes to the sprint. This allows changes to be made to the scope and be implemented rapidly before it is too late. It also saves time in the long run as change requirements can be prioritized immediately with little delay as possible. There are four main aspects to Sprints which are: Sprint planning, Daily stand-up meetings, Sprint Demo, Sprint Retrospective. (Atlassian …show more content…

Some teams will complete it directly after the Sprint Demo. The retrospective can last up to an hour which provides sufficient amount of time for review. This meeting is also used to appraise performance and make plans for making adaptions if required. A simple and practical method of handling a retrospective would be to plan a start-stop-continue meeting. (MountainGateSoftware) There are many ways in conducting a retrospective meeting but this method basically involves team members identifying what they should start, stop or continue to do. At the end of this Retrospective meeting teams will vote on particular aspects in which they believe would be best to focus on in the upcoming

More about Agile Project Scope Creep

Open Document