Agile Method In Project Management

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…
Your authorities should document the new scope and any requirements needed to implement the change. Your authorities will need some type of approval. No organisation or project manager will approach these authorities in the same way. Change usually impacts traditional models at a more severe level, so in projects where change is quite high an Agile method may be more suitable.
When scope change is occurring in Agile projects, management should take extreme care and caution in order to secure business value and profits. Legitimate training, instructions, supervision and ensuring team members are obeying and cooperating with the new changes is key to reducing risk. Today it is not just a matter of fixing the scope it is about project manager and team leaders implementing the scope properly, work efficiently and effectively with the project sponsors to settle trade-offs to the project constraints. Agile helps team members work practically and guide them in their change management process.
…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 Method In Project Management

Open Document