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 are User Story Acceptance Criteria? They are the conditions that define the boundaries of a what “done” solution looks like. Check out this collection of blogs on the topic.
The right way to write User Stories is from a user’s perspective, taking a thin vertical slice through all the horizontal system layers.
I have long advocated that Scrum Teams have a “Definition of Ready”; if you don’t have one, there are many potential negative consequences.
A “Definition of Done” is a commitment to deliver a working increment meeting defined quality criteria to ensure the increment is complete.
No User Story is complete with Acceptance Criteria; they provide the conditions that must be met, and are critical to agile project success.
The Definition of Ready confirms the suitability of a User Story for development. If you want to produce quality increments, 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.
A partnership between a Project Manager and a Business Analyst is key to a successful project. Learn ways you can work well together.
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.
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.
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.