According to theINVEST mnemonic, a good user story should beValuable. This means that the user story must deliver value to the customer or stakeholder. Each user story should have a clear purpose, ensuring that the effort invested in its development contributes to the overall product value. Other criteria of the INVEST mnemonic include Independent, Negotiable, Estimable, Small, and Testable, but “Valuable” is key to justifying the user story’s inclusion in the product backlog.

In Disciplined Agile (DA), theTeam Lead(often equivalent to the Scrum Master role in Scrum) is primarily responsible for ensuring that the team adheres to the agreed-upon practices andbuilds the product correctly.
This involves facilitating the team’s processes, coaching team members on agile practices, and helping them remove impediments. The Team Lead is responsible for guiding the team in following the chosen way of working (WoW) and ensuring that the team’s processes are efficient, effective, and continuously improving.
Therefore, the primary focus is on ensuring that the product is built correctly according to the standards and requirements agreed upon by the team.

On a Disciplined Agile Delivery (DAD) team, theArchitecture Owneris a primary role. The Architecture Owner is responsible for guiding the team in making sound architectural decisions and ensuring that the architecture evolves appropriately to support the team’s work. This role involves collaborating with the team to address architectural concerns, mitigate technical risks, and ensure alignment with the overall technical vision. The Architecture Owner also helps the team navigate complex technical decisions and is a key player in maintaining the integrity of the system architecture.

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.

In Disciplined Agile (DA), aSpecialistis considered a supporting role. Specialists are individuals with deep expertise in a specific area, such as a database administrator, security expert, or a user experience (UX) designer. They are not necessarily core members of the delivery team but can be brought in as needed to provide specific skills or knowledge that the team requires at various points throughout the project. The focus of supporting roles like Specialists is to supplement the team’s capabilities and help address specific technical challenges.

A long-lived (or stable) team is a group of individuals who work together over an extended period, typically across multiple projects or product increments. In the context of PMI’s Disciplined Agile (DA) framework, having a long-lived team is beneficial for several reasons:
* Trustworthy (A):As team members work together over time, they build a strong sense of trust. Trust within a team is foundational for effective collaboration, decision-making, and conflict resolution.
Team members learn to rely on each other’s skills and knowledge, leading to more effective and efficient work processes. Disciplined Agile emphasizes creating environments where trust can be fostered, which is more easily achieved in stable, long-lived teams.
* Highly Collaborative (C):Long-lived teams develop a rhythm of working together, which leads to high levels of collaboration. As team members become more familiar with each other’s working styles, strengths, and weaknesses, they can communicate more effectively, align on goals more quickly, and coordinate their efforts more efficiently. This heightened collaboration accelerates delivery, improves quality, and fosters continuous improvement-key principles in the Disciplined Agile toolkit.
Incorrect Options:
* B. Projectized:While the concept of a “projectized” organization focuses on structuring around projects, this does not inherently relate to the benefits of having a long-lived team. In contrast, Disciplined Agile promotes stable teams over project-centric teams to maximize the value delivery and learning curve.
* D. Specifically resourced:This option refers to the allocation of specific resources for projects or tasks, which does not directly align with the idea of having a stable, long-term team.
* E. Ability to multi-task:Multi-tasking is generally not considered a benefit within agile frameworks, including Disciplined Agile. Multi-tasking can lead to inefficiency and reduced focus, which goes against the principles of optimizing flow and delivering value quickly.
Thus, the most appropriate answers that align with the principles of Disciplined Agile areA.
TrustworthyandC. Highly collaborative

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.

In Disciplined Agile, teams are encouraged to selectgoals that are most relevant to their context and life cycle. This approach ensures that the team focuses on achieving outcomes that align with their specific needs, challenges, and project phase. Goal diagrams in DA help teams visualize and prioritize their objectives, and by choosing goals most pertinent to their current context, teams can address the most critical aspects first and adjust their practices effectively.

Disciplined Agileis described as anagnostic hybrid techniquethat 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.

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 Lean and Agile terminology,Pushrefers to work beinggiven to peopleregardless of their current capacity.
This approach contrasts with a “pull” system, where work is pulled by the team when they have the capacity to handle it. “Push” systems often lead to overloading team members, increased bottlenecks, and inefficiencies.
* A. Delayed until laterdoes not capture the concept of “Push.”
* C. Expedited to meet a deadlineis about urgency, not pushing work.
* D. Outsourced to a vendorrefers to the delegation of work outside the team and is unrelated to the
“Push” concept.
Thus, the correct answer isB. Given to people.

The purpose of aniteration retrospectivein 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 iterationis the purpose of an iteration review or demo, not a retrospective.
* C. To prioritize stories and concrete tasks for the next iterationis typically part of iteration planning.
* D. To identify progress and to note encountered impedimentsis also part of other ceremonies like daily standups but not the main focus of a retrospective.
Thus, the correct answer isB. To transfer knowledge and improvements to the next iteration, aligning with the Disciplined Agile framework’s purpose for iteration retrospectives.

Acomplex adaptive systemis characterized by the idea that understanding the individual components does not necessarily provide a clear understanding of the system’s overall behavior. These systems are composed of interacting agents that adapt and learn from their experiences, leading to emergent behavior that cannot be easily predicted from the properties of the individual components. This concept is critical in Agile and Disciplined Agile practices, where teams and organizations are viewed as complex adaptive systems that evolve and adapt over time in response to their environment.

The method that extends the Kaizen loop strategy to help teams identify techniques likely to work in their context isGuided continuous improvement. In the Disciplined Agile (DA) toolkit, guided continuous improvement refers to using a structured approach to learning and adaptation, where teams are provided with guidance and options based on proven practices. This helps teams apply Kaizen principles effectively in their unique environments by selecting and tailoring techniques that are most likely to yield positive results.
* A. Explicit workflow policiesrefer to defining specific rules about how work is managed but do not inherently guide continuous improvement.
* C. Communities of practiceinvolve groups that share knowledge, but they do not extend the Kaizen loop strategy directly.
* D. Cross-team learninghelps in sharing knowledge between teams but is not the method extending the Kaizen loop strategy.
Thus, the correct answer isB. Guided continuous improvementas it directly aligns with the aim of adapting the Kaizen strategy to specific contexts.

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.

Theeight 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 isB. Delight Customers, Be Awesome, Pragmatism, Context Counts, Choice is Good, Optimize Flow, Enterprise Awareness, Organize around products/services.

In the context of the Disciplined Agile (DA) framework, a “specialist” on a Disciplined Agile Delivery Team is someone with a specific, specialized skill set or domain expertise that contributes to the overall development and delivery process. While the DA framework promotes cross-functional team members, it acknowledges that certain roles require specialized knowledge.
ABusiness Analyst (BA)is considered a specialist role because they bring specific expertise in requirements gathering, process analysis, stakeholder communication, and translating business needs into actionable tasks for the development team. According to PMI’s Disciplined Agile guidelines, BAs provide value by ensuring that the requirements are well-understood and clearly defined, which is crucial in aligning the team’s efforts with stakeholder needs.
On the other hand, the roles ofProduct Owner (B)andProject Manager (C)are more related to leadership, decision-making, and coordination, rather than specialized technical or analytical expertise.Stakeholders (D) are external to the delivery team and are not considered specialists within the team itself.

When a team completes their iteration backlog earlier than expected, the recommended approach in Disciplined Agile is to collaborate with the product owner to pull additional work from the product backlog into the iteration backlog. This approach maintains momentum and ensures that the team continues delivering value without waiting for the next iteration. It promotes agility and maximizes productivity by utilizing any remaining time effectively.
* A. Working on non-critical tasksorD. waiting for other groupsare not effective uses of the team’s time and do not align with agile principles of continuous value delivery.
* C. Reporting differences in completion timehelps with future planning but does not address the immediate need to continue productive work.
Thus, the correct answer isB. Work with the product owner to pull more work from the product backlog into their iteration backlog.

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.