PMI DASM Practice Exam Questions & Answers

In Agile, and specifically within the Disciplined Agile framework, the retrospective is a crucial ceremony where the team reflects on their past iteration to identify areas of improvement. The main purpose is to foster continuous improvement by focusing on how the team can better work together moving forward. It encourages open communication, self-reflection, and team accountability, aligning with the agile principles of continuous learning and adaptation.

The other options are incorrect because:

B . Organizing the product backlog is typically done during backlog refinement sessions, not retrospectives.

C . Prohibiting stakeholders from making requests is not the purpose of a retrospective; stakeholder feedback is valuable and is usually gathered during review sessions.

D . Providing the product owner with insights into team dynamics may occur, but it is not the primary goal of the retrospective.

Therefore, the correct answer is A. It allows the team time to focus on how they can better work together moving forward, as it aligns with the continuous improvement objective central to Agile and Disciplined Agile practices.

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.

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.

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.

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.

In Disciplined Agile, the team members are responsible for defining the amount of work to be completed during an iteration based on their understanding of the team's current capacity. This is aligned with Agile principles that promote self-organizing teams and emphasize the importance of team members making commitments based on their realistic assessment of what they can achieve. This collaborative decision-making process helps to ensure that the team is neither over-committing nor under-utilizing its capacity, leading to sustainable delivery and higher quality outcomes.

PMI Agile Practice Guide, which supports the principle of team autonomy in deciding how much work they can complete in an iteration.

PMI Disciplined Agile (DA) Toolkit, which promotes self-organization and team-based decision-making regarding workload capacity.

A Minimum Viable Product (MVP) is a product with just enough features to satisfy early customers and provide feedback for future product development. The MVP approach allows organizations to test their product hypothesis with minimal effort and investment, gather valuable user feedback, and make informed decisions about further development. By delivering a basic version of the product quickly, teams can learn from real-world use, validate assumptions, and iterate on the product to better meet customer needs in subsequent versions.

PMI Disciplined Agile (DA) Toolkit, which discusses the concept of an MVP as a tool for early market entry, user feedback, and iterative development.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which outlines the role of an MVP in enabling rapid feedback loops and continuous improvement.