Sprint Planning & Issue Tracking

Sprints turn vague roadmaps into executable commitments

A sprint is a fixed time period (usually 1-2 weeks) in which a team commits to completing a specific set of work. The discipline of the sprint — the commitment, the review, the retrospective — is what makes teams get dramatically faster over time.

The Bug Tracker module

While Projects handles general work, the Bugs module is specifically designed for software development teams. It has:

• Issue Projects — Repositories or product areas (e.g., "Backend API", "iOS App")
• Issues — Individual bugs, features, or tasks with type (Bug, Feature, Task, Improvement, Question)
• Sprints — Time-boxed work periods with start/end dates and a status

Issue priority levels

• Critical — Production is down. Drop everything.
• High — Significant impact. Fix in current sprint.
• Medium — Important but not urgent. Plan for next sprint.
• Low — Nice to have. Backlog until bandwidth allows.

Sprint planning in 30 minutes

1. Review all unresolved issues ordered by priority
2. Estimate time for top items (in points or hours)
3. Commit to what can realistically be done in the sprint period
4. Create the sprint and assign issues to it
5. Review daily via the issue list filtered by current sprint