5 Ways a Product Owner should NOT Behave, Part 2
In blog two of three, I cover five more ways a Product Owner on a Scrum Team should not behave. Watch out for these behaviors or traits.
User Stories
Told from a user’s perspective, User Stories are short statements of a need, including who, what, and why the feature or functionality is needed.
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 3
The problem of Agile requirements going wrong is endemic; this is the third of a four-part series on what can go wrong, and how to fix it.
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.
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?
Anti-patterns that Doom a Product Owner to Fail
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.
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.
Debate #12 – What’s the best way to estimate User Stories?
Modified Fibonacci, T-shirt Sizes, Dog Breeds, Ideal Days, and Story Counts are different ways to size User Stories. Which one is the best?
Debate #9 – Story size – what’s an Epic, Theme, Feature…?
User Stories may be written at various sizes and levels, and there are different terms for them – so what should you call yours?