De som köpt den här boken har ofta också köpt Python Crash Course, 3rd Edition av Eric Matthes (häftad).
Köp båda 2 för 1212 krAgile requirements: discovering what your users really want. With this book, you will learn to: Flexible, quick and practical requirements that work Save time and develop better software that meets users' needs Gathering user stories -- even when ...
Proven, 100% Practical Guidance for Making Scrum and Agile Work in Any Organization This is the definitive, realistic, actionable guide to starting fast with Scrum and agileand then succeeding over the long haul. Leading agile consultant an...
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).
About the Author xviiForeword by Robert C. Martin xixForeword by Jim Highsmith xxiForeword by Gabrielle Benefield xxvAcknowledgments xxviiIntroduction xxixPart I: The Problem and the Goal 1Chapter 1: The Purpose of Planning 3
Why Do It? 5
What Makes a Good Plan? 8
What Makes Planning Agile? 9
Summary 10
Discussion Questions 10
Chapter 2: Why Planning Fails 11Planning Is by Activity Rather Than Feature 12
Multitasking Causes Further Delays 15
Features Are Not Developed by Priority 17
We Ignore Uncertainty 17
Estimates Become Commitments 18
Summary 18
Discussion Questions 19
Chapter 3: An Agile Approach 21An Agile Approach to Projects 23
An Agile Approach to Planning 27
Summary 31
Discussion Questions 32
Part II: Estimating Size 33Chapter 4: Estimating Size with Story Points 35Story Points Are Relative 36
Velocity 38
Summary 40
Discussion Questions 41
Chapter 5: Estimating in Ideal Days 43Ideal Time and Software Development 44
Ideal Days as a Measure of Size 46
One Estimate, Not Many 46
Summary 47
Discussion Questions 47
Chapter 6: Techniques for Estimating 49Estimates Are Shared 51
The Estimation Scale 52
Deriving an Estimate 54
Planning Poker 56
Why Planning Poker Works 59
Summary 60
Discussion Questions 60
Chapter 7: Re-Estimating 61Introducing the SwimStats Website 61
When Not to Re-Estimate 62
When to Re-Estimate 64
Re-Estimating Partially Completed Stories 66
The Purpose of Re-Estimating 67
Summary 67
Discussion Questions 67
Chapter 8: Choosing between Story Points and Ideal Days 69Considerations Favoring Story Points 69
Considerations Favoring Ideal Days 72
Recommendation 73
Summary 74
Discussion Questions 75
Part III: Planning for Value 77Chapter 9: Prioritizing Themes 79Factors in Prioritization 80
Combining the Four Factors 86
Some Examples 86
Summary 88
Discussion Questions 89
Chapter 10: Financial Prioritization 91Sources of Return 93
An Example: WebPayroll 96
Financial Measures 102
Comparing Returns 108
Summary 109
Discussion Questions 109
Chapter 11: Prioritizing Desirability 111Kano Model of Customer Satisfaction 112
Relative Weighting: Another Approach 117
Summary 119
Discussion Questions 120
Chapter 12: Splitting User Stories 121When to Split a User Story 121
Splitting across Data Boundaries 122
Splitting on Operational Boundaries 124
Removing Cross-Cutting Concerns 125
Don't Meet Performance Constraints 126
Split Stories of Mixed Priority 127
Don't Split a Story into Tasks 127
Avoid the Temptation of Related Changes 128
Combining Stories 128
Summary 129...