Operating manual
Personal sprints and shared backlog
Select work per person and period and preserve outcomes.
Before you begin
- Projects enabled; managers edit and operators view personal sprints.
Step by step
Add projects and tickets to the department backlog.
Configure each person’s usual duration and share, then create a sprint with name, goal and dates.
Select activities assigned to that person and compare remaining effort with reserved capacity.
Start the sprint and work on original records.
Close, leaving incomplete work in the backlog or carrying it to a planned sprint for the same person; inspect history.
The result to check
A closed sprint retains titles, statuses, assignments, estimates, time and closing capacity.
Limits and considerations
- Duration 1–366 days; share 0–100%; one active sprint per person/department.
- An activity belongs to one open sprint. Closure does not change ticket/task statuses.
- Estimates and time are activity totals; capacity is compared with remaining work.
Continue with related guides
Break down delivery and retain a plan snapshot.
↗PlanningGlobal planning and forecastsRead tickets, projects and tasks without counting containers twice.
↗AdministrationCalendars, capacity and leaveMaintain consistent availability for forecasts, sprints and expected hours.
↗THE NEXT STEP
Keep following the thread.
Explore the tools or compare plans for your team.