Question
Clearly sourced
Expert knowledge for digital decisions
How to Handle Change Requests in Projects
Short answer
Do not decide individually, but collect. Each request goes on a visible list with estimated effort. Regularly – about every two weeks – prioritize: What gets added, what gets removed, what is on hold. This keeps the framework intact without losing good ideas.
Why Individual Decisions Fail
Each request sounds reasonable and small on its own. Ten small requests are half a project. If each is evaluated individually, one ends up saying yes ten times and wonders about the costs.
The Procedure
- Put everything on a list. No request is rejected; all are noted.
- Estimate effort roughly. Small, medium, large is sufficient.
- Prioritize every two weeks. Together, in fifteen minutes.
- When something comes in, something goes out – or the framework is consciously expanded. Both are fine, just not unnoticed.
The Most Important Sentence
"Yes, we will include that – what should it exchange for?"
This turns a demand into a trade-off. Almost always, it turns out that the new request is less important than what would have to be dropped for it.
What Belongs on the List but Rarely Gets Added
Feedback from tests. They are more valuable than any pre-considered requirement because they come from actual use – and they disappear if only expressed verbally.
Key facts
- Principle
- Collect and prioritize instead of deciding individually
- Rhythm
- Every two weeks, fifteen minutes
- Key Question
- What should it exchange for?