๐”– Bobbio Scriptorium
โœฆ   LIBER   โœฆ

Planning Extreme Programming

โœ Scribed by Kent Beck, Martin Fowler


Book ID
127403146
Publisher
Addison-Wesley Professional
Year
2000
Tongue
English
Weight
430 KB
Edition
1st edition
Category
Library
ISBN
0201710919

No coin nor oath required. For personal study only.

โœฆ Synopsis


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 ofestimating 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.


๐Ÿ“œ SIMILAR VOLUMES


Extreme programming explained
โœ Kent Beck ๐Ÿ“‚ Library ๐Ÿ“… 1999 ๐Ÿ› Addison-Wesley Professional ๐ŸŒ English โš– 509 KB

Software development projects can be fun, productive, and even daring. Yet they can consistently deliver value to a business and remain under control.Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vag

Testing Extreme Programming
โœ Lisa Crispin, Tip House ๐Ÿ“‚ Library ๐Ÿ“… 2003 ๐Ÿ› Addison-Wesley ๐ŸŒ English โš– 648 KB

The rapid rise in popularity of Extreme Programming (XP) has put the practice of software testing squarely in the spotlight of application development. At one time, testing was a neglected practice, a highly specialized activity that came as an afterthought as complex, code-intensive projects were r