- Häftad (Paperback)
- Antal sidor
- Cohn, Mike
- 235 x 180 x 17 mm
- Antal komponenter
- 580 g
Du kanske gillar
User Stories Applied: For Agile Software Development
Fri frakt inom Sverige för privatpersoner.
- Flexible, quick and practical requirements that work
- Save time and develop better software that meets users' needs
- Gathering user stories -- even when you can't talk to users
- How user stories work, and how they differ from use cases, scenarios, and traditional requirements
- Leveraging user stories as part of planning, scheduling, estimating, and testing
- Ideal for Extreme Programming, Scrum, or any other agile methodology
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
Boston, MA 02116
Passar bra ihop
De som köpt den här boken har ofta också köpt Essential Scrum: A Practical Guide to the Most ... av Kenneth S Rubin (häftad).Köp båda 2 för 838 kr
Fler böcker av Mike Cohn
Bloggat om User Stories Applied: For Agile Software ...
Mike Cohn is the founder of Mountain Goat Software, a process and project management consultancy and training firm. With more than twenty years of experience, Mike has been a technology executive in companies ranging from start-ups to Fortune 40s, and is a founding member of the Agile Alliance. He frequently contributes to industry-related magazines and presents regularly at conferences. He is the author of User Stories Applied (Addison-Wesley, 2004).
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.Salespersons.Domain Experts.The Marketing Group.Former Users.Customers.Trainers and Technical Support.Business or Systems Analysts.What to Do When Working with a User Proxy.Can You Do It Yourself?Constituting the Customer Team.Summary.Developer Responsibilities.Customer Responsibilities.Questions.6: Acceptance Testing User Stories.
Write Tests Before Coding.The Customer Specifies the Tests.Testing Is Part of the Process.How Many Tests Are Too Many?The Framework for Integrated Test.Types of Testing.Summary.Developer Responsibilities.Customer Responsibilities.Questions.7: Guidelines for Good Stories.
Start with Goal Stories.Slice the Cake.Write Closed Stories.Put Constraints on Cards.Size the Story to the Horizon.Keep the UI Out as Long as Possible.Some Things Aren't Stories.Include User Roles in the Stories.Write for One User.Write in Active Voic...