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.

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.

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, 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.

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.

AMinimum 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.

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.

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.

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.

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.

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.

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.

The key attributes of a leader in an agile context include the ability tofocus on goals,inspire trust, andtake risks. Agile leaders guide their teams by keeping a clear vision of the goals, building trust through transparency and integrity, and being willing to take calculated risks to achieve desired outcomes. They do not simply “go with the flow” or assign tasks in a top-down manner; instead, they empower their teams, foster a culture of trust, and support innovation by encouraging risk-taking within safe-to-fail boundaries.

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.

* Address Changing Stakeholder Needs:This process goal involves actively engaging with stakeholders to understand and respond to their evolving requirements, preferences, and concerns throughout the project’s life cycle. This goal is dynamic and requires significant effort because stakeholder needs and priorities can change frequently, requiring continuous adjustment of the Agile strategy. Tailoring your strategy to effectively address these needs involves multiple activities, such as conducting frequentreviews, reprioritizing the backlog, aligning deliverables with stakeholder expectations, and incorporating feedback into the development process.
* Why It Requires the Most Effort:
* Dynamic Nature of Stakeholder Needs:Stakeholders’ needs are often unpredictable and can change rapidly due to market shifts, regulatory changes, or new business priorities. This requires Agile teams to be highly adaptive and frequently recalibrate their strategies.
* Continuous Engagement and Communication:Maintaining an ongoing dialogue with stakeholders, gathering feedback, and negotiating trade-offs consume considerable time and resources.
* Alignment and Consensus Building:Repeated effort is needed to ensure that all stakeholders are aligned and that there is a consensus on the direction and scope of the project.
Incorrect Options:
* A. Improve Quality:While improving quality is a significant goal in any Agile strategy, it is more focused on refining existing processes, techniques, and tools rather than continuously adapting to external changes. Thus, it may not require as much continuous effort in tailoring the Agile strategy.
* C. Align with Enterprise Direction:This goal involves ensuring that the team’s work aligns with the broader organizational objectives. While important, it is generally a less dynamic activity compared to addressing changing stakeholder needs and may not require as frequent adjustments once alignment is initially achieved.
* D. Explore Scope:Exploring the scope is an initial activity in an Agile project where the team works to understand the project’s boundaries and deliverables. Although this requires effort at the beginning of the project, it is not a continuous effort throughout the project life cycle like addressing changing stakeholder needs.
Therefore,”Address Changing Stakeholder Needs”is the process goal that requires the most effort due to its dynamic nature and the continuous engagement required to adapt the Agile strategy to evolving conditions.

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 agile practices, particularly in the context of user stories, the features are typically defined by the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, and Testable.”Achievable”is not a standard feature of a user story. Instead, user stories should beNegotiable(they are not fixed, and details can be discussed),Estimable(it should be possible to estimate the effort required), andTestable(it should be possible to verify whether the story has been implemented correctly). Therefore, “Achievable” is not one of the features of a user story.

Along-standing teamis best suited for a long-term project with the potential for significant budgeting and tracking overhead. In Disciplined Agile (DA), a long-standing team is a stable, cross-functional team that remains intact over time and works on various projects or continuous delivery of value. This type of team reduces overhead associated with forming and disbanding teams and allows for more consistent tracking, budgeting, and management of resources. Additionally, long-standing teams develop stronger team dynamics and improve performance over time due to their stability.
* B. A project teamis typically temporary and disbanded once the project ends.
* C. A cross-functional teamis a characteristic of many Agile teams but does not specifically address the need for long-term stability.
* D. A shared services teamsupports other teams by providing specialized skills but is not focused on long-term projects with budgeting needs.

The concept ofLeanwas developed around eliminating the three types of deviations that show inefficient allocation ofresources: 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.