2024-09-20 - Keeping the Sprint backlog clean - Chewing the Fat 📈 #9216
Replies: 50 comments 4 replies
-
|
good to be the first one. |
Beta Was this translation helpful? Give feedback.
-
|
Call me OCD but I think a clean Sprint board is essential to project success. As a Scrum Master, I spend 5 minutes every day before Daily Scrum to make sure it's all nice and tidy |
Beta Was this translation helpful? Give feedback.
-
|
OCD |
Beta Was this translation helpful? Give feedback.
-
|
Awesome video! The examples there have great titles (emojis, prefixes and an infinitive verb ) but another common mistake are vague PBI titles. Of course we have a rule for that: https://www.ssw.com.au/rules/meaningful-pbi-titles 😉 |
Beta Was this translation helpful? Give feedback.
-
|
I think the best thing you can do is listen to your team and do the Adaptation that Scrum suggests. Usually, the issue of the board being a mess is just a symptom of a deeper issue. If the process/board is being neglected, or the process is confusing/messy then change it. If you can't change it, you're fundamentally violating one of the core tenants of Agile (The twelfth tenant) and Scrum. Go back to waterfall. 🤷♂️
https://scrumguides.org/scrum-guide.html#adaptation
|
Beta Was this translation helpful? Give feedback.
-
|
This guy's doing a cited thesis +1 <3 |
Beta Was this translation helpful? Give feedback.
-
|
Great Video @jeoffreyfischer! Killed it mate!
People not attaching tasks to a PBI. This can be a issue when the individual is not on the project full time, meaning that when the task needs to be taken over by another dev (to complete the sprint), it is not clear on the current progress. This sometimes results in a loss of work |
Beta Was this translation helpful? Give feedback.
-
|
The most common issue I've seen is Issues being moved to Done without being Closed. +1 to Sam's comment. |
Beta Was this translation helpful? Give feedback.
-
Vague/unrelated titles. I often get tasks where the title is not like the description
No, but I like Jean's method, might start doing that from now on. |
Beta Was this translation helpful? Give feedback.
-
Issues being moved to Done without being Closed.
As Scrum Master, you must continually communicate with the team, understand the work being undertaken and provide guidance for managing the "paperwork" efficiently. You can't just phone-in the role, especially on non-trivial projects. |
Beta Was this translation helpful? Give feedback.
-
Efforts missing.
Remembering to update the tasks regularly. |
Beta Was this translation helpful? Give feedback.
-
|
Why does it let you set it to done without closing it? Seems like a bug in GitHub 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
Hey I was going to say that |
Beta Was this translation helpful? Give feedback.
-
|
its text in a select box - not a status |
Beta Was this translation helpful? Give feedback.
-
+1 |
Beta Was this translation helpful? Give feedback.
-
TIP: It's extra work, but it's important to compartmentalise all the tasks in PBI to show the scale of the work, because if a PBI does into the next Sprint you can better estimate the work. |
Beta Was this translation helpful? Give feedback.
-
I like to spend a few minutes every morning to go through any of my tickets to make sure they are up to date. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Often times PBIs that lack detail, perhaps because whoever created it intends on completing it
Not for the sprint board necessarily but i think linking PBIs and PRs are essential |
Beta Was this translation helpful? Give feedback.
-
|
Great video @jeoffreyfischer! 🔥 Maybe a hot take but I don't think "estimates" are that helpful or at least not how we do them internally. |
Beta Was this translation helpful? Give feedback.
-
|
This isn't something I see very often because the Marketing Sprint is likely easier than dev Sprints when tasks are unallocated from the beginning. In our team, the PBI is added with all 3 usually from the creation, it doesn't sit in the backlog unallocated or without an estimate. |
Beta Was this translation helpful? Give feedback.
-
Sort of related, but not sizing PBI's correctly, or having PBI's that are too big will cause PBI's to stay on the same status on the board for long periods of time.
If your PBI is blocked, or you are working on another one for whatever reason, move the PBI that you are pausing to another state than in progress. This will keep the board clean and the board will represent what is actually going on in the sprint |
Beta Was this translation helpful? Give feedback.
-
A ridiculous definition of done, causing items to stay on the sprint board for far longer than that should. |
Beta Was this translation helpful? Give feedback.
-
Not enough descriptions and technical details
Consistent titles |
Beta Was this translation helpful? Give feedback.
-
The description and acceptance criteria are not clear enough.
Clean the board during the daily stand-up. |
Beta Was this translation helpful? Give feedback.
-
Underestimated PBIs
Keep documenting any progress or update in the PBI discussions |
Beta Was this translation helpful? Give feedback.
-
|
As I'm not part of a team yet, I haven't joined in on SSW Agile practices, but keen to get stuck in! At my previous workplace we used Trello. My biggest self critical learning was for cards that failed code review etc, that I should move them back to 'in progress' no matter how small the extra work looks - as you never know what will pop up and you don't want the card to sit in a testing/in progress limbo. |
Beta Was this translation helpful? Give feedback.
-
Underestimated PBIs and unclear AC
No other tips |
Beta Was this translation helpful? Give feedback.
-
In SSW.Design, probably not adding a closing comment - cause the estimate and the assignee are defined at the beginning of the Sprint but we sometimes forget to close it properly
Probably just being more intentional in keeping it updated |
Beta Was this translation helpful? Give feedback.
-
No closing comments! I would suggest people write a summary of what was done as a closing comment.
Regular review by PO/SM. |
Beta Was this translation helpful? Give feedback.
-
Statuses of PBIs not reflecting the work
Wipe them down with alcohol |
Beta Was this translation helpful? Give feedback.
-
Not much problems. Our PO doing a great job making sure PBIs are clean
Communicate with Scrum Master and PO more! |
Beta Was this translation helpful? Give feedback.
-
Not keeping PBIs up to date
Updating PBIs as things happen and not waiting until daily. |
Beta Was this translation helpful? Give feedback.
-
The status of PBIs does not change when they are done.
Update the PBIs to reflect the current work. |
Beta Was this translation helpful? Give feedback.
and others
-
Hi Scrum-ers 👋🏻
main rule (where the comments are shown) - https://www.ssw.com.au/rules/defining-pbis/
https://www.ssw.com.au/rules/3-steps-to-a-pbi/
https://www.ssw.com.au/rules/tick-and-flick/
What are the most common problems you see on your Sprint board?
Any other tips to keeping your Sprint board clean?
Beta Was this translation helpful? Give feedback.
All reactions