When breaking down a large user story to ensure it is sized appropriately, the default is to use Richard Lawrence’s excellent 9 Patterns for splitting a user story. I also use an additional approach; in the first instance I look to see whether it can be split along its acceptance criteria. Every goo...

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...