Foundations OF Disciplined Agile practice questions

Portfolio Management

Why it fails: Portfolio management is high-level alignment.

Governance Framework

Why it fails: Governance ensures compliance, not lifecycle selection.

Team Roles

Why it fails: Roles define responsibility, not lifecycle.

Team Development

Why it fails: This is a valid blade.

People Management

Why it fails: This is a valid blade.

Financial Management

Why it fails: This is a valid blade.

Architecture Owner

Why it fails: Focuses on technical decisions.

Product Owner

Why it fails: Focuses on requirements.

Stakeholder

Why it fails: External party.

HR Manager

Why it fails: External to the team.

General Manager

Why it fails: Not a standard DA team role.

Project Auditor

Why it fails: Not a standard team role.

Requirements Analysis

Why it fails: This happens throughout.

Finalization

Why it fails: Not a standard phase name.

Approval

Why it fails: Not a lifecycle phase.

Define all rules

Why it fails: Not a process goal.

Mandate the tools

Why it fails: Not a process goal.

Tooling Layer

Why it fails: Not a DA layer.

External Consultant

Why it fails: Not a layer.

Lean life cycle

Why it fails: The Lean life cycle is optimized for teams that need to scale or have some geographic distribution, and it emphasizes flow-based metrics and reducing waste. While it also minimizes documentation, it is not the best fit for a co-located team with a well-understood solution. The Agile life cycle is more suitable here.

Exploratory life cycle

Why it fails: The Exploratory life cycle is used when the solution is not well understood, and the team needs to investigate multiple approaches. It is not appropriate for a well-understood solution. The scenario clearly states the solution is well understood, so this life cycle would introduce unnecessary overhead.

Continuous delivery: Agile life cycle

Why it fails: The Continuous delivery: Agile life cycle is intended for teams that can release frequently, often multiple times per day, and requires a high degree of automation and DevOps practices. The scenario does not indicate that the team has such capabilities or needs. The standard Agile life cycle is a better match.

To automate all documentation

Why it fails: Disciplined Agile provides guidance for selecting and tailoring ways of working; it contains no mechanism to automate documentation generation. It would be correct only where the question asked about tooling that produces artefacts automatically, not about a decision framework for delivery teams.

To force teams to use Scrum

Why it fails: Disciplined Agile is deliberately agnostic, offering a range of life cycles including agile, lean, continuous delivery and traditional; it never mandates Scrum. It would be correct only if the question concerned a framework that prescribes Scrum exclusively, which this toolkit explicitly avoids.

To replace all project managers

Why it fails: Disciplined Agile offers process guidance for choosing a way of working; it does not remove or replace the project manager role, which persists in most of its life cycles. It would be the right choice only if the question concerned eliminating management roles, which the toolkit never advocates.

Add more team members

Why it fails: Adding people increases coordination overhead and onboarding drag, which typically widens variability before throughput stabilises. It is tempting because extra capacity looks like a direct velocity fix, and would be correct when the team is genuinely understaffed against a stable, well-understood workload.

Increase WIP limits

Why it fails: Raising WIP limits lets more items start concurrently, increasing context switching and queueing that destabilise throughput rather than smoothing it. It is tempting because higher limits appear to permit progress, and would be right when the team is starved of work and limits are throttling legitimate parallel effort.

Stop all meetings

Why it fails: Cancelling all meetings removes the collaboration and feedback loops that surface and resolve blockers causing erratic delivery, so it does not optimise flow. It is tempting as a reaction to perceived meeting overhead, and would suit a team whose ceremony load genuinely exceeds the value those sessions deliver.

Team Level

Why it fails: Team Level addresses local delivery practices, backlogs and team-specific data needs, so it cannot align efforts with enterprise strategy; that alignment sits at Enterprise Awareness. Team Level is tempting because alignment ultimately happens in teams, but its actual purpose is executing work within the direction already set above it.

Enterprise Awareness

Why it fails: Enterprise Awareness is the layer that aligns team efforts with overall enterprise strategy, so selecting it here would actually be right; as the distractor it fails because the question's framing points to the layer coordinating delivery execution, which is Governance. Enterprise Awareness is tempting since it genuinely concerns strategic context.

Governance

Why it fails: Governance sets decision rights, standards and investment oversight across the DA framework, but the layer that translates enterprise strategy into team-level direction is Enterprise Awareness, not Governance. Governance is tempting because it does sound strategic, yet its actual purpose is enforcing compliance and accountability once direction exists.

Coordinate Activities

Why it fails: Coordinate Activities sequences work and manages dependencies across teams; it assumes roles already exist. It is tempting because coordination failures often accompany unclear ownership, but the process goal that actually defines roles and responsibilities within the team is the one addressing this gap.

Address Risk

Why it fails: Address Risk identifies, evaluates and mitigates delivery risks; it does not assign team roles or responsibilities. It is tempting because unclear roles can be logged as an impediment, but the process goal covering role definition is the one that organises the team and its accountabilities.

Explore Initial Scope

Why it fails: Explore Initial Scope establishes the project's vision, context and boundaries, not team roles. It is tempting because scoping exercises do surface stakeholders, but role definition belongs to the process goal that organises the Agile team and assigns responsibilities, not to initial scoping.

Team Development

Why it fails: Team Development addresses team growth, skill acquisition and interpersonal dynamics, not workflow. Context switching is a flow problem, so the Work in Progress limits and queue management found in the Work Management blade apply. Choosing Team Development confuses people capability with process control.

Financial Management

Why it fails: Financial Management governs funding, budgets and cost allocation, not the flow of work items or team capacity. It tempts because it is a genuine process blade covering economic governance, which suits portfolio funding decisions. The scenario concerns limiting work in progress and smoothing delivery flow.

People Management

Why it fails: People Management covers staffing, career paths, performance and team composition, not the sequencing of tasks. Frequent context switching stems from excessive concurrent work, which the Work Management blade governs through WIP limits and flow policies. People Management would fit a resourcing or capability gap instead.

Command and Control

Why it fails: Command and control centralises approval in a hierarchy, so teams cannot decide at the speed agile delivery requires and feedback loops stall. Agile governance pushes decisions to the lowest capable level with clear guardrails. Command and control fits stable, safety-critical operations needing strict uniformity.

Ad-hoc Decision Making

Why it fails: Ad-hoc decision making lacks defined ownership, escalation paths and guardrails, so decisions cannot be traced or repeated as the governance model scales. Agile governance still requires lightweight, explicit decision rights. Ad-hoc approaches suit small exploratory prototypes, not an organisation-wide transition.

Full Documentation

Why it fails: Full documentation freezes decisions into artefacts approved before work starts, which conflicts with agile governance that delegates authority to teams and revisits decisions as evidence emerges. Documentation supports audit and onboarding; it becomes the chosen approach in regulated, plan-driven environments demanding formal sign-off.

Enterprise Awareness

Why it fails: Enterprise Awareness concerns aligning teams with organisational goals and broader business context, not rejecting universal approaches. It is tempting because it also warns against narrow local optimisation, but the no-one-size-fits-all emphasis belongs to Principles over Practices, which favours context-driven judgement over rigid prescribed methods.

Choice is Good

Why it fails: Choice is Good concerns giving teams autonomy to select practices, not the principle that contexts differ so no single approach fits all. It is tempting because both concern tailoring, but the concept addressing no one-size-fits-all is Principles over Practices, which rejects prescriptive universal methods.

Optimizing Flow

Why it fails: Optimising Flow addresses reducing batch size and handoffs to accelerate delivery, not the rejection of universal methods. It is tempting because flow improvement is context-dependent, but the concept explicitly stating there is no one-size-fits-all approach is Principles over Practices, which favours judgement over prescribed practice.

Choice is Good

Why it fails: Choice is Good concerns giving teams options and deferring decisions to the last responsible moment, not incremental process improvement. It is tempting because flexibility supports experimentation, but the principle describing continuous small improvements to how work is done is Optimise the Whole.

Context Counts

Why it fails: Context Counts addresses how teams adapt practices to their specific situation, not incremental process improvement. It is tempting because context sensitivity does shape how change is introduced, but the principle describing small, iterative steps toward better ways of working is Optimise the Whole, not this one.

Enterprise Awareness

Why it fails: Enterprise Awareness concerns aligning team decisions with broader organisational goals and strategy, not stepwise process improvement. It is tempting because enterprise-level thinking can motivate change, yet the principle explicitly about continuously refining process in small increments is Optimise the Whole.

Switch to Kanban

Why it fails: Kanban manages flow within one team's existing process; it adds no mechanism for coordinating dependencies, funding or integration across multiple teams. It is the right choice when a single team wants to visualise and limit work in progress, not when the goal is scaling agile across the organisation.

Add a Program Manager

Why it fails: Adding a Program Manager introduces a coordinating role but changes no team structure, process or technical practice, so it cannot deliver the scaled agile capability DA describes. It suits programmes needing cross-team reporting and dependency tracking, not the foundational step of establishing disciplined delivery before scaling.

Implement SAFe immediately

Why it fails: SAFe is a prescriptive scaling framework applied after teams already practise disciplined agile delivery; adopting it first imposes structure on immature teams. It is the right choice for large enterprises needing portfolio-level alignment across many existing agile teams, not as the initial step when scaling efforts.

To ensure everyone works the same way

Why it fails: DA discourages one-size-fits-all.

To report all team activities to management

Why it fails: Enterprise Awareness concerns understanding business strategy, goals and the wider organisational context so data initiatives align with them; activity reporting is governance or status reporting, not awareness. It is tempting because visibility of team work to leadership feels related to enterprise alignment, yet reporting flows upward rather than building shared business understanding.

To limit the team to internal tasks

Why it fails: Enterprise Awareness deliberately connects the team outward to business strategy, customers and cross-functional stakeholders; restricting work to internal tasks contradicts that purpose. It is tempting because focusing on internal data work feels efficient, yet the concept exists precisely to prevent such insularity.

The budget available

Why it fails: Budget constrains how much change a team can fund, but 'Choose Your WoW' selects a way of working from context factors such as team size, distribution, risk and culture; cost alone does not determine the appropriate method. It is tempting because finance gates adoption, and it would be correct when answering what limits the scale of transformation.

Executive preference

Why it fails: Executive preference reflects opinion, not the team's context, so it cannot determine the WoW selection. It is tempting because leadership sponsorship genuinely matters when adopting a scaling framework, but 'Choose Your WoW' derives its choice from the team's value stream, size, and coordination needs, not from a sponsor's taste.

The latest industry trend

Why it fails: Industry trends shift constantly and ignore the team's actual workflow, so they cannot ground the WoW decision. It is tempting because adopting proven external practises can accelerate improvement, but 'Choose Your WoW' selects a starting point from the team's own context and then inspects and adapts it.

Report all silos to HR

Why it fails: Escalating to HR treats siloed behaviour as a personnel conduct matter, whereas DA addresses structural causes such as team topology, funding and handoffs. HR reporting fits a scenario involving a specific individual's misconduct, not organisation-wide delivery friction. It changes nothing about how teams are organised or how work flows between them.

Force all teams to use the same tool

Why it fails: A shared tool standardises the interface but leaves team boundaries, ownership and incentives intact, so silos persist behind identical software. DA instead reorganises teams around value streams with end-to-end accountability. Tool consolidation is right when divergent platforms cause integration or licensing problems, not when the silos are structural.

Mandate daily meetings for everyone

Why it fails: Daily meetings add coordination overhead but leave the underlying silo structure and its delivery incentives untouched, so information still pools within each team. DA instead restructures around cross-functional value streams with shared ownership. Mandating stand-ups suits a single team needing tighter synchronisation, not separate teams whose boundaries are the problem.