Disciplined Agile

Address Changing Stakeholder Needs

This Construction process goal describes our approach to managing requirements changes. Changes may include new functionality, modifications to existing functionality, or potential defects in existing functionality. To be effective, we need to consider several important questions:

  • How will we work with stakeholders?
  • How will our team elicit feedback from stakeholders?
  • How will we explore the problem space? 
2021 Project Management Institute Address Changing Stakeholder Needs v5.2 Stakeholder Interaction With Team Active stakeholder participation On-site customer Indirectly via product owner Indirectly via business analyst Indirectly via product manager Indirectly via digital means Change control board (CCB) Elicit Requirements All-hands demos Interviews Iteration demos Just-in-time (JIT) model storming Look-ahead modeling/backlog refinement On-demand demos Explore Stakeholder Needs Active stakeholder participation/on-site customer Agile Modeling session/big room planning Behavior-driven development (BDD) Definition of ready (DoR) Design sprint (User experience (UX)) Detailed requirements specification High-level requirements specification Just-in-time (JIT) model storming Look-ahead modeling/backlog refinement Split (A/B) testing

Figure 1. The Address Changing Stakeholder Needs process goal diagram (click to enlarge)

More Information

Choose Your WoW!

The strategies/practices referenced in the goal diagram above are described, including the trade-offs involved and considerations for when (not) to apply them, in the book Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working.

If you want to succeed at enterprise agile you need choices, not prescriptions.