In A Kanban Card Calculation Problem Other Things Remaining

When working with Kanban cards, it's common to encounter situations where you need to calculate remaining work while accounting for other factors. This guide explains how to approach such calculations, including the formula, assumptions, and practical examples.

Understanding the Problem

In Kanban methodology, cards represent work items that move through different stages of completion. When calculating remaining work on a card, you often need to consider other factors such as:

Dependencies on other cards
Blocked time due to resource constraints
Estimated effort vs. actual progress
Changes in priority or scope

The key is to adjust your remaining work calculation to account for these external factors while maintaining an accurate estimate of the work left to complete the card.

The Calculation Formula

The basic formula for calculating remaining work in a Kanban card when other factors are involved is:

Remaining Work = (Original Estimate - Completed Work) + Adjustment Factor

Where Adjustment Factor = Σ (Dependencies + Blocked Time + Scope Changes)

This formula accounts for:

Original Estimate: The initial estimate of work required
Completed Work: Actual work done so far
Dependencies: Additional time needed due to other cards
Blocked Time: Time lost due to resource constraints
Scope Changes: Adjustments for changes in requirements

Note: All time values should be in the same units (e.g., hours, days) for accurate calculations.

Worked Example

Let's walk through a practical example to illustrate the calculation.

Scenario

A development team has a Kanban card with the following details:

Original Estimate: 20 story points
Completed Work: 12 story points
Dependencies: 3 story points (waiting on another team)
Blocked Time: 2 story points (resource constraints)
Scope Changes: +1 story point (additional requirements)

Calculation

Remaining Work = (20 - 12) + (3 + 2 + 1) = 8 + 6 = 14 story points

In this example, the remaining work is calculated as 14 story points after accounting for all factors.

Interpreting Results

The result of your calculation provides several important insights:

Current Status: How much work remains compared to the original estimate
Risk Factors: Whether dependencies or blocked time are significantly impacting progress
Scope Impact: How changes in requirements affect the remaining work

Use this information to:

Adjust resource allocation if blocked time is a major factor
Communicate progress to stakeholders
Plan for potential delays caused by dependencies
Re-evaluate scope if changes are significantly impacting remaining work

FAQ

Q: How often should I recalculate remaining work?

A: Recalculate remaining work at least weekly, or whenever there are significant changes in dependencies, blocked time, or scope.

Q: What if I don't have exact numbers for dependencies or blocked time?

A: Use estimates based on historical data or expert judgment. Clearly note that these are estimates in your calculations.

Q: How do I account for scope changes in my calculation?

A: Treat scope changes as adjustments to your original estimate. Positive changes increase remaining work, while negative changes decrease it.