Free PMI Disciplined Agile Scrum Master DASM Exam Questions

The three phases of Disciplined Agile Delivery (DAD)'s delivery life cycle are:

Inception: This phase focuses on getting the project off the ground. It includes identifying stakeholders, understanding the vision, defining the initial scope, and planning for the necessary resources and timeline.

Construction: This phase involves building the solution incrementally and iteratively, with continuous delivery of working software and regular stakeholder feedback.

Transition: This phase prepares the solution for release into production or the marketplace. It includes final validation, user training, deployment planning, and release management.

Other options are incorrect:

A . Commencement, Creation, Evolution are not standard DAD phases.

B . Initiation, Foundation, Conversion do not match DAD terminology.

C . Introduction, Substance, Alteration are not relevant to DAD.

Therefore, the correct answer is D. Inception, Construction, Transitions.

In agile practices, particularly in the context of user stories, the features are typically defined by the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, and Testable. 'Achievable' is not a standard feature of a user story. Instead, user stories should be Negotiable (they are not fixed, and details can be discussed), Estimable (it should be possible to estimate the effort required), and Testable (it should be possible to verify whether the story has been implemented correctly). Therefore, 'Achievable' is not one of the features of a user story.

PMI Disciplined Agile (DA) Toolkit, which discusses the criteria for writing effective user stories using the INVEST model.

PMI Agile Practice Guide, which outlines the characteristics of user stories and the INVEST criteria.

The Product Backlog is the artifact that collects all the work flowing to the team. It is a prioritized list of everything that might be needed in the product, managed and maintained by the Product Owner. The backlog is continuously refined and reprioritized as needed to reflect the changing needs of stakeholders, market conditions, and business priorities.

A . Business backlog is not a standard Agile artifact.

C . Release roadmap outlines future releases but does not collect all work items.

D . Iteration backlog contains a subset of the product backlog items selected for a specific iteration.

In Disciplined Agile (DA), the Team Lead (often equivalent to the Scrum Master role in Scrum) is primarily responsible for ensuring that the team adheres to the agreed-upon practices and builds the product correctly. This involves facilitating the team's processes, coaching team members on agile practices, and helping them remove impediments. The Team Lead is responsible for guiding the team in following the chosen way of working (WoW) and ensuring that the team's processes are efficient, effective, and continuously improving. Therefore, the primary focus is on ensuring that the product is built correctly according to the standards and requirements agreed upon by the team.

PMI Disciplined Agile (DA) Toolkit, which defines the role of the Team Lead as the person who ensures that the team follows effective practices and builds the product correctly.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which provides insights into the responsibilities of the Team Lead role in DA.

The Disciplined Agile (DA) principle of being pragmatic is characterized by the focus on 'being as effective as you can and continuously improving.' According to PMI's Disciplined Agile Toolkit, being pragmatic means applying an agile mindset that is not constrained by a rigid set of rules or practices. Instead, it emphasizes being practical and outcome-focused, aiming for the best results in each unique context while continually seeking opportunities for improvement.

Disciplined Agile promotes pragmatic decision-making by suggesting that teams should balance their approach by being both goal-driven and situation-aware. This means that instead of strictly adhering to a single agile framework or methodology, teams should assess their situation, leverage their experience, and apply the most suitable tools and techniques available. Furthermore, continuous improvement (Kaizen) is a fundamental aspect, meaning teams should regularly reflect on their practices and make iterative enhancements to achieve effectiveness.

This principle also aligns with DA's guidance to 'Optimize Flow' and 'Be Awesome,' as it encourages teams to deliver value while recognizing that every situation might require different tools, techniques, and practices. Thus, 'D. Being as effective as you can and continuously improving' best captures the essence of DA's pragmatic approach.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which details the core principles of Disciplined Agile, including being pragmatic by focusing on effectiveness and continuous improvement.

PMI Disciplined Agile (DA) Toolkit, which explains how being pragmatic involves choosing the best approach for your specific context rather than adhering to a strict methodology.

The eight principles of Disciplined Agile (DA) provide a foundation for making sound decisions within an agile framework. The correct principles are:

Delight Customers: Focus on delivering high-quality products and services that meet or exceed customer expectations.

Be Awesome: Encourage team members to be the best they can be and create an environment that enables them to excel.

Pragmatism: Apply practical approaches and techniques that are most suitable for the given context.

Context Counts: Understand that every situation is unique, and practices should be tailored accordingly.

Choice is Good: Promote multiple ways of working and allow teams to choose the most appropriate techniques.

Optimize Flow: Focus on improving the flow of work to maximize efficiency and minimize waste.

Enterprise Awareness: Ensure teams understand and align with the organization's broader goals and strategies.

Organize around products/services: Structure teams and workflows around delivering value to customers through products or services.

Therefore, the correct answer is B. Delight Customers, Be Awesome, Pragmatism, Context Counts, Choice is Good, Optimize Flow, Enterprise Awareness, Organize around products/services.