I received some really great feedback on the first rendition of my User Story Maturity Model, so I’ve updated it to reflect that feedback. I named it the “Bradley” User Story Maturity Model because I don’t want anyone getting the impression that this is some sort of official thing. It’s my own creation, for better or worse. All feedback(both positive and negative) welcome and appreciated!
In this article, I describe the 2nd version of the Bradley User Story Maturity Model to help teams assess their usage of the practice and identify areas for improvement. You won’t find this anywhere else, because this model is a Charles Bradley original. I base this model on the most credible User Story literature as well as on my experiences coaching Scrum Teams. The model’s best practices are listed in a particular order that represents a strategic path for teams looking to advance their User Story Maturity. While the model doesn’t cover everything, and it is no guarantee of success, it should help teams progress their skills and practices.
|3*||3 Components and 2 Must Haves|
|2||No Stories more than 5 days in size**|
|2||Constant PO interaction|
|1||PO 100% Allocated|
|1||PO Co-located (Talking Distance)|
|2||Weekly Story Grooming|
|2||Story Tests Defined before Development Begins|
|1||Immediate Story Signoff|
|2||All Stories Sized to 2-3 days|
|4||Story Tests 90+% automated
(for all current stories)
For details and to see how your team rates in the scale, please see the link to the full article below.