PMI DASM Disciplined Agile Scrum Master Exam Practice Test

Answer : B

In Disciplined Agile, the Construction phase of the project life cycle is responsible for developing a consumable solution in a collaborative and incremental manner. During this phase, the team iteratively builds the solution, working closely with stakeholders to ensure that the product or service being developed meets their needs and expectations. The Construction phase emphasizes agility, collaboration, and incremental development, where the solution evolves through repeated iterations, incorporating feedback and improvements at each step. This approach helps to minimize risks, adapt to changes, and deliver value more frequently.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which describes the Construction phase as the iterative process where the solution is developed incrementally and collaboratively.

PMI Disciplined Agile (DA) Toolkit, which outlines the phases of the DA life cycle, including the collaborative nature of the Construction phase.

Answer : B

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.

Answer : A

In the context of the Disciplined Agile (DA) framework, a 'specialist' on a Disciplined Agile Delivery Team is someone with a specific, specialized skill set or domain expertise that contributes to the overall development and delivery process. While the DA framework promotes cross-functional team members, it acknowledges that certain roles require specialized knowledge.

A Business Analyst (BA) is considered a specialist role because they bring specific expertise in requirements gathering, process analysis, stakeholder communication, and translating business needs into actionable tasks for the development team. According to PMI's Disciplined Agile guidelines, BAs provide value by ensuring that the requirements are well-understood and clearly defined, which is crucial in aligning the team's efforts with stakeholder needs.

On the other hand, the roles of Product Owner (B) and Project Manager (C) are more related to leadership, decision-making, and coordination, rather than specialized technical or analytical expertise. Stakeholders (D) are external to the delivery team and are not considered specialists within the team itself.

Answer : C

In Disciplined Agile (DA), the Team Member role is primarily responsible for building the product correctly. Team Members are the individuals who directly create the product by writing code, testing, designing, and performing other tasks necessary to deliver a working solution. The Architecture Owner may guide architectural decisions, and the Team Lead may facilitate processes, but it is the Team Members who actively build the product and ensure it meets the required standards and specifications.

PMI Disciplined Agile (DA) Toolkit, which clarifies the responsibilities of the various roles, specifying that Team Members are the ones actively involved in building the product.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which details the responsibilities of Team Members in delivering the product.

Answer : D

An iteration backlog (or sprint backlog) is created at the beginning of each sprint during the iteration planning meeting. This backlog consists of the tasks and user stories that the team commits to completing during the iteration. The process involves selecting the highest-priority items from the product backlog and breaking them down into smaller tasks that can be completed within the sprint timeframe.

A . Planning the Kanban board does not typically use an iteration backlog as Kanban is flow-based, not iteration-based.

B . At the beginning of each project is incorrect because the backlog is created for each sprint, not the entire project.

C . When defining the MBI (Minimum Business Increment) is related to identifying the smallest unit of value delivery but is not when an iteration backlog is created.

Answer : C

In the context of the Disciplined Agile framework, when a team is dealing with rapidly changing requirements but is resistant to frequent releases and does not have an Agile mindset, the Traditional lifecycle is appropriate. This lifecycle aligns with teams that prefer a more plan-driven, less iterative approach, which typically includes longer release cycles and detailed upfront planning. The Traditional lifecycle in Disciplined Agile follows a waterfall-like approach, which is suitable when the team is not yet prepared to adopt Agile principles such as frequent delivery and adaptive planning.

The other options do not match this scenario:

A . Program lifecycle is used for coordinating multiple teams on larger programs, which is not relevant to a single team with the specified conditions.

B . Lean focuses on optimizing flow and delivering value quickly, which contrasts with the team's preference for infrequent releases.

D . Agile lifecycle involves iterative development and frequent releases, which the team is resistant to.

Therefore, C. Traditional is the correct answer as it fits the team's preference for less frequent releases and their lack of an Agile mindset.

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.