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.
user story
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.
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.
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?
Debate #4 – What’s the best way to write Acceptance Criteria?
There are many ways to document Acceptance Criteria for your user stories. But what’s the best way? Check out some different methods.
Debate #3 – Is there a “right” way to write User Stories?
Is there is a “right” way to write User Stories? It sounds simple, but like Agile, User Stories are easy to learn but difficult to master.