The Disciplined Agile principles that best address the need to consider the bigger picture are Enterprise Awareness and Context Counts .

Enterprise Awareness ensures that teams understand how their work fits within the broader organizational context, including alignment with corporate objectives, policies, and other teams. This principle encourages teams to think beyond their immediate tasks and consider the overall goals and constraints of the organization.

Context Counts emphasizes that the approach to work should be tailored to the specific situation and environment. It promotes the idea that different contexts require different strategies, and there is no one-size-fits-all approach. Both principles encourage a holistic view that considers the larger organizational and environmental factors influencing team decisions.

In Disciplined Agile, the amount of work to be completed during an iteration is defined by the team members themselves, based on their understanding of their current capacity and velocity. The team collaboratively estimates what they can achieve and commits to completing that work. Option A (the Product Owner) is responsible for prioritizing the backlog but does not dictate the amount of work. Option B (the team lead) facilitates the process but does not decide the work. Option D (the quality tester) is involved in testing completed work but does not determine the iteration's workload.

Top of Form

Bottom of Form

Disciplined Agile projects do not aim to maximize work-in-progress (WIP). Instead, they aim to minimize WIP to increase efficiency and reduce waste. By limiting WIP, teams can focus on completing tasks faster and delivering value more frequently. This approach is aligned with lean principles, which discourage multitasking and encourage teams to complete work items before starting new ones. Therefore, the statement that disciplined agile projects try to maximize WIP is false. The goal is to optimize the flow of work, not overload the team with too many concurrent tasks.

Top of Form

Bottom of Form

The first step in deciding the team's way of working (WoW) in Disciplined Agile is to analyze the context . Understanding the context includes assessing the team's current situation, the organization's culture, available skills, tools, stakeholder expectations, and project goals. This analysis helps determine which practices, tools, and techniques are most appropriate for the team’s unique environment. Based on this understanding, the team can make informed decisions on their WoW.

References:

PMI’s Disciplined Agile Senior Scrum Master (DASSM) curriculum materials.

"Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)", PMI.

The Team Lead, in Disciplined Agile, is responsible for ensuring that the daily coordination meeting (often known as the daily stand-up) happens. While team members participate in the meeting and are responsible for their coordination, the Team Lead facilitates the process and ensures that it takes place consistently. This role helps maintain the cadence and discipline of the daily coordination meeting.

The principle "Choice is good" in Disciplined Agile does not mean that a team must present multiple products to customers and let them choose. Rather, it emphasizes the importance of providing teams with choices regarding the practices and strategies they adopt, tailored to their unique context. This principle allows teams to make informed decisions on their Way of Working (WoW), rather than being restricted to a prescribed set of processes. Thus, the correct answer is "False," as the principle focuses on flexibility and adaptability for the team, not on presenting multiple product options to customers.

The responsibility for choosing the team's lifecycle in Disciplined Agile (DA) depends on the context . DA promotes a context-driven approach where decisions are made based on the specific needs, objectives, and constraints of the team and the organization. In some cases, the team itself may choose the lifecycle that best fits its way of working. In other scenarios, the decision could be influenced by an Agile coach, team manager, or organizational guidelines. Therefore, it is not a one-size-fits-all answer, and the context determines who is best suited to make this decision.

Guided continuous improvement is not limited to using a prescriptive framework or model. In Disciplined Agile (DA), guided continuous improvement can be achieved by using principles, guidelines, and practices that are adaptable to various contexts. It emphasizes learning and improving based on feedback, rather than following a strictly defined process.

The "Marketing" process blade in the Disciplined Agile framework provides strategies to ensure successful interactions with the external world about your organization, products, and offerings. Marketing focuses on understanding customer needs, communicating the value proposition of products and services, and engaging effectively with potential and current customers to build brand awareness and drive sales. Other options like Portfolio Management (A), Product Management (B), Sales (C), and Business Operations (D) have different focuses and do not specifically cover the broad external communication strategy and positioning that Marketing does.

In the Disciplined Agile (DA) framework, the transition from the Construction phase to the Transition phase in a project is marked by reaching the milestone of "Sufficient functionality." This milestone indicates that the team has built enough functionality to justify moving into the Transition phase, where the focus shifts from developing the product to deploying it into production. The term "sufficient functionality" aligns with the DA's principles that ensure the solution is viable and meets the stakeholders' needs at a basic level before moving to production deployment and further refinement. Other options like "Production ready" or "Proven architecture" may occur before or after reaching this specific milestone, but "Sufficient functionality" is the key indicator for moving into the Transition phase.