How to Screw Up Scrum
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.
What are Agile Sprints or Iterations? These are synonyms for a time-boxed period of time for a Scrum Team to complete an agreed amount of work. Learn more.
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.
You can build a high-performing team by setting them up for success, coaching and guiding them along the way – then get out of their way.
A unifying Sprint Goal is an essential part of Scrum; if you don’t have one, you’re no longer using Scrum. Learn why a Sprint Goal is vital.
The concept of a Product Goal is not new, but it wasn’t an official artifact until the 2020 update to the Scrum Guide. Learn more about it!
The Product Owner is the most crucial member of a Scrum Team, but there are some problematic personality traits & behaviors to watch out for.
In the fourth and final blog in this series on what happens when Agile requirements go wrong, I tackle the final four anti-patterns.
There are many ways requirements can go wrong in Agile. In Part 2 of 4, I tackle five more requirements anti-patterns so you can avoid them.
If your Product Owner used to be a developer or has a technical background rather than business experience, you may run into a few issues.
Managing the Product Backlog is a big job, and there are many ways it can go epically wrong. Learn about the top 5 ways you can screw it up.
Have you ever seen a Product Owner cause Scrum events to go bad? I have, and it’s not pretty. Read on to learn what NOT to do if you’re a PO.