PMI Disciplined Agile Scrum Master DASM Exam Questions

Answer : B

The purpose of an iteration retrospective in the Disciplined Agile framework is to reflect on the team's process and performance during the previous iteration to identify what went well and what can be improved. The primary goal is to continuously improve by transferring the lessons learned, knowledge, and potential improvements to the next iteration. This aligns with Disciplined Agile's emphasis on continuous improvement and learning, which is critical to the team's effectiveness and efficiency.

The other options are not the primary focus of an iteration retrospective:

A . To showcase what the team accomplished in an iteration is the purpose of an iteration review or demo, not a retrospective.

C . To prioritize stories and concrete tasks for the next iteration is typically part of iteration planning.

D . To identify progress and to note encountered impediments is also part of other ceremonies like daily standups but not the main focus of a retrospective.

Thus, the correct answer is B. To transfer knowledge and improvements to the next iteration, aligning with the Disciplined Agile framework's purpose for iteration retrospectives.

Answer : A

In Team Estimation, also known as relative estimation or silent grouping, the team first estimates the relative sizes of all user stories by comparing them against each other. The stories are arranged in order of size (smallest to largest) without initially assigning specific numbers. After ordering, numerical values (such as story points) are then assigned to each story based on their relative size. This method leverages group consensus and comparative analysis to provide more accurate estimates.

B . Ranking teams in order of importance is not part of the Team Estimation process.

C . Defining 'Definition of Done' criteria is a separate exercise, not related to estimating story size.

D . Estimating necessary roles is not a part of Team Estimation.

Answer : C

Disciplined Agile is described as an agnostic hybrid technique that draws upon many different ideas from multiple agile and lean frameworks. Unlike other agile methodologies that prescribe a specific set of practices, Disciplined Agile provides a toolkit that allows teams to choose and tailor their way of working based on their unique context, goals, and constraints. It integrates strategies from Scrum, Kanban, Lean, XP (Extreme Programming), SAFe (Scaled Agile Framework), and other approaches, providing a more flexible and adaptive approach to project management.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which describes Disciplined Agile as a hybrid approach that is framework-agnostic and adaptable to different situations.

PMI Disciplined Agile (DA) Toolkit, which discusses the agnostic and hybrid nature of DA and its ability to draw upon multiple methodologies.

Answer : A

A value stream map is a Lean tool that helps teams visualize the flow of work and identify waste throughout the process of delivering a product or service. The primary purpose of a value stream map is to help the team identify problem areas or bottlenecks in the path to realizing value. By understanding where delays, excess inventory, or unnecessary steps occur, teams can target these areas for improvement, thereby minimizing waste and optimizing the flow of value to customers.

B . Focusing on the construction phase is not specific to minimizing waste across the entire value stream.

C . Reducing delays in the workflow process is an outcome of identifying problem areas but not the direct function of value stream mapping.

D . Applying the five Whys root cause method is a separate Lean technique that can complement value stream mapping but is not its main purpose.

Answer : B

Disciplined Agile (DA) is defined as a process-decision toolkit that offers a broad range of guidance to help individuals, teams, and organizations streamline their processes in a way that makes sense given their unique context. DA is not a specific methodology; instead, it provides a toolkit that integrates various agile, lean, and traditional strategies, allowing teams to choose the best approach for their situation.

A . An agile set of practices promoting autonomy within a PMO is not accurate, as DA is broader than just a PMO.

C . An approach that frequently assesses change is not the specific purpose of DA.

D . A methodology exploring various agile and waterfall practices does not accurately represent DA's comprehensive and context-sensitive nature.

Therefore, the correct answer is B. It is a process-decision toolkit that provides straightforward guidance to help people, teams, and organizations to streamline their processes in a context-sensitive manner.

Answer : A

During an iteration demo (also known as an iteration review), the team presents the work completed during the iteration to stakeholders and obtains feedback. This feedback is crucial for ensuring that the team is delivering the desired value and making adjustments as needed for future iterations. The demo provides an opportunity for the product owner and other stakeholders to inspect the product increment and provide input that can be used to refine the backlog and guide the team's efforts.

B . Retrospective is focused on team improvement rather than obtaining product feedback.

C . Iteration planning is for planning the work to be done, not gathering feedback.

D . Daily stand-up/coordination meeting is used for team synchronization and does not involve external feedback.

Answer : A

In Disciplined Agile (DA), Minimum Business Increment (MBI) (A) is a key tool used to sequence work in order to deliver value quickly. An MBI is the smallest piece of functionality that can deliver recognizable value to the business and its stakeholders. By focusing on delivering MBIs, teams can prioritize and sequence their work to release incremental value to customers in a timely manner, reducing time-to-market and allowing for early feedback.

Here's a breakdown of why MBI is the correct answer:

MBI (A) is specifically designed to deliver real business value with the minimum amount of effort, ensuring that development work is focused on the most impactful features first. It's not just about delivering a working product, but rather delivering the smallest set of functionalities that provide business value, which can be immediately utilized by the organization or customers.

The other options have important roles in Agile but are not directly related to sequencing work to deliver value quickly:

Minimum Viable Product (MVP) (B): While MVP is crucial for early market testing, it is a broader concept compared to MBI. MVP aims to test the product's viability, but MBI is more focused on delivering incremental business value.

Planning Poker (C): A tool for estimating work efforts in Agile but not used for sequencing work.

Work in Process (WIP) Limits (D): This technique is related to managing workflow, typically in Kanban, by limiting the number of tasks in progress to avoid overloading the team. While it improves flow, it does not directly prioritize or sequence work based on business value.

Therefore, MBI (A) is the most effective technique for sequencing work to deliver value quickly in the DA framework.