In some cases user stories are enough, but not when the number of user stories begins to grow, or when you develop enterprise systems for banks, insurance, telecom operations, defense or other large scale or regulated industries. If you do develop in these environments, you may be:
- Wrestling with a big pile of technical stories but scrambling to see the big picture and associated business value
- Drowning under the number of tiny stories in your backlogs and struggling to set priorities
- Struggling to create and maintain easily accessible and lightweight documentation for support and maintenance
- Finding it difficult to understand and manage your growing set of test assets.
Things to Produce:
This practice involves the production of a number of requirements, design and test artefacts:
- A use-case based specification of the requirements, stories and test cases
- The realization of the use cases to drive the development of the software
- The generation of tests and test results to test the resulting system and record the results of the testing.
The Use-Case 2.0 Essentials practice requires the team to be skilled in software requirements capture, design, coding, integration and testing.The most important of these are the skills of the customer representative and the analyst as without these the wrong thing may well be developed and tested.
Things to Do:
The Use-Case 2.0 Essentials practice starts by finding actors and use cases, and selecting and prioritizing the parts (slices) of the use cases to be developed. It continues by detailing the use-cases slices and more importantly their tests, and then implementing software to meet the tests. It concludes by executing the tests, tracking progress in terms of verified, working software and feeding back the results in order to handle change and better support the team.