Solution increments are created during the Evolutionary Development phase. This phase is where the solution is developed iteratively, building on the firm foundations laid out in the previous phases1. It involves creating increments of the product through time-boxed iterations, ensuring that the solution evolves in line with the project's objectives and business needs.

* Active Listening: The change curve requires empathetic and effective communication to understand concerns, address resistance, and guide individuals through emotional responses to change. Active listening is a vital skill in this process.
* Other Options:
* Time management: Important but not specific to the emotional aspects of change.
* Negotiation: Relevant for resolving conflicts but secondary to listening during change.
* Decision-making: Necessary for leadership but not for guiding individuals emotionally.
Key AgilePM Concepts Referenced:
* Engagement and Support: AgilePM Handbook, Chapter 6, Section 6.4.

This wording aligns with Scrum. Scrum explicitly defines a small set of events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective) and artifacts (Product Backlog, Sprint Backlog, Increment) that are interconnected and each serve a clear purpose. Scrum theory emphasizes empiricism supported by three pillars-transparency, inspection, and adaptation-often likened to a three-legged stool: remove a leg and the system becomes unstable. Likewise, removing or watering down any Scrum event or artifact reduces transparency and weakens inspection/adaptation, undermining outcomes. AgilePM has products/roles/phases rather than this specific "events + artifacts" construct, and "all Agile approaches" is too broad. Therefore, the missing framework is Scrum.

The stated benefits of using DSDM include the business being better able to direct development, the reduced risk of building the wrong solution, and a smoother deployment process2. These benefits stem from DSDM's iterative approach and close collaboration with stakeholders2.

Business roles are critical in a DSDM project as they guide the evolution of the solution at a detailed level6.
They provide day-to-day business direction and ensure that the solution being developed aligns with the business needs and objectives.