Refinement ConDa

Improvements for Refinement and Planning

Workflow ConDa

Action item team retro 04 Jun 2024 → inspect and adapt after some weeks e.g. 25 Jun 2024

muss ich moderieren! Wie sorge ich für Schwung, speed, Detailbesprechung? Wo muss ich bei Jira clicken?

Refinement + Check in Planning

• In general: Go more into detail in the refinement.
• In general: Don't create monster stories with numerous subtasks.
• Look at the content of a story:
  • Does it add value on its own? = story
  • If not = subtask
• Make external dependencies visible --> because they entail higher risks.
• Make need for clarification with stakeholders visible:
  • What needs to be aligned
  • Who is responsible to do that?
• Try to make stories smaller/split, but not just for the sake of cutting smaller! They should still create value to our users

Planning

• Be strict: Take nothing which needs to be clarified into the sprint
• Clarification as an own task.

ConDa Refinement and Story Point Estimation Guide

Preparation for the Refinement Session

1. Structure and Efficiency:

• • Clear agenda
  • Timebox each section (e.g., Story discussion 5-10 min, Estimation 3 min per story)
  • Set expectations for participation

2. Stories Readiness:

• • Move stories to "Ready for Refinement"
  • Ask the team to read stories in advance

3. Focus Areas:

• • Concrete discussion of each story
  • Identify and document necessary implementation steps (Sub-Tasks)
  • Conduct story point estimation

4. Roles:

• • You: Moderator, guide estimation, ensure structured flow
  • Marike: Content owner, focus on discussion

Refinement

KeyBenefits of Refinement & Estimation

Refinement Benefits

• Clarity & Alignment– Ensures shared understanding before development.
• Better Planning– Identifies risks, dependencies, and necessary clarifications.
• Work Breakdown– Splits large stories into manageable, value-driven pieces.
• Higher Efficiency– Reduces rework by defining clear requirements early.

Estimation Benefits

• Realistic Sprint/Iteration Planning– Aligns workload with team capacity.
• Better Forecasting– Improves predictability and velocity tracking.
• Risk Mitigation– Highlights complex or unclear stories early.
• Team Collaboration– Encourages discussion and shared responsibility.

Objective Refinement

• Purpose: Discuss and estimate stories for the upcoming sprint/iteration
• Goal: Achieve clarity and consensus on Story Points.

Steps

1. Discuss story details.
2. Define necessary subtasks.
3. Estimate Story Points using the agreed scale.

EstimationScale

• 1: Trivial
• 3: Manageable
• 5: Medium complexity
• 8: Complex, challenging

Participation Expectations

• Read stories in advance.
• Share your perspective in discussions.
• Support consensus in estimations