QUESTION: 5

What are the three phases common across project life cycles? (Choose three)

Inspiration
Modulation
Construction
Inception
Transition

Answer(s): C,D,E

Explanation:

In Disciplined Agile (DA), the three common phases across project life cycles are Inception, Construction, and Transition. These phases reflect the iterative and incremental approach of agile methodologies tailored to suit varying contexts.
Inception: This phase is about getting things started properly. It includes initial planning activities such as defining the vision, developing a preliminary project plan, identifying stakeholders, securing funding, and setting up the initial environment.
Construction: This phase focuses on developing a consumable solution in a series of iterations. The team builds, enhances, and evolves the solution to ensure that it meets stakeholders' needs while remaining aligned with the overarching vision and goals. Transition: The transition phase ensures that the solution is ready for delivery to the end-users or stakeholders. This includes final validation and verification activities, user training, deployment, and addressing any remaining issues.
These phases are common in the DA life cycles, reflecting the disciplined approach to managing complexity in various types of projects, from straightforward to highly complex, while supporting adaptability and continuous improvement.

Reference:

PMI, "Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)," which outlines the DA life cycles, including Inception, Construction, and Transition phases. PMI's Disciplined Agile Toolkit, which describes these phases in detail and their relevance across different types of project life cycles.

Reveal Solution Next Question

QUESTION: 6

What is the architecture owner responsible for?

Mitigating key technical risks
Working cross-functionally to deliver the solution
Removing impediments
Determining the priorities for the solution

Answer(s): A

Explanation:

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.

Reference:

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.

Reveal Solution Next Question

QUESTION: 7

Why is the coordination meeting important for a project team?

It provides a demo of the product to keep everyone up to date.
It provides an opportunity for the team to help itself stay m sync.
It allows the stakeholders to see how well the team is working together.
If allows the team to reassess the backlog to meet their needs.

Answer(s): B

Explanation:

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.

Reference:

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.

Reveal Solution Next Question

QUESTION: 8

What arc the three categories of process blades, according to Disciplined Agile (DA)? (Choose three)

Disciplined DevOps
Disciplined Protect Management Office (PMO)
Disciplined Agile IT
Disciplined Kanban
Disciplined Agile Delivery (DAD)

Answer(s): A,B,E

Explanation:

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.

Reveal Solution Next Question

Free DASM Exam Braindumps (page: 2)

QUESTION: 5

Explanation:

Reference:

QUESTION: 6

Explanation:

Reference:

QUESTION: 7

Explanation:

Reference:

QUESTION: 8

Explanation: