Find a copy online
Links to this item
Find a copy in the library
Finding libraries that hold this item...
Details
Additional Physical Format: | Online version: Cohn, Mike, 1962- User stories applied. Boston : Addison-Wesley, ©2004 (OCoLC)607155889 Online version: Cohn, Mike, 1962- User stories applied. Boston : Addison-Wesley, ©2004 (OCoLC)607799184 |
---|---|
Named Person: | Agile Softwareentwicklung. |
Material Type: | Internet resource |
Document Type: | Book, Internet Resource |
All Authors / Contributors: |
Mike Cohn |
ISBN: | 0321205685 9780321205681 |
OCLC Number: | 54365622 |
Notes: | "A Kent Beck signature book"--Cover. |
Description: | xxi, 268 pages : illustrations ; 24 cm. |
Contents: | 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. 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 Voice. Customer Writes. Don't Number Story Cards. Don't Forget the Purpose. Summary. Questions. II: ESTIMATING AND PLANNING. 8: Estimating User Stories. Story Points. Estimate as a Team. Estimating. Triangulate. Using Story Points. What If We Pair Program? Some Reminders. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 9: Planning a Release. When Do We Want the Release? What Would You Like in It? Prioritizing the Stories. Mixed Priorities. Risky Stories. Prioritizing Infrastructural Needs. Selecting an Iteration Length. From Story Points to Expected Duration. The Initial Velocity. Creating the Release Plan. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 10: Planning an Iteration. Iteration Planning Overview. Discussing the Stories. Disaggregating into Tasks. Accepting Responsibility. Estimate and Confirm. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 11: Measuring and Monitoring Velocity. Measuring Velocity. Planned and Actual Velocity. Iteration Burndown Charts. Burndown Charts During an Iteration. Summary. Developer Res. |
Series Title: | Addison-Wesley signature series. |
Responsibility: | Mike Cohn. |
More information: |
Abstract:
Aims to offer a requirements process that saves time, eliminates rework, and leads directly to better software. This work includes end-of-chapter practice questions and exercises, and is useful for software developers, testers, analysts, and managers working with Extreme Programming, Scrum, or any other agile methodology.
Read more...
Reviews
User-contributed reviews
Add a review and share your thoughts with other readers.
Be the first.
Add a review and share your thoughts with other readers.
Be the first.


Tags
Add tags for "User stories applied : for agile software development".
Be the first.
Similar Items
Related Subjects:(7)
- Agile software development.
- Computer software -- Development.
- Logiciels -- Développement.
- Méthodes agiles (Développement de logiciels)
- Agile Softwareentwicklung
- Programutveckling.
- Agile Softwareentwicklung.
User lists with this item (2)
- Agile and Lean Theory and Practice(10 items)
by digger5280 updated 2013-06-09
- Creuna library(1 items)
by drusha updated 2011-02-26