requirements

Turns backlog work, sprint work, and team flow into a tangible result by noting the story, collecting rules, and checking scope.

Core question: Which concrete examples show this story is complete, and what rule connects them?

30-60 min

3-7

Turns customer problems, solution ideas, and evidence into a tangible result through setting the focus question, gathering stakeholders and context, and deriving open questions and next steps.

Core question: Which context, environment, stakeholders, trends, constraints, and assumptions shapes our initiative, and where do the most important open questions arise?

45-90 min

3-10

Turns architecture context, options, and consequences into a tangible result by collecting stakeholder goals, eliciting quality scenarios, and documenting architecture implications.

Core question: Which Quality Attributes with which concrete scenarios are architecture-critical for the system, and in which order must they be addressed?

2-4 h

5-15

Moves backlog, sprint work, and team flow toward a concrete result through "briefly present the story or feature", "collect examples rule by rule", and "hand over the examples as acceptance tests".

Core question: Which concrete examples describe the business logic unambiguously enough to serve as executable tests?

60-90 min pro Feature

3-6

Moves backlog, sprint work, and team flow toward a concrete result through "pin the story summary to the whiteboard", "write the happy path as Given-When-Then", and "copy the criteria into the story tool".

Core question: Which concrete, testable criteria describe the happy path, edge cases, and negative paths of this story so clearly that all three roles share the same Definition of Done?

20-40 min pro Story

3-6

Concrete domain questions define what an ontology or knowledge model must be able to answer and test.

Core question: Which concrete domain questions must the planned model be able to answer so that it is sufficient for the planned use cases and not oversized?

2-4 h

2-8