Timeline for How to track impact on planning due to scope changes?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 20, 2017 at 0:06 | comment | added | Alan Larimer | When executing with an agile mind set, change is welcome. Therefore any "change management process" should be lean (lightweight). Frameworks and processes that adhere to the agile values and principles do not have fixed long-term plans. Thus changes can have less impact, promoting competitive advantage. | |
| Jun 30, 2014 at 11:06 | comment | added | MCW | Every change should be examined by relevant stakeholders to assess the impact on cost/scope/schedule. Changes that affect the project delivery should be explicitly and formally approved. | |
| Jun 28, 2014 at 15:42 | comment | added | Marv Mills | Literally the best possible answer to this seminal question I could conceive. Shame I can only +1 it! | |
| Jun 28, 2014 at 10:36 | history | answered | David Espina | CC BY-SA 3.0 |