Extreme Programming
Dynamic Systems Development
Crystal Methods
Feature Driven
Lean Development
Joint Application Development
Information Technology Infrastructure Library
Agile Software Development
Rational Unified Process
Rapid Application Development
PRINCE2
Scrum
Adaptive Project Framework
Waterfall
Spiral

Lean Development

Lean Development (LD) is not a project management methodology. Instead it is a set of principles that are applicable in any methodology to improve project planning and execution.

LD focuses on reducing waste. Waste is usually easy to identify and presents 'problems' which can be individually solved. Once you have solved all the individual 'waste' problems the project will be as running as efficiently as it possible can. In contrasts with the usual approach of working out 'good' practices which, may or may not deliver a benefit - reducing waste is an easy win every time.

The principles of LD can be summarized as follows

Eliminate Waste

Current practices have to be examined to establish exactly what is gained by them. Without proper consideration too many activities do not produce a benefit for the organization. Similarly activities that once produced benefit can outlive their usefulness. Claims of indirect benefit must be carefully examined to see that they are actually realized.

Amplify Learning

Too much time is wasted re-inventing the wheel. There is a strange impulse to 'create' solutions rather than discover them. Ironically the need to proceeded quickly encourages the inexperienced to rush into production without checking what others have done before.

Research is an easy win for all endeavours and avoids large amounts of work that might be undertaken to discover what could have been found out in a few hours or even minutes of research.

Research applies inside an organization as well as outside many projects waste time struggling in an area where there is an expert right next door if they did but know it.

Delay Resource Commitment

A lot of waste is generated by committing resources early only to find later that circumstances have invalidated the expenditure.

Feed the Decision Making Process

Waste is usually the result of bad decisions so favour early execution of activities which improve decision making in the future. Actions which inform decision making have hidden benefits that may not be apparent from a dependency or earned value chart.

Empower the Team

A lot of waste is generated by poor team cohesion: One person does something which contradicts or duplicates the actions of another. This often stems form top down management where individuals are encouraged to do as they are directed. Individuals in teams which are part of the management process are much less likely to do work which is not consistent with the work of others

Specify with Tests

Waste is often the result of an unclear brief which results in the production of something which is not what was desired. The clearest form of brief is a predefined acceptance test which the producer can perform themselves or have performed at will. The act of defining the test also focuses the analyst on exactly what they want.