The Great User Story Debate: To Assign or Not to Assign on Agile Teams
Should Sprint Backlog Items (aka User Stories) be assigned to an individual, or left un-assigned? This is my latest Agile great debate.
stories
How to “Slice the Cake” in Agile
The right way to write User Stories is from a user’s perspective, taking a thin vertical slice through all the horizontal system layers.
What happens in Scrum without a Definition of Ready?
I have long advocated that Scrum Teams have a “Definition of Ready”; if you don’t have one, there are many potential negative consequences.
Visual Thinking is something you CAN learn
If you think you’re not good at art, so you can’t use Visual Thinking – think again! Grant and Paddy of The Virtual Jam can teach you how!
What are Acceptance Criteria, and do you need them?
No User Story is complete with Acceptance Criteria; they provide the conditions that must be met, and are critical to agile project success.
What’s a Definition of Ready, and do you need one?
The Definition of Ready confirms the suitability of a User Story for development. If you want to produce quality increments, you need one!
What’s a Definition of Done, and do you need one?
A Definition of Done can vary widely between organizations, departments, and even teams, but it’s crucial that you have one. Find out why.
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.
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?