Reviews

This approach is from Agile User-Centered Design. Stories can also be added to Scrum. Extreme programming, XP, centers on testing, automated and acceptance. The testing is for usability, performance and stress rather than code coverage. There are various techniques used for developing the stories. They are modular for estimation and testability. A case is shown for a workshop having user role cards and story cards. A story card is a reminder of features to discuss. Each bug report is considered its own story. The planning game customer prioritizes their user story cards for the next iteration after developers have indicated the effort estimations for each. Tests are prepared prior to the code. Stories are grouped. A paper prototype is created and refined before programming begins. The UI is postponed for as long as possible. User goals can be listed from which stories will be derived. Burndown charts are used to track iteration hours. Another measure of momentum is the number of story points over time where each is an estimate for an ideal workday. The term smells is used for problems between participants, e.g. customer won’t do the stories, for which solutions are proposed. There are four parts beside an appendix on extreme programming. Each has a chapter summary, responsibilities of the developer and customer, and questions. 

This is the best book on requirements I have ever read. It completely knocked my socks off!