DASM: Disciplined Agile Scrum Master

In Disciplined Agile, the Architecture Owner is responsible for mitigating key technical risks. This role focuses on overseeing the architectural integrity of the solution being developed, ensuring that the team makes sound technical decisions that align with the desired architecture and quality attributes of the project. The Architecture Owner helps in identifying and addressing potential technical risks early in the project life cycle, collaborating with the team to adapt the architecture as necessary to mitigate these risks.

This individual works closely with the team to guide architectural considerations, ensures compliance with the chosen architectural strategies, and maintains the overall technical direction of the project. Although they are involved in other cross-functional activities, their primary responsibility is to foresee and address technical challenges that could jeopardize the success of the project.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which details the responsibilities of the Architecture Owner, including mitigating technical risks.

PMI Disciplined Agile (DA) Toolkit, which provides an overview of the roles and responsibilities within DA, particularly the Architecture Owner's role in managing technical risks.

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.

The Kaizen feedback loop is commonly summarized as Plan, Do, Study, Act (PDSA). This cycle is used for continuous improvement and problem-solving, where:

Plan: Identify a goal or process and plan a change.

Do: Implement the change on a small scale.

Study: Observe and analyze the results of the change.

Act: Decide on necessary adjustments and standardize the successful changes.

Other options do not correctly capture the Kaizen loop:

A . Plan, Do, Monitor, Study incorrectly places 'Monitor'.

B . Plat, Implement Demo, Study mixes unrelated steps.

D . Study, Act, React, Demo does not follow the correct logical order of the Kaizen feedback loop.

Thus, the correct answer is C. Plan, Do, Study, Act.

The eight principles of Disciplined Agile (DA) provide a foundation for making sound decisions within an agile framework. The correct principles are:

Delight Customers: Focus on delivering high-quality products and services that meet or exceed customer expectations.

Be Awesome: Encourage team members to be the best they can be and create an environment that enables them to excel.

Pragmatism: Apply practical approaches and techniques that are most suitable for the given context.

Context Counts: Understand that every situation is unique, and practices should be tailored accordingly.

Choice is Good: Promote multiple ways of working and allow teams to choose the most appropriate techniques.

Optimize Flow: Focus on improving the flow of work to maximize efficiency and minimize waste.

Enterprise Awareness: Ensure teams understand and align with the organization's broader goals and strategies.

Organize around products/services: Structure teams and workflows around delivering value to customers through products or services.

Therefore, the correct answer is B. Delight Customers, Be Awesome, Pragmatism, Context Counts, Choice is Good, Optimize Flow, Enterprise Awareness, Organize around products/services.

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 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.

Disciplined Agile (DA) milestones are based on the concept of Lean governance, which is focused on ensuring that agile practices are aligned with the organization's overall objectives while minimizing bureaucracy. In the DA framework, milestones provide lightweight checkpoints throughout the lifecycle to ensure that the team is on track to meet its objectives and deliver value. These milestones are not about documentation or merely following a predefined lifecycle but are instead focused on achieving business value in a lean and efficient manner.

A . Continuous integration is a practice rather than a basis for milestones.

B . Documentation is not a central focus of DA milestones.

D . Lifecycle refers to the various phases in the DA process, but milestones are specific checkpoints within these phases guided by lean governance principles.

Thus, C. Lean governance is the correct answer, as it embodies the principles upon which Disciplined Agile milestones are established.

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.

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.