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. Mike Cohn. 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 Estimating and Planning.
Frequently Discussed Topics. Getting Started. An Example. Mixed Priorities. Risky Stories. Prioritizing Infrastructural Needs. Selecting an Iteration Length. From Story Points to Expected Duration. The Initial Velocity. Creating the Release Plan.
User Stories Applied: For Agile Software Development - Mike Cohn - Google книги
Iteration Planning Overview. Discussing the Stories. Disaggregating into Tasks. Accepting Responsibility. Estimate and Confirm. Measuring Velocity. Planned and Actual Velocity. Iteration Burndown Charts. Burndown Charts During an Iteration. User Stories Aren't Scenarios. Verbal Communication. User Stories Are Comprehensible. User Stories Work for Iterative Development. Stories Encourage Deferring Detail.
User Stories Applied: For Agile Software Development
Stories Support Opportunistic Development. User Stories Encourage Participatory Design. Stories Build Up Tacit Knowledge. Why Not Stories?
Comment for use in SAMS context:
Stories Are Too Small. Interdependent Stories.
Too Many Details. Thinking Too Far Ahead. Splitting Too Many Stories. Customer Has Trouble Prioritizing.
Customer Won't Write and Prioritize the Stories. Scrum Is Iterative and Incremental. The Basics of Scrum. The Scrum Team. The Product Backlog. The Sprint Planning Meeting. The Sprint Review Meeting. The Daily Scrum Meeting. Adding Stories to Scrum. A Case Study. Handling NonFunctional Requirements. Paper or Software? User Stories and the User Interface. Retaining the Stories. Stories for Bugs.
The Project. Identifying the Customer. Identifying Some Initial Roles. Consolidating and Narrowing. Role Modeling. Adding Personas. Stories for Teresa. Stories for Captain Ron. Stories for a Novice Sailor. Stories for a Non-Sailing Gift Buyer. Stories for a Report Viewer.
- Best Value Purchase.
- User Role – SAMS Project?
- Ideas Under Fire: Historical Studies of Philosophy and Science in Adversity?
- April Fools Pranks: 31 Pranks for the Office?
- A.D.A,M. Interactive Anatomy Online Student Lab Activity Guide;
Some Administration Stories. Wrapping Up. The First Story. Advanced Search. Rating and Reviewing. Finishing the Estimates. All the Estimates. Estimating Velocity.
The Finished Release Plan. The Search Tests. Shopping Cart Tests. Buying Books. User Accounts. Testing the Constraints. A Final Story. The Twelve Practices. XP's Values. The Principles of XP. Appendix B: Answers to Questions. Chapter 1, An Overview. Chapter 2, Writing Stories. Chapter 3, User Role Modeling. Chapter 4, Gathering Stories. Chapter 5, Working with User Proxies. Chapter 6, Acceptance Testing User Stories. Chapter 7, Guidelines for Good Stories. Chapter 8, Estimating User Stories.
- Complete Commentaries on the New Testament (With Active Table of Contents).
- Subscribe to RSS;
- General Messages (1) (The Collected Works of Watchman Nee Book 37)!
- A History of the Indians of the United States (The Civilization of the American Indian Series).
Chapter 9, Planning a Release. Chapter 10, Planning an Iteration. Chapter 11, Measuring and Monitoring Velocity. Chapter 12, What Stories Are Not. Chapter 13, Why User Stories?