The FLOW view in Disciplined Agile does not mean that there are no starts and stops in any DA project. Rather, it emphasizes optimizing the flow of work through the system by minimizing delays, reducing bottlenecks, and removing unnecessary handoffs. However, starts and stops may still exist due to various factors such as dependencies, changing priorities, or external constraints.

Theteam leadisnot responsible for securing fundingfor the team. In a Disciplined Agile framework, funding responsibilities typically fall under the purview of management or a sponsor. The team lead focuses on enabling the team, removing impediments, facilitating collaboration, and coaching the team toward effective delivery practices.

References:

PMI’s Disciplined Agile Senior Scrum Master (DASSM) curriculum materials.

"Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)", PMI.

Disciplined Agile (DA) milestones are based on Lean governance principles. Lean governance emphasizes lightweight control mechanisms and focuses on achieving desired outcomes rather than enforcing compliance through heavy documentation or bureaucratic processes. DA milestones are established to ensure that value is being delivered efficiently and effectively throughout the lifecycle, with decisions made based on evidence and validated learning rather than detailed documentation (A) or strict adherence to lifecycle stages (D). While continuous integration (C) can support Lean governance by providing frequent, actionable insights into product development, it is not the foundation upon which DA milestones are based.

The purpose of an iteration retrospective in Disciplined Agile (DA) is to reflect on the recent iteration and identify areas of improvement, successes, and challenges. The retrospective allows the team to transfer knowledge, insights, and process improvements to subsequent iterations, fostering continuous improvement. This helps the team become more effective and efficient over time.

Option B relates to a daily stand-up, Option C involves iteration planning, and Option D pertains to an iteration review or demo, not a retrospective.

References:

PMI’s Disciplined Agile Senior Scrum Master (DASSM) curriculum materials.

"Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)", PMI.

"Ensure production readiness" is one of the process goals in the transition stage of the Disciplined Agile (DA) framework. During the transition phase, the team focuses on finalizing the product and preparing it for release, which includes activities like final testing, user training, and deployment planning to ensure the solution is ready for production use. Options A (Produce a potentially consumable solution) and B (Develop common vision) are more aligned with earlier phases, such as Inception or Construction. Option D (Address risk) is a goal throughout the lifecycle but is not specific to the transition phase.

True: On an Agile team, the Product Owner is the go-to person for business domain information. The Product Owner is responsible for defining the product vision, managing the product backlog, and acting as the primary liaison between the development team and stakeholders. They provide clarity on business requirements, priorities, and customer needs, ensuring that the team understands what is needed to deliver value. The Product Owner's deep knowledge of the business domain makes them the authoritative source for business-related questions and guidance.

The primary advantage of working in an Agile team, according to the PMI Disciplined Agile framework, is the ability to quickly adapt to changing customer needs (Option C). Agile teams emphasize flexibility, responsiveness, and continuous improvement, enabling them to respond effectively to feedback and evolving requirements. Options A, B, and D do not reflect the core value proposition of Agile. While agile teams may aim for timely delivery, specialization, andreduced customer intervention, their core strength lies in adaptability and responsiveness to change, ensuring that the product remains aligned with customer needs.

Top of Form

Bottom of Form