4.5.17 Glossary (Technical Debt - User Story Creation)

Focusing on long-term code implications, testing, conflict models, and requirement formats.

• Technical Debt: Implied cost of rework from suboptimal technical choices. Practical Context: Cutting corners technically creates future work (debt) that needs managing.
• Test Plan: Document outlining testing strategy. Practical Context: Defines approach, scope, resources for testing activities.
• Thomas-Kilmann (Conflict): Model describing five modes for handling conflict. Practical Context: Helps understand different approaches to conflict and choose appropriately.
• Throughput: Number of work items completed per unit of time. Practical Context: Key flow metric measuring completion rate.
• Time box: Fixed period of time for an activity. Practical Context: Used for iterations, meetings, spikes to enforce focus and cadence.
• Tuckman (Team Stages): Describes stages teams typically go through. Practical Context: Helps understand team dynamics and tailor leadership.
• User Story: Small requirement description from user perspective. Practical Context: Common agile format ("As a [user], I want [goal], so that [benefit]") focusing on value.
• User Story Creation (3Cs): Collaborative approach (Card, Conversation, Confirmation). Practical Context: Emphasizes discussion and shared understanding over detailed documentation alone.