Cycles

Cycles are sprints — fixed-length periods (commonly one or two weeks) during which your team commits to a defined set of tasks. They're optional, but if you run iterative work, cycles are how Workestra measures velocity and forecasts delivery.

Screenshot needed — add an annotated image showing this UI

Creating a Cycle

1. Go to Projects → Cycles
2. Click New Cycle
3. Fill in: name, project, start date, end date
4. Drag tasks in from the backlog (or assign tasks to the cycle directly from the task detail)

Cycle Lifecycle

Cycle Metrics

Every cycle tracks:

• Scope — total tasks committed
• Completed — tasks marked Done
• Burndown chart — daily remaining work over time, with an ideal line
• Velocity — total estimate (story points or hours) completed per cycle
• Predictability — how often you complete what you commit to (see Reports)

Closing a Cycle

When a cycle ends, incomplete tasks need a destination. You'll be prompted to:

• Move to next cycle — carry the work forward
• Return to backlog — re-prioritize later
• Cancel — drop them entirely

Velocity & Predictability

Once you've completed a few cycles, the Reports page surfaces:

• Velocity by team — average completed estimate per cycle, with trend lines
• Cycle predictability — % of committed scope you actually shipped
• Estimate-vs-actual — how accurate your sizing has been

Workestra also uses your cycle history to power Predictive ETAs for ongoing work.

---

Next Steps

• Tasks — assign tasks to cycles
• Reports — velocity and predictability dashboards
• Predictive ETA — forecast completion dates
• Epics — group cycles under a larger initiative