Previous page

Reflections on MSE methodology

 

Judgements on Methodologies:
Methodology Benefits Limitations Judgement

Extreme Programming (XP)

Systematic

Highly codified

Indications that it works well

Nearly impossible for:

  • groups not located together
  • large (> 10 persons) or very small teams (1 person)
Requires high levels of:
  • organizational discipline
  • commitment from employees
  • commitment from organization
  • commitment from customer 
Not viable for one-person project

Crystal

Extremely flexible to varying project factors:
  • Criticality
  • No. of people
  • Organization need
Less known about it than for XP A candidate methodology

Adaptive Software Development

Strong philosophical underpinning Methodology less completely developed than XP, Crystal, others Not viable
Dynamic System Development Method (DSDM)

Systematic approach

Consistent with "lightweight' approach

Popular in U.K.

Less commonly used in U.S. A candidate methodology
Scrum "Game" model translates well to U.S. culture Seems to mimic other, more serious and better-developed approaches Not viable
Feature Driven Development Extremely detailed model for implementation phase Limited mainly to design & implementation, less useful in analysis and early design Not viable

"Light" Rational Unified Process (RUP)

Extremely systematic

High level of detail possible

UML diagrams throughout

Adaptable to broad range of project types

 

Too heavy for small project? A candidate methodology