Forecast
When the remaining work is likely done, from the project's own pace, how likely a target date is, what slows it down, what happens if one item goes first, and how finished work compared with its due dates.
For: Founder, Product owner, Project lead, Solo builder
How the dates are made
Corpole counts the stories, tasks, defects and subtasks finished in each of the last eight weeks and plays 2,000 possible futures from that pace. The 50% date is as likely to be early as late; the 85% date is the safer promise. Each item counts as one, so splitting large items makes the forecast sharper.
Using it
- Scope: a theme, epic, work package or story code limits it to that item and everything under it; the target defaults to its due date.
- What if this goes first: how soon one item (and what is under it) could be done if the team took it next; the overall end date stays the same.
- What slows it down: blocked items, open questions, items running longer than the usual flow time, items waiting for review or verification, items not refined yet, items past due.
- Plan versus actual: finished items compared with their due dates. Corpole holds no hour estimates; give work items due dates to compare.
- Your agent answers the same with get_forecast, e.g. "when will phase 1 be done?".