Most Recent PMI DASM 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.

According to the INVEST mnemonic, a good user story should be Valuable. This means that the user story must deliver value to the customer or stakeholder. Each user story should have a clear purpose, ensuring that the effort invested in its development contributes to the overall product value. Other criteria of the INVEST mnemonic include Independent, Negotiable, Estimable, Small, and Testable, but 'Valuable' is key to justifying the user story's inclusion in the product backlog.

PMI Disciplined Agile (DA) Toolkit, which outlines the INVEST criteria for user stories and emphasizes the need for stories to deliver value.

PMI Agile Practice Guide, which describes the characteristics of well-formed user stories using the INVEST mnemonic.

On a Disciplined Agile Delivery (DAD) team, the Architecture Owner is a primary role. The Architecture Owner is responsible for guiding the team in making sound architectural decisions and ensuring that the architecture evolves appropriately to support the team's work. This role involves collaborating with the team to address architectural concerns, mitigate technical risks, and ensure alignment with the overall technical vision. The Architecture Owner also helps the team navigate complex technical decisions and is a key player in maintaining the integrity of the system architecture.

PMI Disciplined Agile (DA) Toolkit, which describes the roles in a DA team and specifies the Architecture Owner as a primary role responsible for architectural concerns.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which outlines the roles and responsibilities of the Architecture Owner.

When a team completes their iteration backlog earlier than expected, the recommended approach in Disciplined Agile is to collaborate with the product owner to pull additional work from the product backlog into the iteration backlog. This approach maintains momentum and ensures that the team continues delivering value without waiting for the next iteration. It promotes agility and maximizes productivity by utilizing any remaining time effectively.

A . Working on non-critical tasks or D. waiting for other groups are not effective uses of the team's time and do not align with agile principles of continuous value delivery.

C . Reporting differences in completion time helps with future planning but does not address the immediate need to continue productive work.

Thus, the correct answer is B. Work with the product owner to pull more work from the product backlog into their iteration backlog.

The coordination meeting (often referred to as the daily stand-up or daily coordination meeting in Agile practices) is crucial for a project team because it provides an opportunity for the team to help itself stay in sync. This meeting is typically held daily and allows team members to communicate their progress, discuss any challenges or impediments, and align their activities with the project's goals.

In Disciplined Agile, such meetings are vital for fostering collaboration and ensuring that everyone on the team is aware of what others are doing, which helps avoid misunderstandings, duplicate work, and potential blockers. The purpose is not to report to a manager but for the team to coordinate, plan, and adjust their work dynamically to ensure continuous alignment and effective progress towards the team's objectives.

PMI Disciplined Agile Toolkit, which emphasizes the importance of coordination meetings (or daily stand-ups) in maintaining team alignment and promoting self-organization.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which describes the value of regular team coordination to ensure synchronicity and continuous alignment within agile teams.