Home > Articles

Overcoming Software Development Problems with XP

This chapter is from the book

Before we go more in depth with XP it is helpful to have a solid understanding of what key problems XP overcomes. Some of these were hinted at during Hour 1, "Setting the XP Landscape." In this hour we'll uncover the major software development problems and see how XP resolves them. By the end of the hour you will have learned

  • How you can control your project's outcome with XP

  • What the key risks are with software development and how XP mitigates them

  • How XP projects produce quality software products

  • How XP embraces change during development

Uncovering Software Development Problems

In this section we will uncover some of the most common problems with software development. Then, we will isolate four variables that you can use to control the outcome of your project. Before I explain what these are and how XP manages projects differently, let's dig a little deeper into why software projects go bad.

The Software Development Crisis

In Hour 1 we discovered how software engineering was born in the late 1960s as a response to the rising level of project failures. Something had to be done and rigorous control appeared to be the answer. Thirty years later software development still struggles with bad press from what seems an endless list of project failures and cost overruns. A 1995 research article from KPMG reported on the causes and effects of project failure. The top reasons for software project failures were

  • Project objectives not fully specified

  • Bad planning and estimating

  • Technology new to the organization

  • Inadequate or no project management methodology

  • Insufficient senior staff on the team

  • Poor performance by suppliers of hardware/software

The Denver International Airport (DIA) Baggage Handling System is one of the most publicized and dramatic examples of a software runaway. The images of luggage littered throughout the baggage claim area, dismembered, and spat out by the hugely complex automated system, became headline news during 1994–95. The idea was to take an existing, simple baggage-handling system that worked well and scale-up to a more complex, integrated system. After stumbling through delay after delay, the airport finally opened on February 28, 1995, with more than $300 million spent on the automated baggage system for United Airlines. The vision to develop a completely integrated system, serving all airlines had failed. Shifting goals, technical challenges, politics, and personnel change had all combined to derail the project.

Software runaway is a project that goes out of control primarily because of the difficulty of building the software needed by the system.

Your software development projects might not approach the complexity of the DIA baggage handling system, but you can learn lessons from such spectacular failures. Some industry pundits claim we are in the midst of a software "crisis" where the chances of completing a successful project are extremely poor.

NOTE

The software runaway article is available from: "Runaway Projects—Causes and Effects," Software World (UK), Vol.26, No.3, 1995, by Andy Cole, KPMG.

To summarize, your project is liable to drift into runaway if you lack a development strategy that is highly flexible, open, and scaleable. XP attacks this risk at the root by embracing change and accepting it as the norm. The practices support dynamic development that weeds out defects in quality as they occur.

The Death March

Software runaway projects are typically started with a good chance of success, but the wheels fall off during development. Increasingly developers are being dragged, tricked, or happen into a new style of software project: the death march. Edward Yourdon devotes an entire book to this subject (Death March—The Complete Software Developer's Guide to Surviving "Mission Impossible" Projects, 1997), for now we'll gain an understanding of how XP can aid you in not just surviving but overcoming the death march.

Death march is a project that after objective analysis has greater than 50% likelihood of failure.

Death march projects start with little chance of success; they are doomed to fail. Apple spent years developing what was to be its new operating system, code-named "Pink," all the while continuing to treat it as a two-year endeavor. Expectations were not adjusted when it became clear development could never be completed within a two-year time frame. Pink was eventually dissolved with seven years worth of effort wasted. Whether this project was a runaway or a death march is immaterial; it was a failure. Yourdon lists some of the typical reasons for death march in his book:

  • Politics—Internal or personal factors result in impossible constraints being established ("the project must be completed by 1 May"). These constrains are either never questioned or issues are swept under the carpet with the smokescreen of "its just politics."

  • Naive promises—Senior management makes promises to customers or marketing without checking with the development team.

  • Naive optimism—Developers with little experience or maturity, underestimate the effort involved. When committed they lack the confidence to retract their estimates.

  • The "Marine Corps" mentality—Developers understand the impossibility of the task ahead, which becomes some kind of weird challenge. This do-or-die mentality is fueled by a lethal mix of inexperienced team members, weak project management, and a general gung-ho attitude.

How can XP help with a death march? One obvious way is the XP practice that mandates a 40-hour work week. XP allows change to the scope of the project, but not the cost, time, or quality.

The Four Control Variables in Your Project

There are four variables that you can control in your software project: time, cost, quality, and scope, as shown in Figure 3.1.

Figure 3.1 The four variables of development.

What then are the impacts of controlling your project using these variables? The customer chooses three of the four and leaves you to manage the fourth. Which is the best control variable? Table 3.1 lists our variables and the side effects of controlling each.

Table 3.1 The Four Control Variables and Their Effect

Variable

Effect

Time

Too little time will certainly impede the quality of the product because there's not enough time to listen to customers, code, or test. On the other hand, extending the timeframe (not common) might not yield the answer you expected. The role of the development team is to implement changes as quickly as possible so that the customer can give feedback. Quality might be improved by lengthened timelines, but, as we will discuss later in this chapter, there is more to quality than bugs.

Cost

Can throwing money and resources at the project save you from disaster? Adding more resources to a project that is already late will only succeed in making it later. The customer needs to fund development to the estimated level, but should not expect that pouring money into a project in strife will cover issues.

Quality

The worst of our control variables! Reducing quality can appear to quicken development time, but in the end we've only succeeded in moving testing into the hands of our end users.

Scope

The standard procedure with software development is to only begin work after the scope has been agreed to and signed off. Tying down requirements and scope is an uphill battle in this model. Customers want to make sure they throw in everything they think they want and might want in the future.


How do we overcome software development issues and challenges with XP? We allow the scope of development to change, fix the other variables, and develop using the 12 XP practices.

NOTE

Allowing scope to change does not mean an unlimited-length project! The key word is change. If the customer adds a new feature request they will have to remove something of equivalent size. This is quite different from scope creep where the customer continually adds requests that the team never planned for.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020