Session 3.3 - Building a Balanced Plan

Chapter 5: The Development Plan | Duration: 1 hr

Learning Objectives

By the end of this session, you will be able to:

  • Define a balanced plan and why it prevents schedule problems
  • Identify signs of unbalanced workload and how to fix them
  • Apply TSPi guidance on task size (≤ ~10 hours)
  • Explain planned value as a tracking tool

Introduction

Chapter 5 links plan quality to schedule success. A balanced plan distributes work realistically, uses fine-grained tasks, and tracks progress with meaningful measures like planned value.

What is a Balanced Plan?

  • Workload fits the schedule and staff capacity
  • Roles and skills are matched to tasks
  • Tasks are small enough to estimate and track
  • Unplanned work allowance is included

Balancing Workload

Scheduling problems often come from overloading a few engineers. Balance avoids idle time for some and overtime for others.

Symptom Impact Fix
One or two people overcommitted Schedule slips; quality drops Redistribute tasks; pair work; adjust scope
Large tasks assigned to single owners Late visibility on progress/risks Split tasks; share ownership; add checkpoints
No buffer for unplanned work Frequent fire drills; overtime Reserve small weekly allowance per Chapter 5

Task Granularity (≈10 hours)

TSPi requires task estimates at ~10 hours or smaller. Finer tasks improve estimate accuracy, reveal risk early, and simplify replanning.

Planned Value & Tracking

Planned value (earned value) connects schedule and work completion. Chapter 5 provides examples of calculating planned value to understand whether the team is ahead or behind.

Planned Value Basics
  • Assign planned value to each task (often equal to its planned effort)
  • Earn value as tasks complete (or proportionally as milestones are hit)
  • Compare earned vs. planned to spot variance early

Summary

  • A balanced plan avoids overload, aligns skills, and includes buffer for unplanned work.
  • Keep tasks small (~10 hours) for realistic estimates and visibility.
  • Use planned value to measure progress and expose schedule variance early.
  • Redistribute work when imbalance appears—don’t wait for late-phase crunch.