PMI DASM Practice Test - Questions Answers, Page 2

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.

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.

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.

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.

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.

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.

Disciplined Agile is described as an agnostic hybrid technique that draws upon many different ideas from multiple agile and lean frameworks. Unlike other agile methodologies that prescribe a specific set of practices, Disciplined Agile provides a toolkit that allows teams to choose and tailor their way of working based on their unique context, goals, and constraints. It integrates strategies from Scrum, Kanban, Lean, XP (Extreme Programming), SAFe (Scaled Agile Framework), and other approaches, providing a more flexible and adaptive approach to project management.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which describes Disciplined Agile as a hybrid approach that is framework-agnostic and adaptable to different situations.

PMI Disciplined Agile (DA) Toolkit, which discusses the agnostic and hybrid nature of DA and its ability to draw upon multiple methodologies.

The concept of Lean was developed around eliminating the three types of deviations that show inefficient allocation of resources: Muda (waste), Mura (unevenness), and Muri (overburden). Lean principles focus on maximizing value by minimizing waste and optimizing the use of resources, such as time, effort, and materials. By identifying and eliminating these inefficiencies, organizations can ensure that resources are allocated effectively, reducing costs, improving quality, and increasing customer satisfaction.

PMI Disciplined Agile (DA) Toolkit, which outlines Lean principles and their focus on optimizing resource allocation by eliminating waste, unevenness, and overburden.

Lean methodology concepts, which emphasize the elimination of Muda, Mura, and Muri to optimize resource allocation and efficiency.

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.