10 Symptoms Your Scrum Team is Broken, Part 1
How do you tell if your Scrum Team is broken? Here are 10 symptoms there might be something wrong…
A Sprint Goal provides a unifying idea to rally around while developing during a Sprint. It is the “north star” for the team to follow.
How do you tell if your Scrum Team is broken? Here are 10 symptoms there might be something wrong…
In the fourth installment of my blog series on “More Agile Great Debates,” I dive into another five topics that people like to argue about.
My previous “Great Agile Debates” have proven extremely popular, so I thought I would add to this body of knowledge with a new blog series.
Scrum Teams without formal training are apt to make tons of mistakes because they don’t have experience or guidance. Here’s what can happen.
Not delivering a “done” increment at the end of a Sprint can cause many negative consequences. It’s a bad habit and won’t make anyone happy.
There should be no “special” Sprints in Scrum. The goal of every iteration is to create a working increment that is potentially releasable.
While Scrum is a flexible framework, it isn’t Scrum unless you have all the components, so NO, it’s not okay to skip some Scrum events!
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?
I can’t tell you how many organizations I have worked with that had employees who confused the Sprint Review with the Sprint Retrospective.
What’s the purpose of a Sprint Review? I’ve seen tons of confusion about the reason for this critical agile event. Let me help clear this up.