Sprints, board and metrics

• Sprint lifecycle. A sprint is Created, Active, then Closed or Cancelled, with one active sprint per project. Closing a sprint asks what happens to unfinished work. Each sprint has planned and actual dates and an overdue signal, and can be archived.
• Target version. A sprint can name the version its work goes into.
• Board. One column per status. Dragging a card moves the issue, and the workflow still applies.
• Backlog versus unplanned. The backlog is work not yet started; unplanned is work in no sprint. Quasar keeps the two apart.
• Metrics, computed when you look. Sprint report, burndown, velocity and cumulative flow.
• Workload. Each person's load against an even share of the sprint's capacity. An over-capacity signal warns and never blocks.