Know when it will really be done.

Kanban: flow, measured

Drag cards across your columns. PtahCast records when work starts and finishes, so the board feeds the forecast without any extra effort.

• Columns of your own, with work-in-progress limits that warn you before the team overloads.
• Started and finished dates are recorded when you move a card.
• Flow metrics: throughput, cycle time, work item age and cumulative flow.
• A live answer to "when will the backlog be done?" at the top of the project.

Sprints, without the story points

Time-box the work in iterations with a name, a goal and a first and last day. PtahCast tells you the chance the open tickets finish in time.

• Plan, start and close iterations. Open tickets roll to the backlog or the next one.
• The committed count is recorded when the iteration starts.
• "Will it finish?" is calculated from your own throughput history, not from estimates.
• Velocity is simply tickets finished per closed iteration.

There are no points or estimates anywhere in the app. That is deliberate.

Waterfall: phases, milestones and a forecast for each

Epics become phases with start and due dates. Chain them with dependencies, add milestones, and see how likely each date is to hold.

• Finish-to-start dependencies between epics, with loops refused and date overlaps flagged.
• Milestones with a date, notes, and an optional epic that must be done by then.
• Per epic: 50% and 85% finish dates, the chance of meeting the due date, and the 85% slip in days.
• Project end at 50, 70, 85 and 95%, the longest chain, and the chance of hitting each milestone.

Epics that do not wait for each other are shown side by side. They are not made to share the team's capacity.