Plans that survive contact with the week.
Sprints bound work by time. Milestones bound it by outcome. Dependencies say what has to happen first. Krrim keeps all three as the different things they are.
- Sprints and burndown
- Milestones
- Dependency graph
- Critical path
Sprints and milestones are not interchangeable
Using milestones as sprints makes velocity and burndown meaningless — the charts still render, they just stop meaning anything.
Sprints — bounded by time
The next two weeks. Ends when the dates run out; unfinished work rolls forward. Measured by velocity and burndown.
Milestones — bounded by outcome
Version 2.0. Ends when the thing ships; unfinished work stays in it and the milestone is simply late — which is the information you wanted.
Record what is actually in the way
Blocks and is blocked by
Link from either side; Krrim stores one edge per relationship, so you cannot accidentally create the same dependency twice.
Learn moreCycles refused by name
A link that would close a loop is rejected, and Krrim names every task in the cycle rather than saying "invalid".
A blocked badge that clears itself
It goes away when the last blocker closes, and the assignee is told — one of the few moments genuinely worth interrupting someone for.
Critical path that will not guess
Tasks with no dates and no estimate are marked unscheduled and left out. People replan around a critical path, so a confidently wrong one is worse than none.
Recurring work
Weekly reports, monthly reviews. Wall-clock times in your timezone, and month-end clamps rather than skipping February entirely.
Learn moreEstimates and time logged
Estimate up front, log time as you go, and compare the two in reports rather than in an argument.
The shape of a fortnight
Plan
Pull from the backlog until the sprint holds about what the team finished last time. That number is your velocity.
Start
Starting the sprint sets the burndown baseline, so the chart measures against what you committed to.
Work
Standups surface blockers daily. Stuck work escalates on its own rather than waiting to be noticed.
Close
Decide what happens to unfinished work — next sprint or back to the backlog — and read the velocity you actually achieved.
Questions people ask
- Can a task be in both a sprint and a milestone?
- Yes, and usually it should be. Milestones describe what you are shipping; sprints describe the fortnight you are in.
- Why is our critical path empty?
- Because too few tasks on the chain have a start date, a due date or an estimate. Krrim lists exactly which ones are unscheduled rather than inventing durations for them.
- What happens to unfinished work when a sprint closes?
- You choose — move it to the next sprint or return it to the backlog. Nothing is decided for you, and nothing is silently dropped.
Plan the next two weeks properly
Sprints, milestones and dependencies are all there on day one — no plugin, no configuration project.
Free to start · No credit card required