A recent devBetter . com discussion:
"How can we automate moving stories from current to next sprint in Azure DevOps?"
You're trying to automate away pain that is a symptom of a problem with your process.
#AzureDevOps #DevOps #scrum
"How can we automate moving stories from current to next sprint in Azure DevOps?"
You're trying to automate away pain that is a symptom of a problem with your process.
#AzureDevOps #DevOps #scrum
The underlying problem is that you're trying to stuff too much into a sprint. If you're close to accurate, then you should be over half the time and under half the time, and only by a little bit, so there shouldn't be enough work to require automation.
If you have enough work that you need to automate it, then probably you're over more than half the time and by more than a story or two.
If that's the case, the solution isn't automation, it's putting fewer things in your sprint.
If that's the case, the solution isn't automation, it's putting fewer things in your sprint.
Minimize WIP and optimize for flow.
Sadly it's probably outside of your control how much goes into a sprint, but to the extent you have some say in it, push for fewer things. And point out it's a fallacy for stakeholders to think they're going to get more done if they try to overfill the sprint.
The opposite is actually true - because you're spending more time managing stories and that time would have been spent on delivering them.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
