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.

In Disciplined Agile (DA), theTeam Memberrole is primarily responsible for building the product correctly.
Team Members are the individuals who directly create the product by writing code, testing, designing, and performing other tasks necessary to deliver a working solution. The Architecture Owner may guide architectural decisions, and the Team Lead may facilitate processes, but it is the Team Members who actively build the product and ensure it meets the required standards and specifications.

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.

In Lean and Agile methodologies, the role of management is tocreate awesome team environmentsthat foster collaboration, creativity, and high performance. Lean principles emphasize empowering teams, removing obstacles, and creating a culture of continuous improvement and respect. This means management’s role is to support the team, provide the necessary resources, and ensure a safe and conducive environment for delivering high-quality work.
* A. Ensure documentation is completedis not the primary role of management in Lean.
* B. Provide minimum viable products to the teamis more related to the responsibilities of product owners or teams, not management.
* C. Ensure decisions are not made regionallyis not directly related to the core responsibilities of management in Lean.
Therefore,D. Create awesome team environmentscorrectly reflects the Lean management role.

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.

In Disciplined Agile (DA),Minimum Business Increment (MBI)(A) is a key tool used to sequence work in order to deliver value quickly. An MBI is the smallest piece of functionality that can deliver recognizable value to the business and its stakeholders. By focusing on delivering MBIs, teams can prioritize andsequence their work to release incremental value to customers in a timely manner, reducing time-to-market and allowing for early feedback.
Here’s a breakdown of whyMBIis the correct answer:
* MBI (A)is specifically designed to deliverreal business valuewith the minimum amount of effort, ensuring that development work is focused on the most impactful features first. It’s not just about delivering a working product, but rather delivering thesmallest set of functionalitiesthat provide business value, which can be immediately utilized by the organization or customers.
The other options have important roles in Agile but are not directly related to sequencing work to deliver value quickly:
* Minimum Viable Product (MVP) (B): While MVP is crucial for early market testing, it is a broader concept compared to MBI. MVP aims to test the product’s viability, but MBI is more focused on delivering incremental business value.
* Planning Poker (C): A tool for estimating work efforts in Agile but not used for sequencing work.
* Work in Process (WIP) Limits (D): This technique is related to managing workflow, typically in Kanban, by limiting the number of tasks in progress to avoid overloading the team. While it improves flow, it does not directly prioritize or sequence work based on business value.
Therefore,MBI (A)is the most effective technique for sequencing work to deliver value quickly in the DA framework.

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.

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.

The role of theProduct Ownerin Agile and Disciplined Agile frameworks is to ensure the team isbuilding the right productthat aligns with stakeholder needs and provides maximum value tothe customer. The Product Owner achieves this by managing and prioritizing the product backlog, defining user stories, clarifying requirements, and making decisions on behalf of the stakeholders.
* A. Coordinate the productis not a primary function of the Product Owner.
* B. Inspect the productmay be a part of their responsibilities, but the focus is on guiding the product’s development.
* D. Organize the product teamis more aligned with the Scrum Master’s role.

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.

When introducing new features to a large, existing product, the product team should employ theMinimum Business Increment (MBI)technique. An MBI is the smallest piece of functionality that can be delivered that provides value to the business. It allows teams to deliver business value quickly while minimizing risk and ensuring that only essential, incremental changes are introduced. This approach is particularly useful for managing the complexity of large, established products and ensuring that new features are aligned with business goals.

Aniteration backlog(or sprint backlog) is createdat the beginning of each sprintduring the iteration planning meeting. This backlog consists of the tasks and user stories that the team commits to completing during the iteration. The process involves selecting the highest-priority items from the product backlog and breaking them down into smaller tasks that can be completed within the sprint timeframe.
* A. Planning the Kanban boarddoes not typically use an iteration backlog as Kanban is flow-based, not iteration-based.
* B. At the beginning of each projectis incorrect because the backlog is created for each sprint, not the entire project.
* C. When defining the MBI (Minimum Business Increment)is related to identifying the smallest unit of value delivery but is not when an iteration backlog is created.

The Disciplined Agile mindset includes principles that guide individuals and teams in making decisions and taking actions that align with Agile values and the specific context of their organization. Three principles of the Disciplined Agile mindset are:
* B. Enterprise awareness: Encourages teams to work with an understanding of their organization’s goals, strategies, and needs, ensuring alignment and collaboration across teams and departments.
* C. Delight customers: Focuses on delivering high value and exceptional service to customers, ensuring that their needs are met or exceeded.
* E. Be pragmatic: Involves taking a practical and context-sensitive approach, applying tools and practices that best fit the situation rather than adhering strictly to a particular methodology.
Other options likeA. Accelerate deliveryandD. Be a servant leaderare relevant to Agile practices but are not explicitly stated as Disciplined Agile mindset principles.
Thus, the correct answers areB. Enterprise awareness,C. Delight customers, andE. Be pragmatic.

In Disciplined Agile, theConstructionphase 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.

Avalue stream mapis a Lean tool that helps teams visualize the flow of work and identify waste throughout the process of delivering a product or service. The primary purpose of a value stream map is tohelp the team identify problem areas or bottlenecksin the path to realizing value. By understanding where delays, excess inventory, or unnecessary steps occur, teams can target these areas for improvement, thereby minimizing waste and optimizing the flow of value to customers.
* B. Focusing on the construction phaseis not specific to minimizing waste across the entire value stream.
* C. Reducing delays in the workflow processis an outcome of identifying problem areas but not the direct function of value stream mapping.
* D. Applying the five Whys root cause methodis a separate Lean technique that can complement value stream mapping but is not its main purpose.

In Agile, and specifically within the Disciplined Agile framework, theretrospectiveis 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 backlogis typically done during backlog refinement sessions, not retrospectives.
* C. Prohibiting stakeholders from making requestsis 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 dynamicsmay occur, but it is not the primary goal of the retrospective.
Therefore, the correct answer isA. 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.

InTeam Estimation, also known as relative estimation or silent grouping, the team first estimates the relative sizes of all user stories by comparing them against each other. The stories are arranged in order of size (smallest to largest) without initially assigning specific numbers. After ordering, numerical values (such as story points) are then assigned to each story based on their relative size. This method leverages group consensus and comparative analysis to provide more accurate estimates.
* B. Ranking teams in order of importanceis not part of the Team Estimation process.
* C. Defining “Definition of Done” criteriais a separate exercise, not related to estimating story size.
* D. Estimating necessary rolesis not a part of Team Estimation.

In Agile and Disciplined Agile practices, iterations are plannedat the beginning of each iterationduring an iteration planning meeting. The team, along with the product owner, pulls the highest-priority items from the product backlog that they believe can be completed within the iteration. This ensures that the work is well- defined, understood, and aligned with the current goals and priorities.
* A. Retrospective meetingsfocus on reflecting on the past iteration to identify improvements, not planning the next iteration.
* B. Using iteration reviewsimproves quality but is not about planning.
* D. Iteratively planning by the product owneralone does not ensure team alignment or collaboration, which is essential in Agile.
Therefore, the correct answer isC. At the beginning of each iteration by pulling from the product backlog.

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.