Planning Extreme Programming

Planning Extreme Programming

Paperback XP

By (author) Kent Beck, By (author) Martin Fowler

$30.54
List price $37.47
You save $6.93 18% off

Free delivery worldwide
Available
Dispatched in 2 business days
When will my order arrive?

  • Publisher: Addison-Wesley Educational Publishers Inc
  • Format: Paperback | 160 pages
  • Dimensions: 184mm x 230mm x 12mm | 340g
  • Publication date: 16 October 2000
  • Publication City/Country: New Jersey
  • ISBN 10: 0201710919
  • ISBN 13: 9780201710915
  • Sales rank: 559,561

Product description

In this timely follow-up to Extreme Programming Explained, software engineering gurus Kent Beck and Martin Fowler show exactly how to plan your next software project using Extreme Programming (XP). Planning is a vital element of software development -- but all too often, planning stops when coding begins. Beck and Fowler show how to make software projects far more manageable through a series of simple planning steps every project manager and team leader can easily perform "every day. The book follows XP projects from start to finish, presenting successful planning tactics managers and team leaders can use to adjust to changing environments more quickly and efficiently than ever before. This book is full of war stories and real-world analogies, and offers actionable techniques on virtually every page. It will be invaluable for every project manager called upon to deliver reliable, high-value code in "Internet time."

Other people who viewed this bought:

Showing items 1 to 9 of 9

Other books in this category

Showing items 1 to 10 of 10
Categories:

Author information

Kent Beck consistently challenges software engineering dogma, promoting ideas like patterns, test-driven development, and Extreme Programming. Currently affiliated with Three Rivers Institute and Agitar Software, he is the author of many Addison-Wesley titles. Martin Fowler is the Chief Scientist of ThoughtWorks, an enterprise-application development and delivery company. He's been applying object-oriented techniques to enterprise software development for over a decade. He is notorious for his work on patterns, the UML, refactoring, and agile methods. Martin lives in Melrose, Massachusetts, with his wife, Cindy, and a very strange cat. His homepage is http://martinfowler.com.

Back cover copy

""XP is the most important movement in our field today. I predict that it will be as essential to the present generation as the S.E.I. and its Capability Maturity Model were to the last."" --From the foreword by Tom DeMarco The hallmarks of Extreme Programming--constant integration and automated testing, frequent small releases that incorporate continual customer feedback, and a teamwork approach--make it an exceptionally flexible and effective approach to software development. Once considered radical, Extreme Programming (XP) is rapidly becoming recognized as an approach particularly well-suited to small teams facing vague or rapidly changing requirements--that is, the majority of projects in today's fast-paced software development world. Within this context of flexibility and rapid-fire changes, planning is critical; without it, software projects can quickly fall apart. Written by acknowledged XP authorities Kent Beck and Martin Fowler, "Planning Extreme Programming" presents the approaches, methods, and advice you need to plan and track a successful Extreme Programming project. The key XP philosophy: Planning is not a one-time event, but a constant process of reevaluation and course-correction throughout the lifecycle of the project. You will learn how planning is essential to controlling workload, reducing programmer stress, increasing productivity, and keeping projects on track. Planning Extreme Programming also focuses on the importance of estimating the cost and time for each user story (requirement), determining its priority, and planning software releases accordingly. Specific topics include: Planning and the four key variables: cost, quality, time, and scope Deciding how many features to incorporate into a release Estimating scope, time, and effort for user stories Prioritizing user stories Balancing the business value and technical risk of user stories Rebuilding the release plan based on customer and programmer input Choosing the iteration length Tracking an iteration What to do when you're not going to make the date Dealing with bugs Making changes to the team Outsourcing Working with business contracts In addition, this book alerts you to the red flags that signal serious problems: customers who won't make decisions, growing defect reports, failing daily builds, and more. An entire chapter is devoted to war stories from the trenches that illustrate the real-world problems many programmers encounter and the solutions they've devised. 0201710919B04062001

Table of contents

Foreword. Preface. Acknowledgments. 1. Why Plan? 2. Fear. 3. Driving Software. 4. Balancing Power. 5. Overviews. 6. Too Much to Do. 7. Four Variables. 8. Yesterday's Weather. 9. Scoping a Project. 10. Release Planning. 11. Writing Stories. 12. Estimation. 13. Ordering the Stories. 14. Release Planning Events. 15. The First Plan. 16. Release Planning Variations. 17. Iteration Planning. 18. Iteration Planning Meeting. 19. Tracking an Iteration. 20. Stand-Up Meetings. 21. Visible Graphs. 22. Dealing with Bugs. 23. Changes to the Team. 24. Tools. 25. Business Contracts. 26. Red Flags. 27. Your Own Process. Index. 0201710919T04062001