Quality

Brings business, development, and testing together before implementation to clarify a story's examples, rules, and edge cases.

Core question: Which examples express business intent, technical feasibility and testable behavior?

• 15-30 min
• 3

Sorts possible causes into categories and creates a shared picture for investigation and next tests.

Core question: Which possible causes and mechanisms could create this observed effect, and how will we test them?

• 30-60 min
• 2-8

Shows which few causes carry the greatest effect and directs attention to the most important levers.

Core question: Which categories contribute most to the measured total burden?

• 30-60 min
• 1-6

Clarifies workflows, data, causes, and improvements by framing the problem precisely, branching possible causes, and defining countermeasures.

Core question: Which evidenced conditions explain the problem and which can we usefully change?

• 1-3 h
• 2-8

Clarifies workflows, data, causes, and improvements by defining scope and process, collecting failure modes, and assigning actions and owners.

Core question: How can a function fail, what effects follow and which actions demonstrably reduce risk?

• 2-6 h
• 3-10

Separates events, evidence, confirmed causes, and fitting actions so analysis does not turn into blame-finding.

Core question: Which evidenced system causes must change so this or a similar event does not recur?

• 1-4 h
• 3-8

Guides improvement work from problem definition through measurement and analysis to controls and lasting transfer.

Core question: How will we improve an existing process through valid measurement, confirmed drivers, and sustainably controlled changes?

• 2-12 Wochen
• 3-10

Coordinates team, immediate actions, root cause analysis, and prevention across eight steps to a verified solution.

Core question: How will we safely contain a material problem, permanently remove verified occurrence and detection causes, and prevent similar cases?

• 1-6 Wochen
• 4-10

Compares work as actually performed with the standard and reveals deviations that improve the process in a targeted way.

Core question: Which safe, quality-capable sequence meets customer takt with the minimum required standard WIP?

• 1-3 h
• 2-6

Paired data points reveal whether two variables move together and where a suspected relationship needs deeper proof.

Core question: What pattern exists between X and Y, and which observations or groups need explanation?

• 30-90 min
• 1-4

Examines how architecture decisions support important quality goals and makes risks and trade-offs visible.

Core question: How does the architecture support our most important quality goals, and where do risks or trade-offs arise?

• Several meetings plus preparation and analysis; total effort depends on scope
• Evaluation team, architects, and relevant stakeholders

Uses concrete tasks to show how well an architecture supports use and change.

Core question: What changes do our planned tasks require, and how do the architecture alternatives differ?

• Preparation, scenario analysis, and findings review; effort depends on scope
• Architecture experts and stakeholders for scenarios and weighting

Helps a small team assess the main quality risks in its software and choose where to investigate further.

Core question: How well does our software meet its quality goals, and which risks should we investigate further?

• 3–4 h for initial assessment; preparation and deeper analysis additional
• 1 or a small team; particularly suitable for 3–4 people