DoingGoodUserStories

This is version 4. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

• their intent) - hogood stories don't seem to mention any specific

Attached Tests

Really good stories can make reference to some tests (we have tried attaching these a secondary card stapled to the story). You don't always get the tests up-front like this (but once in a while you do - and thats great, and should be encouraged). If you don't get some tests up-front don't worry they can be developed with a user over the course of an iteration and incorporated when you are DoingFunctionalTests.

Capturing the Intent ing sure that we record the true intent of a Story: I want to query the trades in a system by specifying the counterparty and instrument "vs." making assumptions that can be used to fit the intent into a deliverable time frame (I will enter the query details into a file). If we capture the intent, then the story can move with the changes in the system and not prevent unnecessary code from being carried around.

Granularity

Half of the purpose of a UserStory is to capture requirements, the other half is to schedule it, so there must be enough detail for the developers to have a go at guessing its cost and, if you follow the C3 line, that cost should be 1, 2 or 3 ideal weeks. One issue we've come across is in DealingWithSmallUserStories that don't seem to fit elsewhere, other than by stapling some together. --SteveFreeman

Structured Or Not?

I think that it's better for a real development to structure in a better way the specification about the requirements about a software products. We must to be on the right way to produced a real software that meet user expectation. --IAP

Please help me..... I do not understand the last statement above.... rcf ..........

Getting your story noticed

OliBye has noticed that his customers have started putting little red stickers on their cards in a effort to get them noticed. It's nice to see that they see the stories as important.

Using stickers for progress

At ConneXtra we use coloured stickers to indicate progress. All stories start out with a red sticker (tasks have blue stickers). Developers can make tasks finished by applying a green sticker. Developers can mark stories as "developer finished" by applying a yellow sticker. Only Customers can mark a UserStory as complete by applying a green sticker when it passes acceptance tests. The nice thing about this scheme is you can quickly see what's complete on the planning board. We used to tick with a marker pen but using stickers for marking progress is easy to reverse if a problem is spotted. - RachelD ³DoingGoodUserStorie