Hard Difficulty Questions

Extend the sprint duration to allow more time for analysis

Why wrong: Extending sprints often leads to more analysis paralysis rather than resolution.

Switch to a full Kanban system without any planning

Why wrong: Even Kanban requires some level of planning and prioritization.

Mandate a strict waterfall phase gate review

Why wrong: This increases delay and does not address the cause of paralysis.

Assign it to a separate team

Why wrong: The team that creates it should manage it.

Ignore it until the project is over

Why wrong: This leads to system failure.

Ban all technical debt

Why wrong: Some debt is inevitable; it must be managed.

To enforce the rules of the company

Why wrong: Coaches guide the team to find their own best practices.

To act as the project manager

Why wrong: The coach focuses on process, not project administration.

To perform the technical coding tasks

Why wrong: Coaches don't typically do the core technical work.

Command and Control

Why wrong: This is outdated and non-agile.

Ad-hoc Decision Making

Why wrong: This lacks consistency and accountability.

Full Documentation

Why wrong: This creates unnecessary friction.

Commit to the feature immediately and learn as they build

Why wrong: This is risky and likely leads to poor quality.

Reject the feature request until they are experts

Why wrong: This blocks value delivery.

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

Why wrong: This bypasses the team's need to learn and grow.

Portfolio Management

Why wrong: Portfolio management is high-level alignment.

Governance Framework

Why wrong: Governance ensures compliance, not lifecycle selection.

Team Roles

Why wrong: Roles define responsibility, not lifecycle.

The preferred color of the workspace

Why wrong: This is irrelevant to lifecycle.

The office location of the stakeholders

Why wrong: Location is a factor, but not a primary driver of lifecycle choice.

The board looks too crowded.

Why wrong: A crowded board is a symptom, but metrics are the definitive proof.

The team is having too many meetings.

Why wrong: Unrelated to WIP limits.

The team members are complaining about stress.

Why wrong: Subjective; look at the metrics.

It reduces the need for salary increases.

Why wrong: Unrelated to Lean flow.

It increases the number of people available for specialized tasks.

Why wrong: T-shaped skills focus on breadth, not specialized depth.

It makes documentation unnecessary.

Why wrong: It does not replace the need for documentation.

Hire more senior developers to review code.

Why wrong: Does not address the flow bottleneck.

Eliminate code reviews.

Why wrong: This violates the principle of 'Build Quality In'.

Schedule all reviews for the end of the week.

Why wrong: This creates a huge batch and more wait time.

Automated regression testing.

Why wrong: This is a value-add activity.

Pair programming sessions.

Why wrong: Pairing is a quality-building activity.

It reduces the cycle time of the entire system.

Why wrong: It actually increases wait time at the bottleneck.

It has no effect on the system.

Why wrong: It significantly impacts the queue at the bottleneck.

It improves the total throughput of the system.

Why wrong: Throughput is governed by the bottleneck (Theory of Constraints).

Avoid all documentation.

Why wrong: This is irresponsible and ignores the 'pragmatic' principle.

Use the same documentation as the Waterfall team.

Why wrong: This is likely inefficient and not necessarily 'fit-for-purpose'.

Create a new documentation process from scratch.

Why wrong: Leveraging the DA toolkit is more efficient than reinventing the wheel.

Create a separate, long-term project to fix the debt.

Why wrong: This is an anti-pattern; DA advocates for iterative, continuous improvement.

Ignore the debt until a 'system overhaul' phase is authorized.

Why wrong: This leads to system collapse.

Ask the product owner to prioritize only new features.

Why wrong: This ignores the long-term health of the product.

Creating specialized teams that work in complete isolation.

Why wrong: Isolation prevents whole-system optimization.

Assigning one manager to oversee each individual team member.

Why wrong: Micromanagement is not a Lean system strategy.

Create a standard process and enforce it.

Why wrong: This is anti-DA.

Mandate that all teams use the 'Agile' lifecycle.

Why wrong: This is a one-size-fits-all approach.

Take over their process decisions.

Why wrong: Teams should own their process.

Leave it to the Product Owner

Why wrong: PO manages scope, not architecture.

Ask senior management to decide

Why wrong: Decisions should stay at the team level if possible.

Vote in the team meeting

Why wrong: Technical decisions shouldn't be based on popularity.

Grow Team Members.

Why wrong: This is about individual development.

Improve Team Velocity.

Why wrong: This is about speed, not quality.

Coordinate Activities.

Why wrong: This relates to team synchronization, not quality directly.

Because it's the only way the PMO will approve.

Why wrong: This is not the reason; the reason is team effectiveness.

Because all current processes are already perfect.

Why wrong: No process is perfect.

Because it's the easiest way to do nothing.

Why wrong: DA encourages active improvement.

Teams should rely on external consultants to define their process.

Why wrong: The team should own their process.

Teams should adopt a new framework every quarter to stay modern.

Why wrong: Constant framework swapping is disruptive and anti-DA.

Teams should skip retrospectives to maximize delivery time.

Why wrong: Retrospectives are essential for improvement.