Some help while you're using this page

Hover and click on coloured underlined text to it's relevant comment in a popup. Clicking on the icon to see more about the colour coded "Functions and Qualities" of writing. You can show and hide each comment's type by clicking on their colour codes in the sidebar under "Comments Key", this can help make the Extract easier to read.

Among software development processes (SDP), Extreme Programming (XP)has become the best known example of an Agile Development method and is used in small to medium software development companies.

It is recommended as best suited to applications that have unstable and changing requirements. Because XP utilises the benefits of team work it is not suitable for larger companies with development teams working at different locations.

In recent years, there has been an increasing interest in the benefits of Extreme Programming and its effectiveness in the commercial environment.

This report aims to evaluate the effectiveness of XP's adoption in small to medium software development companies since 2004.

2. Are the techniques underpinning XP effective?

There are ten core techniques underpinning the XP method. In order to assess each one a comparison has been done using two case studies:

A study by Layman et al. (2004) looked at the effects of using XP in an industrial case study with Sabre Airline Solutions.

A study by Madsen (2005) detailed the effectiveness of each technique in a start up environment.

However, the main weakness of these studies is the failure to address the impacts on the customer. It is necessary to consider the effect that each technique can have and whether it delivers satisfaction in the end product.

A study by Grisham and Perry (2005) looked at the effects of the XP development environment from the view of customer satisfaction. The techniques bring the customer and the development team closer together by focusing on delivering cost efficiencies and quality. The effects this has on the customer is considered.

The effectiveness of each technique is discussed in order below.

2.1 Small releases

The functionality that provides the highest business value is delivered first. Increments of additional functionalities frequently follow.

Madsen (2005) found that with tight controls over the release management small releases are less risky. This was achieved by having one set of project source files. Layman et al. (2004) also found this technique to be effective as developers preferred the concise tasks to follow over the coming weeks.

The aim of small releases is to build stability into the software development processes which Madsen (2005) has shown.

An early increment delivery could provide customer satisfaction. According to Grisham and Perry (2005) small releases might not always be satisfactory as the impact of each release on the customer is unknown. Having a system deliver business value in small releases may hinder some customers but suit others.

The evidence from these case studies shows that this technique could be successful with customers capable of receiving increments. The developing system might be replacing two older systems and initial increments may not replace the old systems. The customer would have an additional system to use in place which would not be beneficial. A system that is replacing a manual process might be more suited to incremental delivery as each one will provide increased efficiency.

Quality: Structure

The writer produces a contents page which helps the reader to navigate through the report. Consistent headings and sub-headings show clear thinking and good structure. The use of questions as headings shows that the writer has analysed the issue into component problems, and also suggests that the report will be interesting to read.

Introducing the terms "software development process" and "extreme programming" in full before using the acronyms "SDP" and "XP" within the rest of the report is not only good practice but also helpful to the reader.

The writer clearly outlines the aim and scope of evaluation, which helps the reader navigate the following sections and understand the purpose of the writer"s arguments. Clear signposts of intention are also helpful to assessors.

This is a complex section of the report with ten techniques to be considered using three different source texts. The writer takes time to explain the approach and the sources to be used. This helps the reader and clearly demonstrates how the subsequent material contributes to the overall analysis.

Within each of the numbered sub-headings, the same approach is taken. A short description of the technique is followed by an analysis of how the technique was implemented in the three source texts and a short conclusion on the value of the technique in these and other cases. This allows the reader to navigate the ten techniques with ease.

Function: Describe

This is a very concise overview of extreme programming. The writer is assuming some knowledge on the part of the reader, so the overview simply explains the context and scope of the report. For a less informed reader, more information might be necessary.