There’s no planning in Agile – is there?
It’s a common misconception that there’s no planning in Agile (there is), and the Product Owner is responsible, but a lot can still go wrong.
User Stories
What is an Agile User Story? A User Story is a statement, written from a user’s perspective, about a specific capability s/he needs to achieve a goal.
When your Agile Requirements go Wrong, Part 4
In the fourth and final blog in this series on what happens when Agile requirements go wrong, I tackle the final four anti-patterns.
When your Agile Requirements go Wrong, Part 2
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.
When your Agile Requirements go Wrong, Part 1
The problem of Agile requirements going wrong is endemic; this is the first of a four-part series on what can go wrong, and how to fix it.
Six Perils of a “technical” Product Owner
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.
Five ways to screw up your Product Backlog
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.
When Product Owners cause Scrum Events to go Bad
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.
Who owns Quality on a Scrum Team?
Unfortunately, quality is often skipped or overlooked when developing products using an Agile approach. So, who owns quality in Scrum?
Debate #18 – How are defects best handled in Agile?
In Agile, defects can be handled in different ways – so what should you do when you discover a bug? Find out how to handle defects in Agile.
Debate #13 – Is it OK to add items to the current Sprint?
So, can you add items to the Sprint Backlog during the Sprint? The Scrum Guide states that you can, but you may not want to do it. Learn why.