User stories applied : for agile software development (engelsk)

Del af Addison-Wesley signature series

Mike Cohn (1962-)

Detaljer

...

Beskrivelse

Mike Cohn shows how to build robust software that more closely meets the customer's need through applying the concept of user stories. Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software. The best way to build software that meets users' needs is to begin with "user stories": simple, clear, brief descriptions of functionality that will be valuable to real users. In User Stories Applied , Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing. User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other "proxies" Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach.

Indhold

Seneste udgave, bog

Foreword. Acknowledgments. Introduction. I: GETTING STARTED. 1: An Overview. What Is a User Story? Where Are the Details? "How Long Does It Have to Be?" The Customer Team. What Will the Process Be Like? Planning Releases and Iterations. What Are Acceptance Tests? Why Change? Summary. Questions. 2: Writing Stories. Independent. Negotiable. Valuable to Purchasers or Users. Estimatable. Small. Testable. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 3: User Role Modeling. User Roles. Role Modeling Steps. Two Additional Techniques. What If I Have On-Site Users? Summary. Developer Responsibilities. Customer Responsibilities. Questions. 4: Gathering Stories. Elicitation and Capture Should Be Illicit. A Little Is Enough, or Is It? Techniques. User Interviews. Questionnaires. Observation. Story-Writing Workshops. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 5: Working with User Proxies. The Users' Manager. A Development Manager.- ; Table of Contents Front Matter Foreword by Kent Beck Table of Contents : Introduction Part 1: Getting Started 1. An Overview 2.Writing Stories 3. User Role Modeling 4. Gathering Stories 5. Working With User Proxies 6. Acceptance Testing User Stories 7. Guidelines for Good Stories Part 2: Estimating and Planning 8. Estimating User Stories 9. Planning a Release 10. Planning an Iteration 11. Measuring and Monitoring Velocity Part 3: Frequently Discussed Topics 12. What Stories Are Not 13. Why User Stories? 14. A Catalog of Story Smells 15. Using Stories with Scrum 16. Additional Topics Part 4: An Example 17. The User Roles 18. The Stories 19. Estimating the Stories 20. The Release Plan 21. The Acceptance Tests Part 5: Appendices • An Overview of Extreme Programming • Answers to Questions