You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have backlog items that need to be watched in daily standup. Currently I have a clumsy method of pulling them into sprint but labeling to make them stand out (and keep the original sprint/backlog info somewhere in text).
Hi @Dennis Lindenberg ,
Would it work keeping them in the sprint using labels (e.g. add label 'mid-sprint') and then creating a swimlane in the scrum board that separates those stories where label = "mid-sprint"? I used a similar method to separate "blocked" stories from others and it seems helpful.
Thanks for the suggestion. I am using a label to differentiate the committed and 'workahead' work in swimlanes.
I am trying to solve the problem of keeping the workahead stories in their original sprints, or backlog, but still show them on the active board. I have to do a hack that changes to the current sprint, but edit the originated sprint in text in the story description. Not elegant and potentially error-prone.
I see... You could create a new Kanban board from a saved filter that looks like this:
project in ("Carlos classic Project") AND sprint in openSprints() AND sprint not in futureSprints() OR labels = mid-sprint
where you use your project name instead of "Carlos classic Project"
Then, yoiu can edit the board settings and create a swimlane for those stories where labels-mid-sprint and another swimlane for everything else
I just tried it and I think it looks like what you're looking for:
Hope it helps,
A good try! While it solves one problem, it creates others. I need to keep my team focused on the Scrum board. The kanban board would be yet another board.
Based upon this and other replies, the rules of a scrum board require items to be in the active sprint, so I'll do the diligence of maintaining the original sprint in the story description. Seems to be working this far.
Thanks for your consideration and thoughts.
I guess a creative quick filter on the backlog view won't help for your stand-ups because you want the status columns that are visible on the active sprint view.
Can you provide more information about this use case? What are the backlog items being monitored for?
Hi Kat, the desire is to differentiate between work committed by the team and stories that were added mid-sprint. We want all work to be visible on the board but be clear about what needs to finish during the sprint.
I can create swim lanes with a simple query based on some flag like a label. The problem is that the basic board query does not specify 'current sprint'. It appears to be a given, so that automatically excludes items that are not in the sprint. I prefer to keep that workahead stuff in the original sprint. Less chance of error, and keeps the plans/backlog intact.
Do you use the Sprint Report? This report can be viewed for the active sprint as well as past sprints.
All the sorties in the current sprint are separated under the headings Completed Issues, Issues Not Completed, and Issues completed outside of this sprint. Any stories added mid-sprint are indicated with an *.