Planning Cycle

Origin & evolution

The planning cycle formalises the time-boxing at the heart of agile delivery. The fixed-length iteration comes from Scrum and Extreme Programming in the 1990s; nesting sprints inside a longer cadence — the Program Increment — comes from the Scaled Agile Framework. Each treats a bounded interval as the unit that work is committed to and reviewed against.

The UPG's contribution is to make that interval a first-class node, orthogonal to the product breakdown and shared across a portfolio🧸PortfolioPortfolioA grouping of products by strategic axisView reference →. Because a planning cycle is portfolio-shared, the same quarter or increment can be reasoned about across several products at once, instead of living implicitly inside one team's project-management tool.

How it works in practice

A team creates a planning cycle for each real cadence box and nests finer cycles inside coarser ones: sprints inside a quarter, quarters inside a Program Increment. Stories are scheduled into a cycle with planning_cycle_schedules_user_story, and the objectives the cycle serves are attached with objective_scoped_to_planning_cycle.

Scheduling and scoping are deliberate links, not containment. A user story💬User StoryProduct SpecificationA user's goal and the value they expect, in the "As a… I want… So that…" format. Now also a first-class plannable unit (priority, effort, assignee, due_date) that schedules into a planning_cycle, and it round-trips an external board's column via workflow_state.View reference → scheduled into Sprint 24 still belongs to its feature and epic; the sprint simply carries it for two weeks. This keeps two questions independent — how is this product structured, and what is committed when — so neither distorts the other.

Where it fits in the graph

A product runs its planning cycles (product_runs_planning_cycle); cycles nest via planning_cycle_contains_planning_cycle; they schedule user stories and scope objectives and strategic themes🧵Strategic ThemeStrategyA high-level strategic focus area for a planning period. Its own time_horizon is now deprecated: promote the period to a planning_cycle and link the two with strategic_theme_scoped_to_planning_cycle, so themes share one dated, nestable interval instead of a drifting per-theme label.View reference →. Rolling a coarse cycle up through its children answers time-shaped questions — what is committed this quarter, which objectives this increment advances — in a single traversal.

Common pitfalls

The failure mode is the empty cadence box: a planning cycle that neither schedules a story nor contains a finer sub-cycle. A date range with nothing flowing through it is a sprint nobody planned into, or a coarse period never broken down. Either schedule the work it carries or nest finer cycles inside it — otherwise the interval is not yet a real cadence box.