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

In Disciplined Agile, theConstructionphase of the project life cycle is responsible for developing aconsumable 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.

In Disciplined Agile, a good Team Lead (or Scrum Master) should act as a servant leader, supporting and enabling team members to succeed. When a team member is falling behind, the appropriate response is tohave a conversation with the team member to understand what is getting in their way and work together to find solutions. This approach fosters an environment of trust and collaboration and helps to identify and remove impediments that may be affecting the team member's performance. The goal is to address the root cause of the issue and provide support, rather than assigning blame or creating discomfort.

In Disciplined Agile,the team membersare responsible for defining the amount of work to be completed during an iteration based on their understanding of the team's current capacity. This is aligned with Agile principles that promote self-organizing teams and emphasize the importance of team members making commitments based on their realistic assessment of what they can achieve. This collaborative decision-making process helps to ensure that the team is neither over-committing nor under-utilizing its capacity, leading to sustainable delivery and higher quality outcomes.

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.

When analyzing a team's context for tactical scaling in Disciplined Agile, two key factors that must be considered areDomain ComplexityandTeam Size:

C. Domain Complexity: Refers to the complexity of the problem domain the team is working within. More complex domains require different approaches and potentially more sophisticated techniques to manage uncertainty, dependencies, and risks.

D. Team Size: The size of the team affects how the team communicates, collaborates, and organizes itself. Larger teams may require additional coordination, communication practices, and role definitions to be effective.

The other options are less relevant for tactical scaling:

A. Demographics,B. Best Practices,E. Budget, andF. Dynamicsare not directly identified as key tactical scaling factors in the Disciplined Agile context.

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

In Disciplined Agile, theArchitecture Owneris responsible formitigating 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.

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.

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.

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.