Stories

A story belongs to a sprint scope and can have an assignee, priority, estimate and due date. Its status moves through backlog, in progress, in review, blocked and done as the team works. The status board is the shared place to inspect the current position of work without losing the sprint context.

• Starting record. A story belongs to a sprint scope and can have an assignee, priority, estimate and due date.
• Named owner. Team Member updates assigned work; Project Manager manages priority and blocker follow-up.
• Current position. The status and linked records tell the team where attention belongs next.

Agree when the team moves a story into review and who decides that it is done. Keep the sprint scope link accurate when priorities change. Set an assignee before expecting an individual to act, and use the blocked state when work cannot proceed. Estimates and actual hours support a practical discussion about effort.

Give the team a shared rule for when a story enters review and when it is marked done. The Project Manager checks the sprint scope before reassigning work. If a blocked story is linked to an impediment, keep the two statuses current so the board reflects the actual next action.

A developer starts a high priority story in the current scope. A dependency stops progress, so the story is marked blocked. The Project Manager sees it in the blocked queue and checks the impediments for the same project and follows up with their owners. After the owner resolves the issue, the assignee resumes the story, sends it for review and marks it done after the team accepts the work.

The Project Manager checks the blocked story’s assignee and sprint scope, then opens the impediment for the same project. The assignee waits for the owner to resolve the problem before moving the story back into progress. The story can enter review when the work is ready; its status board then shows the next handoff.

• Task Board by Status — Stories grouped by their current work status.
• Blocked Stories — Work needing follow-up before progress resumes.

See sprint planning for the planning handoff and review and approval for the decision record. Begin with a small project in implementation, then compare the team’s results with the data model.