Pass the PMI PMI Agile DASM Questions and answers with CertsForce

Disciplined Agile (DA) milestones are based on the concept ofLean 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 integrationis a practice rather than a basis for milestones.

B. Documentationis not a central focus of DA milestones.

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

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

Thecoordination meeting(often referred to as the daily stand-up or daily coordination meeting in Agile practices) is crucial for a project team becauseit 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.

In Disciplined Agile (DA), the three common phases across project life cycles areInception, Construction,andTransition. 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.

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, Evolutionare not standard DAD phases.

B. Initiation, Foundation, Conversiondo not match DAD terminology.

C. Introduction, Substance, Alterationare not relevant to DAD.

Therefore, the correct answer isD. Inception, Construction, Transitions.

A well-written user story in agile practices, including Disciplined Agile, describesthe customer's perspective. User stories are short, simple descriptions of a feature or requirement from the point of view of the end user or customer. They are intended to capture the "who, what, and why" of a requirement, focusing on the value it delivers to the customer. This perspective ensures that the development team understands the real-world needs and motivations behind the features they are building, allowing them to create solutions that truly meet user needs.

During aniteration demo(also known as an iteration review), the team presents the work completed during the iteration to stakeholders and obtains feedback. This feedback is crucial for ensuring that the team is delivering the desired value and making adjustments as needed forfuture iterations. The demo provides an opportunity for the product owner and other stakeholders to inspect the product increment and provide input that can be used to refine the backlog and guide the team’s efforts.

B. Retrospectiveis focused on team improvement rather than obtaining product feedback.

C. Iteration planningis for planning the work to be done, not gathering feedback.

D. Daily stand-up/coordination meetingis used for team synchronization and does not involve external feedback.

Disciplined Agile (DA)is defined as aprocess-decision toolkitthat 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 PMOis not accurate, as DA is broader than just a PMO.

C. An approach that frequently assesses changeis not the specific purpose of DA.

D. A methodology exploring various agile and waterfall practicesdoes not accurately represent DA's comprehensive and context-sensitive nature.

Therefore, the correct answer isB. 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.

The first step in choosing a team’s way of working (WoW) in Disciplined Agile is toanalyze the context. This involves understanding the specific needs, constraints, and circumstances of the team and its environment. By analyzing the context, the team can make informed decisions about which practices, tools, and frameworks are most appropriate for their situation. This ensures that the chosen WoW is tailored to fit the team’s unique challenges and goals.

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) provides a solid foundation for business agility through multiple mechanisms, including:

B. Defining a framework for agility at scale: DA offers a comprehensive toolkit that supports scaling agile practices across an organization, integrating principles from various agile methodologies to ensure coherence and alignment.

D. Providing guidance to streamline processes in a context-sensitive manner: DA emphasizes tailoring processes to the specific context of the organization, project, or team, rather than applying a one-size-fits-all approach. This flexibility allows organizations to adapt more effectively to change and improve their agility.

A. Enforcing adherence to organizational standardscontradicts the DA principle of pragmatism and flexibility.

C. Creating awesome teams that foster joyis beneficial but is not specifically cited as foundational for business agility.

E. Describing trade-offsis part of DA's decision-making framework but not directly a way of providing a foundation for business agility.

Thus, the correct answers areB. Defines a framework for agility at scaleandD. Provides guidance to streamline processes in a context-sensitive manner.