Active Sprint board and marking stories that were carryover or pulled into the sprint

[Neil Wills]

I know there are sprint burn down, sprint review reports to know what was pulled in or what stories carried from sprint to sprint.

When we do a daily stand up,

We focus on the sprint goal health

then we look at the other stories that the team committed to outside the sprint goal

Stories may have carried over from one sprint to another.

Some team members may be in pull status and pull in scope if the sprint goal and other commitments are achieved.

The scrum master would like to review the active sprint board, and have a sense for what was pulled in, and what has carried over into the sprint during the sprint without using the burned down report.

I solved this by tagging the sprint goal items, the sprint commitment items, and anything that has carried over multiple sprints. We are trying to avoid carrying over stories over multiple sprints with a move to close out stories at the end of sprint that we commit to.