It is a known fact that sometimes we need to change from Waterfall to Agile, in particular Scrum, while the project is moving.
In this case, we basically need to be sure that we comply just a few of elements:
This is quite simple, agree? Please find some details in this article here.
2 Comments
6/21/2016 09:59:35 am
"It is a known fact that sometimes we need to change from Waterfall to Agile," true - but I would also suggest that the most important question to understand is why. Sometimes agile is seen as this magical silver bullet that will rescue a doomed project whereas there are some more fundamental problems that need to be addressed along with project methodology.
John Warrick
1/9/2017 12:54:39 pm
Scrum can be used to work through the tasks in the Integrated Master Schedule that was created to track the execution of the waterfall project. The pert view of the IMS can be used to create the product backlog. If the IMS is a resource loaded schedule, the Product Backlog created from the IMS task list will carry over resource and duration estimates. The Scrum weekly planning meeting can be used to validate IMS legacy estimates and reaffirm the commitment of the task assignee to execute within previously established estimates. Alternately, this can also be an opportunity to challenge the assumptions defining the tasks and redefine/clarify budgets, scope, closure criteria, etc... Leave a Reply. |
|
|