PMI Disciplined Agile Scrum Master DASM Exam Questions

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 : D

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.

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 : B

Address Changing Stakeholder Needs: This process goal involves actively engaging with stakeholders to understand and respond to their evolving requirements, preferences, and concerns throughout the project's life cycle. This goal is dynamic and requires significant effort because stakeholder needs and priorities can change frequently, requiring continuous adjustment of the Agile strategy. Tailoring your strategy to effectively address these needs involves multiple activities, such as conducting frequent reviews, reprioritizing the backlog, aligning deliverables with stakeholder expectations, and incorporating feedback into the development process.

Why It Requires the Most Effort:

Dynamic Nature of Stakeholder Needs: Stakeholders' needs are often unpredictable and can change rapidly due to market shifts, regulatory changes, or new business priorities. This requires Agile teams to be highly adaptive and frequently recalibrate their strategies.

Continuous Engagement and Communication: Maintaining an ongoing dialogue with stakeholders, gathering feedback, and negotiating trade-offs consume considerable time and resources.

Alignment and Consensus Building: Repeated effort is needed to ensure that all stakeholders are aligned and that there is a consensus on the direction and scope of the project.

Incorrect Options:

A . Improve Quality: While improving quality is a significant goal in any Agile strategy, it is more focused on refining existing processes, techniques, and tools rather than continuously adapting to external changes. Thus, it may not require as much continuous effort in tailoring the Agile strategy.

C . Align with Enterprise Direction: This goal involves ensuring that the team's work aligns with the broader organizational objectives. While important, it is generally a less dynamic activity compared to addressing changing stakeholder needs and may not require as frequent adjustments once alignment is initially achieved.

D . Explore Scope: Exploring the scope is an initial activity in an Agile project where the team works to understand the project's boundaries and deliverables. Although this requires effort at the beginning of the project, it is not a continuous effort throughout the project life cycle like addressing changing stakeholder needs.

Therefore, 'Address Changing Stakeholder Needs' is the process goal that requires the most effort due to its dynamic nature and the continuous engagement required to adapt the Agile strategy to evolving conditions.

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 : D

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.

Answer : A, B, E

In PMI's Disciplined Agile (DA) framework, process blades refer to modular, process decision-making tools that help organizations optimize their way of working (WoW). They are categorized into three primary areas:

Disciplined DevOps (A) - This blade focuses on streamlining and integrating development and operations activities, with a focus on continuous delivery and automation practices. It encompasses activities such as IT operations, quality assurance, data management, and release management to improve flow and operational efficiency.

Disciplined Project Management Office (PMO) (B) - The Disciplined Agile PMO is designed to oversee and provide governance to an organization's project and product delivery processes. It facilitates strategic alignment and value delivery across teams, ensuring that agile principles are applied at a broader organizational level, and that governance and funding models are adaptable.

Disciplined Agile Delivery (DAD) (E) - Disciplined Agile Delivery is a hybrid agile approach focused on the delivery of software-based solutions. It combines strategies from Agile, Lean, Scrum, and other methodologies to create a flexible and scalable approach to delivery. DAD provides guidance across all stages of solution delivery, from concept to deployment.

These three categories help organizations leverage Disciplined Agile principles by enabling flexible, scalable solutions that can be customized based on their specific context and needs.