DAF Hard Questions — 25 Difficult Questions

Question 1

Why does the DA toolkit explicitly advise against 'standardizing' all teams on the same process?

Accepted Answer

Different teams have different contexts, and a single process would be suboptimal for most.. DA is built on the principle that there is no single 'best' process — the best process is the one that fits a team's specific context. Different teams face different constraints: team size, geographic distribution, regulatory compliance, technical debt, customer availability, and organizational culture. Standardizing all teams on one process would force many teams into practices that are suboptimal or even counterproductive for their situation, undermining the very adaptability DA is designed to enable. DA therefore recommends each team 'choose their WoW' and then consciously evolve it.

Answer

It is cheaper to let teams choose their own.

Answer

DA is a marketing tool that discourages standardization to sell more training.

Answer

Standardization is technically impossible.

Question 2

When applying 'Coordinate Activities' across multiple teams, what is the best DA approach?

Accepted Answer

Use a regular coordination meeting. DA recommends lightweight, regular coordination mechanisms — such as coordination meetings, scrum of scrums, or communities of practice — to align multiple teams without imposing rigid uniformity. A regular coordination meeting is the canonical DA approach for cross-team alignment. It preserves team autonomy while ensuring dependencies and integration points are managed.

Answer

Force all teams to use the same lifecycle

Answer

Appoint a single manager for all teams

Answer

Merge all teams into one large team

Question 3

How does DA handle technical debt?

Accepted Answer

Make it visible and plan for remediation. DA encourages managing technical debt through explicit visibility and planned remediation within the process goals.

Answer

Assign it to a separate team

Answer

Ignore it until the project is over

Answer

Ban all technical debt

Question 4

Your team needs to scale their agile efforts. What should be your first step according to DA?

Accepted Answer

Assess the current team maturity and context. According to Disciplined Agile, the first step when scaling agile efforts is to assess the current team maturity and context. DA emphasizes that scaling is not a one-size-fits-all journey; you must understand where the team is now (their skills, culture, constraints) before choosing a scaling approach. This aligns with DA's principle of 'Context Counts' and its guided continuous improvement approach.

Answer

Switch to Kanban

Answer

Add a Program Manager

Answer

Implement SAFe immediately

Question 5

Your organization is scaling Agile. What does Disciplined Agile suggest for scaling?

Accepted Answer

Choose a lifecycle that fits the specific needs of the teams. Disciplined Agile (DA) suggests that scaling Agile is not about adopting a single framework for all teams, but rather about choosing a lifecycle — such as Agile, Lean, Continuous Delivery, Program, or Hybrid — that fits the specific needs and context of the teams involved. This reflects DA's 'Choice is Good' principle and its recognition that different teams require different approaches.

Answer

Increase the size of individual teams to 50+ members

Answer

Adopt a single framework like SAFe for all projects

Answer

Standardize all teams to use the exact same process

Question 6

Which THREE of the following strategies help in 'scaling' Agile across multiple teams?

Accepted Answer

Use shared communication tools. Option B is correct because shared communication tools (e.g., Jira, Confluence, Slack, or Azure DevOps) give distributed Agile teams a single source of truth for backlogs, sprint boards, and impediments, enabling transparency and synchronization at scale. Option D is correct because coordinating activities across teams — through Scrum of Scrums, PI Planning, or dependency-mapping ceremonies — manages cross-team dependencies and integration points that inevitably arise when many teams work on one product. Option E is correct because a consistent Definition of Done ensures every team applies the same quality bar (e.g., code reviewed, tests passed, CI green, documentation updated), so increments from different teams are genuinely integratable and releasable. Option A is not correct because adding project managers increases overhead and central control rather than enabling the self-organizing, empirical flow that Agile scaling frameworks rely on. Option C is not correct because mixing frameworks per team (e.g., one Scrum, one Kanban, one SAFe) fragments terminology, cadence, and metrics, making cross-team coordination and shared planning far harder.

Answer

Increase the number of project managers

Answer

Ensure each team uses a different framework

Question 7

A team has high 'wait time' between code completion and code review. How should they address this using Lean principles?

Accepted Answer

Incorporate code review into the 'In Progress' workflow state.. The team should pull the review into their workflow, making it a collaborative, immediate step rather than an external dependency.

Answer

Hire more senior developers to review code.

Answer

Eliminate code reviews.

Answer

Schedule all reviews for the end of the week.

Question 8

Which THREE criteria are important to consider when selecting a delivery lifecycle in DA?

Accepted Answer

Project team size. In Disciplined Agile (DA), the delivery lifecycle is chosen based on context factors, and three of the options listed are genuine criteria: C (Project team size) matters because larger teams need more coordination and ceremony, favoring a more structured lifecycle such as a continuous delivery or lean lifecycle, while small teams can use lighter approaches; D (The level of uncertainty) is critical because high uncertainty favors an exploratory/agile lifecycle like Lean or Agile, whereas low uncertainty suits a more predictive or continuous delivery approach; and E (Technical complexity) is important because complex technical solutions may require more architecture, integration, and validation, influencing whether a continuous delivery, exploratory, or lean lifecycle fits best. Options A (The preferred color of the workspace) and B (The office location of the stakeholders) are not DA lifecycle selection criteria, as workspace color is irrelevant and stakeholder location is at most a minor environmental factor, not one of the core criteria for choosing a delivery lifecycle.

Answer

The preferred color of the workspace

Answer

The office location of the stakeholders

Question 9

Your organization is transitioning to a more agile governance model. Which approach should you adopt to ensure effective decision-making?

Accepted Answer

Lean Governance. Lean Governance focuses on risk-based oversight rather than bureaucratic checklists.

Answer

Command and Control

Answer

Ad-hoc Decision Making

Answer

Full Documentation

Question 10

A team is experiencing 'analysis paralysis' during the initial phase of their project. Which Disciplined Agile strategy is best to move forward?

Accepted Answer

Implement 'Just-in-Time' planning to reduce upfront analysis. Disciplined Agile suggests 'Evolutionary' approaches, where the team performs just enough planning to start, then adapts.

Answer

Extend the sprint duration to allow more time for analysis

Answer

Switch to a full Kanban system without any planning

Answer

Mandate a strict waterfall phase gate review

Question 11

A team has been asked to implement a new feature. They don't know the technology stack well. What is the most 'disciplined' approach?

Accepted Answer

Perform a 'Spike' to explore the technology. Conducting a 'Spike' allows the team to research the technology before committing to a delivery plan.

Answer

Commit to the feature immediately and learn as they build

Answer

Reject the feature request until they are experts

Answer

Ask management to assign an expert to do the work for them

Question 12

You are leading a project where the team needs to adopt a lean lifecycle. Which aspect of the DA toolkit helps you choose the right lifecycle for this specific context?

Accepted Answer

Process Goals. The Choose Your WoW process goal allows teams to select appropriate life cycles based on their unique situation.

Answer

Portfolio Management

Answer

Governance Framework

Answer

Team Roles

Question 13

You notice your team's velocity is inconsistent. How should you apply the 'Optimize Flow' principle?

Accepted Answer

Identify and remove bottlenecks. The 'Optimize Flow' principle in Disciplined Agile is about making value move smoothly through the system by finding and eliminating constraints. When velocity is inconsistent, the correct response is to identify bottlenecks — the constraint that limits throughput — and remove or relieve them, which stabilizes flow. This aligns with Lean's theory of constraints and the DA guidance to optimize the whole system rather than local efficiencies.

Answer

Add more team members

Answer

Increase WIP limits

Answer

Stop all meetings

Question 14

When applying 'Enterprise Awareness', what is the most important consideration for a team?

Accepted Answer

Alignment with broader enterprise objectives. Enterprise Awareness in Disciplined Agile emphasizes that teams should consider the broader organizational context when making decisions. The most important consideration is alignment with enterprise objectives, ensuring that team goals and activities contribute to the overall strategic direction of the organization. This alignment helps avoid sub-optimization and ensures that teams deliver value that matters to the enterprise.

Answer

Their own speed

Answer

The latest software tools

Answer

Their internal team dynamics

Question 15

Which TWO of the following are potential side effects of failing to address bottlenecks in a process?

Accepted Answer

Increased lead time for all items in the system.. Option B is correct because a bottleneck caps the throughput of the entire process, so work-in-progress queues up in front of the constrained step and every item—regardless of priority—spends longer waiting, which directly increases lead time (Little's Law: WIP = throughput × lead time). Option D is correct because unaddressed bottlenecks force people to constantly expedite, context-switch, and absorb schedule pressure at the constrained resource, which raises stress levels and is a well-documented driver of burnout. Option A is wrong because bottlenecks typically create friction and blame between teams rather than improving collaboration. Option C is wrong because a bottleneck delays all items, including high-priority ones, unless explicit prioritization mechanisms are introduced. Option E is wrong because bottlenecks usually increase costs through overtime, expediting, and delayed delivery, not reduce them.

Answer

Improved team collaboration.

Answer

Faster delivery of high-priority items.

Answer

A natural reduction in project costs.

Question 16

You are leading a team in a highly regulated industry. When using the Choose Your Way of Working tool, which aspect of the DA process decision framework must you prioritize to ensure compliance while maintaining agility?

Accepted Answer

Address the 'Produce Potentially Consumable Solution' process goal and evaluate the 'Document Solution' decision point.. In a highly regulated industry, compliance is critical. The DA process decision framework includes the 'Produce Potentially Consumable Solution' process goal, which encompasses the 'Document Solution' decision point. By addressing this goal and evaluating the documentation decision point, teams can ensure that necessary compliance documentation is produced while still maintaining agility through tailored practices.

Answer

Choose a lifecycle that supports lightweight documentation only.

Answer

Minimize the number of roles to increase speed.

Answer

Ignore the DA toolkit and stick to your existing Waterfall process.

Question 17

Which THREE of the following are elements of 'Agile Governance'?

Accepted Answer

Continuous risk management. Agile governance is lightweight, transparent, and built into the workflow.

Answer

Requiring a signature for every small change

Answer

Strict adherence to a detailed yearly budget

Question 18

You are leading a project with highly complex requirements. Which strategy does DA suggest for 'Explore Initial Scope'?

Accepted Answer

Use active stakeholder engagement and modeling. Disciplined Agile recommends exploring initial scope through active stakeholder engagement combined with modeling techniques such as user story mapping, impact mapping, and lightweight prototypes. This approach acknowledges that complex requirements cannot be fully specified upfront and are best discovered collaboratively with the people who will use and fund the solution.

Answer

Write a full requirements document

Answer

Delegate to the architecture team

Answer

Guess the requirements

Question 19

A team is building a high-criticality system (e.g., medical software). What is the DA approach to documentation?

Accepted Answer

Tailor documentation to meet regulatory and quality needs. DA's guidance is to tailor documentation to the actual regulatory, quality, and stakeholder needs of the system being built. For high-criticality systems like medical software, that means producing the traceability, design records, and verification evidence required by standards such as IEC 62304 or FDA design controls, but doing so incrementally rather than upfront. The principle is 'just enough documentation, just in time' scaled to risk.

Answer

Rely solely on automated test cases as documentation

Answer

No documentation is required as per Agile principles

Answer

Document everything in detail before starting

Question 20

Your organization is struggling with 'Shadow IT'—teams buying their own software without oversight. What is the Disciplined Agile view on this?

Accepted Answer

Provide organizational guidance on standards while allowing for innovation. Disciplined Agile advocates for a balanced approach to Shadow IT, where the organization provides guidance on standards and governance while still allowing teams the flexibility to innovate. This means establishing clear guidelines for software procurement and usage, but not imposing rigid bans that stifle innovation. The goal is to enable teams to make informed decisions that align with enterprise objectives.

Answer

Fully decentralize all IT procurement decisions

Answer

Force all teams to use legacy software only

Answer

Ban all software purchases by individual teams