Agile Estimating and PlanningPearson Education, 1 nov. 2005 - 368 pages Agile Estimating and Planning is the definitive, practical guide to estimating and planning agile projects. In this book, Agile Alliance cofounder Mike Cohn discusses the philosophy of agile estimating and planning and shows you exactly how to get the job done, with real-world examples and case studies. Concepts are clearly illustrated and readers are guided, step by step, toward how to answer the following questions: What will we build? How big will it be? When must it be done? How much can I really complete by then? You will first learn what makes a good plan-and then what makes it agile.
Using the techniques in Agile Estimating and Planning, you can stay agile from start to finish, saving time, conserving resources, and accomplishing more. Highlights include:
Agile Estimating and Planning supports any agile, semiagile, or iterative process, including Scrum, XP, Feature-Driven Development, Crystal, Adaptive Software Development, DSDM, Unified Process, and many more. It will be an indispensable resource for every development manager, team leader, and team member. |
À l'intérieur du livre
Résultats 1-5 sur 34
... programmer, a tester or a CEO, part of an Agile team, or just looking for a way to stamp out chaos and death marches, this book will guide you.” —Lisa Crispin, coauthor of Testing Extreme Programming (Addison- Wesley, 2003) “Mike Cohn ...
... programmer and allow her ten or twenty years to write the system, allowing her years of detouring to perhaps master the domain, become an expert in database administration, and so on. Obviously, though, we can rarely wait twenty years ...
... programmer assigned to that activity will generally make sure the activity takes the full five days. She may do this by adding a few bells and whistles if it looks like she'll finish early (a practice known as gold-plating). Or she may ...
... programmers, testers, analysts, database engineers, usability experts, technical writers, architects, designers, and so on. Using this definition, even the product owner may be thought of as a developer on many projects. A final role is ...
Vous avez dépassé le nombre de pages que vous êtes autorisé à consulter pour ce livre.
Table des matières
Discussion Questions | |
Discussion Questions | |
Choosing between Story Points and Ideal Days | |
Discussion Questions | |
Estimating Velocity | |
Discussion Questions | |
Why Planning Fails | |
Summary | |
Buffering Plans for Uncertainty | |
Tracking and Communicating | |
Splitting User Stories | |
ReEstimating | |
Planning for Value | |
Financial Prioritization | |
Prioritizing Desirability | |
Discussion Questions | |
Monitoring the Iteration Plan | |
Summary | |
Why Agile Planning Works | |
A Case Study | |