Insight Agile Methodologies

This article gives an introduction to four methodologies used for Agile software development:

• Scrum
• DSDM
• XP
• RUP

Scrum

• Formal management methodology
• Delivers real business advantage
• Lightweight and adaptive

Scrum is a lightweight, Agile project management process. Derived principally from modern manufacturing techniques such as Just in Time, Lean and Total Quality Management it facilitates an adaptive, empirical approach to management.

Scrum utilises 30 day iterations, known as "sprints", to provide a focused goal on which your team can work with minimal external interference; once the sprint requirements are fixed. The premise is that 30 days is sufficient time for your team to focus and deliver significant business advantage, and yet short enough to allow re-alignment between sprints and still meet the business needs.

Only where there is a substantial shift in business strategy would a change be required mid-sprint, but this is not the norm. The formal Scum methodology provides tools and techniques to manage the project.

Sprint planning, prioritised task management, tracking, and communication are provided for.

Scrum In Practice

The above is a description of Scrum that will be very familiar to Scrum practitioners.

The challenge for those that complete the traditional "Scrum Master" course is how the techniques they learn can be put into operation and how they scale up.

This is where IndigoBlue's industry-leading experience can be beneficial:

• To mentor Scrum Masters to take them beyond the course
• To help organisations to adopt Agile in an easily accessible way, building up from pilot projects to roll out Agile across the organisation
• To get the best balance of Agile and Lean for major programmes

DSDM (Dynamic Systems Development Method)

• Early Agile approach
• Recent version Atern
• Time-boxed, iterative approach
• Includes training and roll-out

Developed in the early 90’s by a consortium which included a number of blue chip organisations, DSDM was a forerunner to many of today’s Agile processes.

At its core, DSDM utilises a time-boxed iterative approach, though this is phased rather than incremental. More recent versions have incorporated Agile ideas and techniques and in its latest incarnation - Atern - DSDM seeks to combine the discipline of traditional "waterfall" methods of project management with the responsiveness of Agile methods. It also extends out further than other Agile methods by including training and roll out.

XP (Extreme Programming)

• Development focused
• High-quality engineering techniques
• Low initial cost to implement

The unfortunately named Extreme Programming (XP) is a development focused methodology. It comprises of 12 basic rules and techniques that govern and control your project providing a disciplined rather than controlled environment.

XP is a natural process which will be accepted rather than enforced. Intuitive techniques such as continual customer collaboration, short iteration planning, refactoring, test-driven design, simplicity and prioritisation are readily adopted, particularly by development teams, and as such XP has gained strong support from the development community.

Some people see a weakness of XP being its developer focus and minimal management view (of the 12 rules only 3 relate to management). However, when embedded within an iterative, Agile process that has more management focus (e.g. DSDM, RUP or Scrum) it can deliver significant benefit at relatively low (or zero) cost and low risk.

RUP (Rational Unified Process) - Agile at its Core

• Iterative process
• Configurable to be Agile
• Can be low on ceremony

To some, the appearance of the Rational Unified Process (the RUP) in this list of Agile processes will seem odd, if not incorrect.

At its core, however, the RUP is Agile, and the spirit of the RUP is very much Agile. Regardless of any particular configuration, it is intended that it should be iterative and low ceremony. The most common fault when implementing the RUP, though, is failing to accept the required mind-set change to embrace the iterative approach, instead mapping the phases to create what is essentially a more traditional, waterfall approach.