User Story Maturity
2011-04-01 02:20:58 GMT
I'm working on a User Story Maturity Survey of sorts, and I'd be interested on others' thoughts.
User Story Maturity Survey
15* 3 Components/2 Must Haves (* Required)
15 PO 100% Allocated to the team as PO
5 PO Co-located(Talking Distance)
10 Weekly Backlog Grooming
10 Multiple Acceptance Testing Styles(4+)
5 Immediate Story Signoff(Within 1 day)
20 Small Stories (2-3 days for one person or a pair)
20 Acceptance Tests 90+% Automated
Score User Story Maturity Level
25-39 Beginning Team
40-89 Intermediate Team
90+ Advanced Team
If you do the practice generally 90% of the time, then give yourself the points for that practice, otherwise don't give yourself any points for that practice (i.e. no partial credit).
-3 Components/2 Must Haves (* Required)
This means every User Story has the 3 required components.
i.e. at least a title, some associated conversations, and acceptance tests/examples defined in at least prose/text.
aka the 3 C's: Card, Conversation, Confirmation
This means that every User Story confirms with 2 Must Have characteristics:
1. The story provides direct value to a non dev team stakeholder (i.e. anyone who is not a dev on the team)
2. The story describes new or changed functionality in the system.
This practice + 10 points garnered from elsewhere, is required to even be a beginning User Stories team.
- Multiple Acceptance Testing Styles
This means the team uses at least 4 styles of expressing acceptance tests. This is simply the conceptual form of an acceptance test(i.e. not an automated test) -- some people call this "Hi gh Level Test Cases".
Some Example Styles are:
"Test that..." ^1
"Test with..." ^1
Specification By Example
Pictures of White boards
Notes/Bullets on an index card
^1 from Mike Cohn's User Stories book
Please let me know if you need further clarification of any of the practices.
Charles Bradley, CSM, PSM I
Experienced Scrum Coach
My blog: http://scrumcrazy.wordpress.com/
To Post a message, send it to: scrumdevelopment <at> eGroups.com
To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe <at> eGroups.com
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured