What happens when you don’t have a fully cross-functional Scrum Team?
So, you have a Scrum Team. But does your team have all the necessary cross-functional skills to get to a “done” increment each Sprint?
So, you have a Scrum Team. But does your team have all the necessary cross-functional skills to get to a “done” increment each Sprint?
Ideally, your Scrum Team includes full-time people with the right cross-functional skills; but if you have part-timers, you’ll have problems.
In this episode of “More Agile Great Debates,” I tackle five more topics: Generalist vs. Specialist, Quality, Canceling Sprints, and more!
This time on “More Agile Great Debates”: incomplete backlogs, improvements, “special” Sprints, people swapping, and cross-functionality.
Here are my latest five great agile debates: Story Points, Job Titles, Velocity, Project Managers, and Business Analysis. Join the argument!
For agile transformations to succeed, they must have top-down support from executives who really understand what it means to be agile.
I can’t tell you how many times I have seen Scrum go wrong. If you want the perfect recipe for screwing up Scrum, you’re in the right place.
I have worked with good and bad Agile Product Owners, and I found some sure signs that a Product Owner is doomed to fail. Learn what they are.
Agile teams are fully cross-functional so they can create a done increment each sprint. But what does that mean? Explore the official roles.
The Scrum Guide 2020 advises that teams of 10 people or less are small and nimble enough, but that any larger may be less effective.