Sprint backlog
Plan with populated active-sprint scope and a prioritised backlog.
Feature
Keep cadence and effort connected to the work record.
Plan sprint scope, record estimates and time, and use delivery reports without exporting the team’s operating context.
How it works
A clear operating path.
Configure the structure once, then use it where the work happens.
- 01
Edit the sprint
Set the sprint goal, dates, and selected work-item count.
- 02
Estimate tickets
Record original and remaining effort on planned work.
- 03
Inspect delivery
Review committed and completed scope in the agile report.
Capabilities
What teams can use today.
These capabilities are implemented in the current TOW product.
Estimates
Keep ticket estimates beside the delivery record.
Worklogs
Inspect who logged time, when it was recorded, and the accompanying note.
Agile report
Compare commitment, completion, and changing scope.
Control point
AI follows the same boundary.
Where AI is enabled, accessible context and review-oriented flows apply to the surrounding workspace rather than bypassing its controls.
- Scoped context
- Configured provider
- Visible proposals
- Human decision
Deployment and security
Control the deployment and the boundary.
Use TOW Cloud, run TOW on controlled infrastructure, or operate an air-gapped Docker Compose deployment. Permissions, identity settings, exports, and AI provider choices stay visible to administrators.
Explore self-hosting
FAQ
Questions worth answering clearly.
Current product, deployment, and commercial boundaries.
Is sprint backlog implemented in TOW?
Yes. Sprint backlog, Estimates, Worklogs, Agile report are part of the current product surface and are backed by the linked implementation evidence.
Can this be self-hosted?
Yes. The capability is available within the TOW application in a configured self-hosted deployment.
See TOW in your environment