Jack Milunsky,
Scrum Master
Simplifying Agile Project Management

AGILE CONSULTING

I have received many requests to assist with Agile training and deployment. I am humbled by your interest and, being a huge proponent of Agile, want to help any way I can by providing consulting where I am able to.

I know a number of other very qualified trainers and consultants who are also willing to help. So if you are looking for assistance, please contact me and I will work with you to get the services you require.


Click Here for More Information

 

Agile project management blog

 

 

Agile project management blog


 

 
Agile project management blog

Check out my white paper.

"How Agile methods resolve chaos and unpredictability in software projects"


 
 

 
Agile project management blog

« Technical stories - are they included on the backlog? | Main | Whose doing your Sprint demos »

October 6, 2010

User Stories defined - notes from the XP forum

I was recently following a thread on the XP forum and one of the responses from Ron Jeffries is worth repeating here for you all to read.

 

"

Um, yes. Or as someone put it long ago, a user story consists of ...
Card
Conversation
Confirmation

The card is just a token used to pass around if one estimates, to
hang on the wall as something to be done, to move around the status
board, and so on.

It is in conversation between PO and team that the team learns what
is really meant. It is here that much of the creativity lies,
converting what the PO originally thought she wanted into the best
idea the team can come up with.

Confirmation, in the most productive teams, consists of concrete
tests, or checks, that show when they pass that the software does
what was agreed it would do. Fastest and most reliable development
seems to happen when a very high proportion of these checks are
automated.



[Some people have the impression that a user story is only #1 or
only #1 and #2. I don't agree, but that's another topic. I don't
think any of the 3 MUST be fully documented, but I do believe all
of the 3 should be well communicated to the dev team.]

Yes. The point is communication. The card serves as a point of
focus, and a status marker. The conversation builds common
understanding and agreement, the confirmation contains the details
of the agreement.

Your detailed test examples are right on point to the original
questions. The one thing that I would add is that it is perfectly
fine to write these story ideas on cards associated with the story,
or on a sheet of paper. The probably do not to be documented further
within the team, and there should probably be no one outside the
team who needs that level of detail.

If the tests are going to be automated -- and generally I recommend
that -- then the test itself serves as perfectly adequate
documentation, especially if written in a FitNesse table or a system
like Cucumber. If the tests are going to be done manually, first go
back to the previous sentence. If there are still tests that need to
be done manually, it may be worth writing them down in a test book
so that you can be sure to do them again, and again, and again, as
regression tests ... which is why automation is so important.

You recommend Mike Cohn's book, and it's definitely a good one. It
is possible to get the impression from it that you should do
everything in there, and it's probably best to do as little as
possible. Start with Card, Conversation, Confirmation. Then, for 99
percent of teams: stay there.

If you're interested in sources, here's an early description of the
ideas, and a darn good one if I do say so myself:

http://xprogramming.com/articles/expcardconversationconfirmation/

Ron Jeffries

 

"

TrackBacks (0)

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a010535ea7534970b01348804eb35970c

Listed below are links to weblogs that reference User Stories defined - notes from the XP forum:

Comments (8)

made me curios, after reading the description i think i am going to take a look on Mike's book too

This is definitely a blog that people need to get behind. The problem is, no one wants to do a great deal of reading and not have something else to stimulate the mind.

Thanks for the link, i followed your link,and found it very interesting and informative that is a good book i can say..I prefer this book and try to learn some thing informative from it..

Completely true, conversation does build common understanding and agreement. The post holds so much truth and logic. I've also extracted a lot of information from the resource category. Thanks, it'll be a pleasure to visit this blog anytime.

Nice work on putting together a very interesting post. Fabulous ideas and very helpful information. Well thought out and well written.

Not only is this a great idea, it is so fun to read the blog to find out about the fun stuff you find!

The problem is, no one wants to do a great deal of reading and not have something else to stimulate the mind.

Highly interesting information shared over here! Keep adding great stuff like this one.

The comments to this entry are closed.

 
 

 

 

 
© 2009 Brighstpark 3.0