Many novice teams find it difficult to strike the balance between too much and too little detail when writing user stories. User stories often start their lives as big statements of intent with lots of unknowns and that’s okay. For something that’s not going to be developed in the near future it mak...

Recently some of the teams I’m coaching found it difficult to distinguish between acceptance criteria for user stories and the definition of done. Here’s my attempt to make the distinction clear: For a user story or feature to be "potentially shippable" it needs to meet the expectations of the Prod...

One of the teams I have recently coached quickly got a grasp of how to phrase user stories but found it hard to relate to the concept of acceptance criteria. I wrote this short FAQ as an attempt to make it easier for my team to work with acceptance criteria and hope that other teams might find this...