Pass the PMI Agile DASSM Questions and answers with ExamsMirror

Using a Pull system means that work is pulled by the team members only when they are ready to start the next piece of work. It does not mean that all team members are pulled in to do the work. Instead, the team pulls in work based on capacity and readiness, ensuring a manageable workflow and limiting Work In Progress (WIP). Options B, C, and D describe principles that align with a pull system, but A does not.

In Disciplined Agile (DA), the "Specialist" is considered a supporting role. Specialists possess expertise in specific areas (e.g., security, database management) and are brought in as needed to support the primary delivery team. The supporting roles are not part of the core team but contribute specialized skills and knowledge when required.

Options A (Stakeholder), B (Team Lead), and D (Architecture Owner) are not supporting roles. Stakeholders represent end-users or business interests, while Team Leads and Architecture Owners are considered primary roles within a DA team.

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.

A Minimum Viable Product (MVP) is a product with the minimum set of features needed to satisfy early customers and gather feedback for future development. The primary purpose of an MVP is to validate product assumptions, understand user needs, and guide subsequent iterations based on real user feedback. This iterative approach helps in aligning the product with customer expectations and reducing the risk of failure.

Options A (last iteration of development), B (not yet ready to be sold), and C (used for demonstration only) do not accurately reflect the primary purpose of an MVP in Disciplined Agile.

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.

When choosing your team's way of working (WoW), it is important to focus onall of the goal diagrams. In Disciplined Agile, the goal diagrams provide guidance on various aspects of agile project management, including inception, construction, transition, and ongoing work. By considering all of these diagrams, teams can select the most appropriate practices and strategies for their specific context. This comprehensive approach helps teams build a tailored way of working that optimizes their processes across all phases of development, from inception to ongoing support. Relying on only one set of diagrams would limit the team's ability to adapt and optimize effectively.

User stories are a key component in Agile practices, including the Disciplined Agile (DA) framework. They are typically described by the acronym INVEST, which stands for:

Independent: User stories should be self-contained, so they do not overlap with others.

Negotiable: User stories are not contracts; they should leave room for discussion and refinement.

Valuable: Each user story must deliver value to the end user or customer.

Estimable: A good user story can be estimated in terms of the effort required to complete it.

Small: User stories should be small enough to be completed within a single iteration.

Testable: A user story must be testable, meaning it should be possible to determine whether the user story has been completed successfully.

Based on the INVEST criteria, "Achievable" is not a recognized feature of a user story. While achieving a user story is an implicit goal, it is not explicitly mentioned in the standard definition or characteristics used in Agile frameworks such as Disciplined Agile. The features that are essential to a user story are "Negotiable," "Estimable," and "Testable," as they ensure the story is clearly defined, measurable, and valuable to the user.

References:

Disciplined Agile Delivery: A Practitioner's Guide to Agile Software Delivery in the Enterprise, Scott Ambler & Mark Lines.

PMI’s Disciplined Agile Scrum Master (DASM) and Disciplined Agile Senior Scrum Master (DASSM) training materials.

In Disciplined Agile, it is the team members who decide how much work is moved from the product backlog to the iteration backlog. This decision is based on the team's capacity, velocity, and understanding of the complexity and size of the work items. While the Product Owner (B) prioritizes the product backlog, it is up to the team to determine how much of that work can be realistically completed within an iteration. Stakeholders (C), the team manager (D), or the project manager (E) do not make this decision.

Among the four views that describe Disciplined Agile (DA),Practicesare best represented asgoal diagrams. DA goal diagrams visually depict the process goals and decision points that teams can navigate to choose the best way of working (WoW) in their specific context. These diagrams provide guidance on options, techniques, and strategies for achieving different agile and lean practices.

Options B (Lifecycle models), C (Principles and guidelines), D (Roles and responsibilities), E (Team structures), and F (Workflows) describe other aspects of DA but do not specifically represent 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.