The Product backlog is the artifact that collects all the work flowing to the team. It contains a prioritized list of user stories, tasks, enhancements, bug fixes, and other work items that represent the overall scope of the product development effort. The Product Owner manages the backlog, ensuring it is continuously refined and updated to reflect changing priorities and requirements. The iteration backlog (option B) is a subset of the product backlog items that the team commits to delivering in a single iteration, while the business backlog and release roadmap are not typically used to collect all work items for a team.

If a team completes the work in their iteration backlog earlier than expected, the best course of action is to work with the product owner to pull more work from the product backlog into their iteration backlog. This approach keeps the team productive and focused on delivering value, rather than waiting or working on non-critical tasks. Option A suggests working on non-critical tasks, which does not maximize value delivery. Option B (waiting for other groups) is not a productive use of time. Option D (reporting differences in completion time) is helpful for future planning but does not address the immediate need to keep the team engaged.

In the Disciplined Agile framework, a "process blade" represents an organizational capability that addresses a specific need or problem within an organization. Process blades provide guidance on how to effectively implement a particular capability (such as finance, governance, or portfolio management) in a context-sensitive manner. They are not meetings (Option A), specific goals or visions (Option C), or cross-functional teams (Option D); instead, they are resources or guidelines that help the organization improve its processes and capabilities.

Top of Form

Bottom of Form

The principle of pragmatism in Disciplined Agile does not mean that the team will always do what the customer wants. Instead, it means that the team will make practical decisions based on the specific context, constraints, and overall business goals. The team may sometimes need to challenge or refine customer requirements to ensure that the solutions provided are feasible, valuable, and sustainable.

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.

In the context of Disciplined Agile (DA), an Epic is a large user story that represents a significant piece of work that usually requires substantial effort and may span multiple iterations or sprints to complete. Epics are often too large to be completed in a single iteration and are typically broken down into smaller, more manageable user stories. Option A (a collection of smaller user stories) is partially correct because epics are often decomposed into smaller user stories, but option B provides a more precise definition as it emphasizes the size and effort required for completion. Options C and D are not correct in the DA context; they describe different types of analysis tools or techniques.

False : On an Agile team, the team members do not accept or reject their own work at the iteration demo. Instead, the Product Owner, along with stakeholders, is responsible for accepting or rejecting the work presented. The iteration demo (or sprint review) is an opportunity for the team to showcase their completed work to stakeholders and gather feedback. The decision to accept the work is based on whether it meets the Definition of Done, fulfills the acceptance criteria, and aligns with stakeholder expectations.

The primary advantage of breaking a project into phases is that it enables teams to focus on critical themes and ease of governance. Phases provide a structure to manage complex projects by focusing on specific objectives or deliverables at each stage, facilitating better planning, monit oring, and control. This approach also makes it easier to align with governance requirements and to make course corrections based on learnings from earlier phases. Options A, B, and C do not capture the strategic and governance benefits provided by phased approaches.

In the PMI Disciplined Agile framework, the timely delivery of the product as committed is ultimately the responsibility of the entire team. While the Product Owner (Option A) provides direction and prioritization of work, and the Team Lead (Option B) facilitates the process, it is the collective responsibility of the Team Members (Option C) to deliver the product incrementally and meet commitments. Agile teams operate under the principle of shared responsibility and accountability for outcomes, meaning every team member contributes to the delivery process. Other roles, such as Gold User (Option D) and Architecture Owner (Option E), have specific responsibilities but are not accountable for the delivery timeline.

In Disciplined Agile, teams are encouraged to be flexible and evolve their life-cycle based on their context, learning, and needs. As teams gain experience, they may start with one life-cycle model and later transition to another that better suits their situation (e.g., moving from Scrum-based to Lean continuous delivery). This flexibility enables the team to optimize their way of working for continuous improvement.

Options A, B, and C are not correct. The inception phase does not last until the architecture is proven; the transition phase is not necessarily about the amount of functionality built; Agile and Lean life-cycles can include inception and transition phases.

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.

Making design choices early in a project is not a desirable practice in design thinking. Design thinking encourages a flexible, iterative approach to problem-solving, where solutions are refined through experimentation and feedback from real users. By delaying design choices until more information is available and validated, teams can better align their solutions with user needs and constraints. The other options—being aware of constraints, empathy for customers, and situational appropriateness—are core principles in design thinking that help teams create more user-centered and effective solutions.