Timeline and cycle history

Understand how the hill changed over the cycle

The current hill answers “where are we now?” The timeline adds “how did we get here?” By moving through saved snapshots, your team can review the evolution of every scope without reconstructing the cycle from memory.

Replay meaningful project states

The timeline uses your snapshot history. Move through those checkpoints to compare scope positions and see the chart evolve across the cycle.

Because the history is based on deliberate snapshots, each point can correspond to a review, decision, or other moment your team considered important.

Learn from movement, not activity counts

A scope that crosses the top tells a different story from a list of completed subtasks. Reviewing its movement can reveal when the team resolved the central unknown and how much execution followed.

  • Review a cycle with the team
  • Explain major shifts to stakeholders
  • Use past movement to improve future shaping

Keep the current chart simple

History stays available without crowding the working hill. Return to the current view for day-to-day decisions, then open the timeline when you need the wider cycle story.