Agile sprints and backlog management
How SmartERP Project Agile manages sprint life cycles, enforces Definition of Ready, tracks story points and velocity, and controls task execution across Kanban boards.
SmartERP Project Agile (smarterp_project_agile) introduces Scrum and Kanban capabilities directly into native projects. Teams organize tasks into backlogs, estimate story points, enforce quality standards through Definition of Ready checks, and execute sprints with automated velocity tracking.
[projects-sprint-workflow]
Sprint life cycle and states#
A sprint represents a time-boxed iteration (typically 1 to 4 weeks) aimed at delivering a committed set of user stories and backlog items.
[projects-sprint-status]
| State | Description | Permitted actions |
|---|---|---|
Planning (draft) | Sprint dates and goals are defined; tasks are pulled from the backlog into the sprint backlog. | Add/remove tasks, update story points, adjust sprint target dates. |
Active (active) | Sprint is running. Committed hours and story points are frozen. Tasks move across Kanban columns. | Move tasks through workflow stages, log timesheets, raise blockers, complete tasks. |
Closed (closed) | Sprint iteration is finished. Actual velocity and completion rates are permanently recorded. | Review sprint metrics, conduct retrospective, rollover unfinished items. |
Cancelled (cancelled) | Sprint was aborted due to major scope pivot or project pause. | Review rationale, reset to Planning if resuming. |
Warning
Only one sprint per project can be in the Active state at any given time. Starting a new sprint while another is active is blocked until the active sprint is closed or cancelled.
Definition of Ready (DoR)#
When agile_dor_enforced is enabled on the project, SmartERP prevents starting a sprint if any assigned task fails the Definition of Ready criteria:
- Task must have an assigned owner.
- Story points must be estimated (cannot be zero or unassigned).
- Detailed acceptance criteria must be populated in the task description.
- Technical estimate must be approved (if estimation approval is enabled).
If any task fails these checks, pressing Start Sprint halts the transition and displays a detailed refusal message listing each non-compliant task and what is missing.
Sprint execution and metrics#
When a sprint moves to Active, SmartERP automatically freezes baseline metrics:
- Committed Story Points: Total points planned at sprint inception.
- Committed Hours: Total estimated labor hours at sprint start.
During sprint execution, team members update task progress on the Agile Kanban board:
[ Backlog ] -> [ In Progress ] -> [ Code Review ] -> [ QA Testing ] -> [ Done ]When the sprint is closed:
- Completed Velocity: Total story points of tasks reaching the
Donestage. - Completion Rate: Percentage of committed points successfully delivered ($\frac{\text{Completed Points}}{\text{Committed Points}} \times 100$).
- Incomplete Tasks: Prompted for automatic rollover into the next planned sprint or return to the product backlog.