Skip to main content

Using Extreme Programming to Manage High-Risk Projects Successfully

  • Chapter
Software Quality and Software Testing in Internet Times

Abstract

Today, software development and its process management is a demanding task. The development company must reach the project goals on time and in budget. On the other hand, requirements change daily, developers are not domain experts and customers want to maintain close control of the project. Web application development has increased this challenge as new project-management issues have to be met. Extreme Programming (XP), a lightweight development process, is designed to meet the challenge. We have used XP successfully in a number of projects and attained the goals mentioned above. Using XP enabled us to deliver software on time and in budget, while supporting close communication between the (potential) customer and the development team as requirements changed daily. One to two releases per customer per week (two per day at the peak) indicate the flexibility and risk-minimising capabilities of the process. This allowed optimal control and planning of the projects by the development company. We illustrate our experiences using one particular time-critical project.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. We use these examples from the XP planning book to give you an impression of what user stories are like. The stories we used for the project (see below) were somewhat more detailed, but unfortunately we are not allowed to publish them.

    Google Scholar 

  2. We have since conducted other projects with equal success.

    Google Scholar 

  3. We actually built one major prototype (a combination of a presentation and a functional prototype) and several small laboratory prototypes. In what follows we will talk mainly about the major prototype.

    Google Scholar 

  4. The different XP techniques (12 in all) benefit from each other. Continuous Integration is, then, not the only prerequisite for small and frequent releases, but here we focus on this technique.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2002 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Lippert, M., Züllighoven, H. (2002). Using Extreme Programming to Manage High-Risk Projects Successfully. In: Meyerhoff, D., Laibarra, B., van der Pouw Kraan, R., Wallet, A. (eds) Software Quality and Software Testing in Internet Times. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-56333-1_6

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-56333-1_6

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-42632-5

  • Online ISBN: 978-3-642-56333-1

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics