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.
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.
My Scrum Team Doesn’t Want to do some Events
Each event of Scrum has a specific audience and purpose. While skipping some might be tempting, you might want to read this before doing so.
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.
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 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 are Sprint Goals, and why do you need them?
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.
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.
Want to earn the IIBA®-AAC certification?
Do you want to earn the Agile Analyst Certification (AAC) through the International Institute of Business Analysis (IIBA)? Let me help!