#68 Four Types of Scrum Work

The podcast explores the complexities of managing work within Scrum frameworks, emphasizing the categorization of tasks into distinct types to enhance team efficiency and alignment with product goals. Four primary work categories are discussed: consumer value work (70-80% of capacity for delivering new or revised features), defect resolution (addressing issues with previously delivered work), team improvement (retrospective-driven activities like process refinement), and backlog refinement (preparing items for development). Unplanned work, such as technical debt or emergencies, is highlighted as a critical but often underestimated category requiring dedicated capacity. Teams are encouraged to systematically track and prioritize these categories to avoid overcommitment and improve historical decision-making. The product owners role in allocating resource investment to value-added work, using velocity metrics, is emphasized, though the team may provide input on priorities.

The discussion also addresses the challenges of refinement work versus value delivery, stressing the need to balance time spent on preparing backlog items with executing deliverables. Refinement is positioned as essential to prevent sprint blockages and ensure tasks meet definition of ready criteria, while excessive refinement risks stalling progress. Techniques like time-boxing research or allocating a fixed percentage of capacity for team improvements (e.g., cross-training or automation) are proposed to maintain focus on both immediate outputs and long-term capabilities. The podcast critiques rigid Scrum practices, advocating for adaptability in handling unplanned work and rework. It also introduces alternatives like earned value management for broader project insights, while acknowledging the limitations of velocity-driven planning in addressing long-term organizational goals. Key risks include over-refinement, inadequate backlog preparation, and misalignment between team efforts and strategic objectives.

• What if you time-boxed backlog refinement to 1 hour per week, using that time to prepare 2-3 user stories for the next sprint

  • Move: Dedicate 1 hour weekly to refining 2-3 user stories using a "definition of ready" checklist (e.g., clarity, dependencies resolved).
  • Why Now?: Unprepared stories often get deferred or blocked, disrupting sprint velocity. This creates a consistent buffer for refinement without overcommitting.
  • Expected Upside: Reduced rework, smoother sprint execution, and faster delivery of high-priority features.

• What if you color-coded your backlog into green (new feature), blue (enhancement), and red (rework) to track velocity by category

  • Move: Label all backlog items with green, blue, or red tags and track sprint velocity by category in your task tracker.
  • Why Now?: High rework rates (e.g., 40-60% of work) signal systemic process flaws. Visibility into rework proportions helps prioritize defect resolution.
  • Expected Upside: Transparent prioritization of value-added work (green/blue) over rework (red), improving stakeholder trust in delivery timelines.

• What if you allocated 5-10% of your sprint capacity as a buffer for unplanned work, treating it as a mandatory time-box

  • Move: Reserve 5-10% of your capacity (e.g., 1-2 hours per day) for unplanned tasks (e.g., technical debt, emergencies), logging them in a dedicated buffer column.
  • Why Now?: Unplanned work (e.g., urgent fixes) disrupts sprint goals and velocity. A buffer ensures capacity for surprises without derailing planned work.
  • Expected Upside: Predictable delivery of planned features, reduced risk of hardening sprints, and better alignment with product owner priorities.

• Time-Box Team Enhancement Work: Dedicate a fixed percentage (5-10%) of your weekly capacity to activities like cross-training, DevOps automation, or process improvement, even if solo. For example, allocate 2 hours weekly to learning a new tool or refining your workflow.
• Track Unplanned Work Explicitly: Reserve 5-10% of your sprint capacity for ad-hoc tasks (e.g., technical debt, urgent bugs). Use a shared document or task tracker to log these, ensuring they dont consume time meant for planned work.
• Time-Box Backlog Refinement: Spend 1-2 hours weekly refining product backlog items (e.g., clarifying requirements, estimating effort) to ensure tasks are ready for execution, even as a solo operator. Avoid over-refining to prevent delays.
• Focus Velocity on Consumer Value: Prioritize tasks that directly deliver user value (70-80% of your capacity) and exclude non-value-added work (e.g., refinement, spikes) from velocity tracking to maintain alignment with stakeholder expectations.
• Categorize and Track Work Types: Maintain a simple spreadsheet or tool to categorize tasks into "value-added," "team enhancement," "refinement," and "unplanned" each week. Use this data to adjust priorities, identify bottlenecks, and improve future planning.