DAF Exam Questions and Answers

To help teams tailor their WoW

Disciplined Agile exists to guide teams in choosing and tailoring their Way of Working (WoW) to fit their unique context, rather than imposing one prescribed method. This directly satisfies the stem's focus on tailoring, distinguishing it from frameworks that mandate fixed practices.

Identify and remove bottlenecks

Inconsistent velocity signals uneven flow through the value stream, so Optimize Flow requires locating the constraint restricting throughput and eliminating it. Removing bottlenecks smooths delivery cadence, directly addressing the variability described in the stem rather than adjusting estimates or pushing the team harder.

Portfolio Management

Portfolio Management coordinates value streams and initiatives across teams, translating enterprise strategy into funded, prioritised work. It is the layer that connects strategy to delivery, ensuring team efforts align with organisational goals rather than local optima.

Form Team

Form Team establishes the team's structure, including the roles members occupy and how responsibilities are allocated. Unclear roles therefore point directly at this goal, which defines who does what before the team can deliver value effectively.

Coordinate Activities

Coordinate Activities addresses cross-team dependency management and work-flow orchestration, directly tackling the context switching caused by uncoordinated handoffs. Unlike process blades focused on a single team's internal cadence, it governs how multiple teams align their efforts, satisfying the stem's constraint of managing flow across the wider value stream rather than within one team.

Lean Governance

Lean Governance decentralises decisions to the teams closest to the work, using guardrails and feedback rather than upfront approval gates. Adopting it satisfies the stem's constraint of agile transition, where decision-making must be fast and evidence-based.

It allows for early detection and correction of errors

Iterative delivery produces working increments each cycle, so defects and misaligned requirements surface during testing rather than after full build. This early feedback loop satisfies the stem's need to detect and correct errors before they compound across the whole delivery.

Implement 'Just-in-Time' planning to reduce upfront analysis

Just-in-time planning focuses on immediate work, reducing unnecessary analysis.

Include 'refactoring' and 'testing' tasks within each iteration

Embedding refactoring and testing tasks within each iteration directly satisfies the stem's constraint of addressing technical debt during the iteration, rather than deferring it. Disciplined Agile treats debt as a continuous concern, so incremental improvement is folded into daily work, preventing accumulation and keeping the codebase maintainable.

Increase the frequency of stakeholder feedback loops

Increasing the frequency of stakeholder feedback loops shortens the gap between requirement clarification and delivery, surfacing ambiguity before it becomes scope creep. It satisfies the stem by tightening collaboration cadence, letting the team validate assumptions early and adjust scope continuously.

Update the plan and pivot the strategy accordingly

Updating the plan and pivoting preserves alignment with current market reality instead of executing a plan whose assumptions have failed. This satisfies the stem's constraint that the initial plan is no longer viable, reflecting Agile's empirical approach of responding to change over following a fixed, outdated baseline.

Be pragmatic and choose your way of working (WoW)

The Disciplined Agile Mindset holds that teams should be pragmatic, choosing and evolving their way of working to fit context rather than adopting one prescribed process. This satisfies the stem by describing the mindset's stance that process should be tailored, not mandated.

Analyze your team's context factors and select the option that best addresses your current challenges.

Context factors are the DA mechanism for choosing between equally viable options; they expose the team's specific constraints and challenges. Selecting the option that best addresses those challenges satisfies the stem's requirement to decide rationally rather than by preference.

The size of the team.

Team size directly shapes coordination overhead, communication paths and ceremony weight, so it is a primary tailoring factor in Disciplined Agile. Smaller teams need lighter governance, while larger teams require more structure, making size a genuine axis for choosing the Way of Working.

The complexity of the solution being built.

Solution complexity determines how much architecture, testing rigour and risk mitigation the team needs. Highly complex solutions demand more deliberate practices, while simple ones suit lighter approaches, making complexity a genuine tailoring factor within the Disciplined Agile Way of Working.

Inception.

Inception covers the project's early phases: defining scope, identifying stakeholders and agreeing the shared vision. This directly satisfies the stem's alignment goal, since it establishes common understanding before requirements and construction begin, unlike later Disciplined Agile phases such as construction or transition.

It allows teams to improve their way of working based on their unique context.

GCI tailors improvement to the team's own context rather than imposing a prescribed method. It satisfies the scenario's need for context-sensitive evolution by guiding teams to inspect their unique situation and select practices that fit, making the way of working genuinely their own.

Choice is good.

Choice is good affirms that teams should select from viable options rather than follow a single mandated process. This principle directly enables the Choose Your WoW approach, letting teams tailor their way of working to fit.

Context counts.

Context counts reflects Disciplined Agile's core premise that no single method suits every team, so the 'Choose Your WoW' process tailors practices to each organisation's unique situation. This principle directly satisfies the stem's requirement for a foundational guide, ensuring teams deliberately adapt rather than adopt a one-size-fits-all approach.

Be pragmatic.

Being pragmatic means focusing on what actually works for the team rather than dogmatically following any prescribed framework or ceremony. This supports 'Choose Your WoW' by encouraging practical, evidence-based tailoring over rigid adherence to a single method.

Analyze the 'Coordinate Activities' process goal and select a practice to limit WIP.

The Choose Your Way of Working mindset starts from the process goal, not the symptom. Analysing 'Coordinate Activities' and selecting a practice that explicitly limits WIP addresses the root cause of the delays, rather than applying an unaligned local fix.

To minimize the opportunity for information loss and waiting.

Each handoff between specialised teams creates a queue where work waits and knowledge must be transferred. Lean seeks to reduce these handoffs because every transfer risks information loss and adds waiting time, both of which are non-value-add waste.

Developing features that the customer will never use.

Muda is any activity consuming effort without delivering value. Building features the customer never uses produces no value, so the effort, cost and delay it consumes are pure waste, unlike necessary but non-value-adding activities such as compliance testing.

It introduces a queue, increasing cycle time.

Centralised approval by the Project Management Office creates a queue: work waits between value-adding steps, and according to Lean, queues directly extend cycle time and delay feedback. The constraint in the stem is mandatory approval of every change, so each item must idle before release, making queueing an inherent, measurable flow penalty.

Shift team focus to assist in the Testing phase to clear the backlog.

Shifting team focus to assist Testing applies the theory-of-constraints principle of subordinating non-bottleneck capacity to the bottleneck, directly relieving the stalled Testing stage. Clearing that backlog raises throughput, whereas optimising upstream stages would only worsen the queue.

Build Quality In.

Reworking delivered code directly contradicts building quality in, which demands defects be prevented at each stage rather than detected downstream. The 30% rework figure evidences escaped defects, violating the Lean principle that quality is designed into the process, not inspected afterwards.

Establish strict WIP limits for each workflow state.

Task switching stems from people holding too many items at once, so limiting work in progress per workflow state constrains concurrent load. This directly satisfies the stem's constraint by reducing multitasking and its associated waste.