Bandwidth Issue
I have a situation in which QE is working on 8,8 pointer two left out user in the current sprint and developers 2 out of 3 don't have any user story to work in the current sprint. So, I advised them to pick from backlog and keep it in backlog because only 2 days left for the sprint to complete and QE's don't have bandwidth so they won't be able to complete the user story if new user story is pulled in the current sprint.
My question is
Is it a right approach to ask dev to work from the backlog user story or should I pull the new user story in the current sprint knowing that it will lead to spill over?
It seems to me the real issue isn’t whether to pull more work, but whether the Scrum Team is focused on achieving a usable Increment and meeting the Sprint Goal.
Scrum isn’t about keeping individuals busy; it’s about the entire Scrum Team being accountable for delivering value. Everyone is responsible for the Increment and quality, not just the QE role. If some Developers have availability while others are bottlenecked, then the team should swarm on the unfinished work. That can mean pairing, automation, exploratory testing, or simply helping QE complete what’s needed.
Pulling in new stories with two days left only increases the risk of spillover and distracts from what matters: finishing what’s needed for the Sprint Goal. A transparent Sprint Backlog shows what is achievable in the Sprint, not a holding place for “extra” work.
In short: the right approach is "all hands on deck" to get to Done. Get into the mindet that every Sprint might be your last.
All the best.
Thanks @chris it helped. :)
I advised them to pick from backlog and keep it in backlog because only 2 days left for the sprint to complete and QE's don't have bandwidth so they won't be able to complete the user story if new user story is pulled in the current sprint.
Which backlog did you advise them to pick from? If it's the Product Backlog, it might be wiser to spend the time refining it.
"Get into the mindet that every Sprint might be your last."
That actually sounds like a very bad advertisement for Scrum to be honest.
You know, anxiety, so on.
Idk Chris, how long have you lived from invoice to invoice?
That actually sounds like a very bad advertisement for Scrum to be honest.
You know, anxiety, so on.
Idk Chris, how long have you lived from invoice to invoice?
Allow me to clarify. My statement wasn't about about fear or anxiety. It’s about urgency and intentionality. I've seen too many teams treat Scrum like an infinite treadmill. When we assume there’s always another Sprint, we delay improvement, skip feedback, and roll work forward endlessly.
Also, I’ve done my fair share of invoice-to-invoice living, which is exactly why I don’t take time, value, or opportunity for granted.
All the best.