Posts Tagged ‘Lean’

The Difference between Lean and Agile

Tuesday, August 3rd, 2010

We’re often asked what we consider to be the difference between Lean and Agile, and if you ask 5 different people around our office, you’ll get 5 different answers. (Actually, if you ask the same person 5 times you’ll probably get 5 different answers - depending on who it is you’re asking). So we thought we’d state explicitly our views on the topic.

 

Simply put, there is no difference between Lean and Agile. To put it more complicatedly, though, there are subtle differences that we would notice in order to define something as being either Lean or Agile, but at the root of their existence, Lean is Agile, and Agile is Lean.

 

So no need to ask us that question again….

The A - Z of Agile - L is for:

Thursday, June 10th, 2010

Lead time - agile allows a project to begin with a much shorter lead time than conventional project management methodologies.

 

Lean - having evolved from the Just In Time principle, lean is the overarching methodology behind maximising business value through minimising waste.

 

Learning - it’s a crucial element of our service that we react to learnings about the project and its environment at every stage of the process.

 

Lifecycle - the primary processes required to complete the project within a pre-determined time frame.

The A - Z of Agile - K is for:

Tuesday, June 8th, 2010

Kanban - a system of workflow management that is at the heart of the Japanese Just In Time methodology. Essentially, it’s a system for signposting actions that need to be taken, originally through leaving a card in place at a point where it would become necessary to produce more items - eg at the bottom of a container.

 

Key elements - an essential component of agile practices is defining the key goals and objectives at the start of the project.

Virtues of Lean versus Strengths of Agile

Monday, March 9th, 2009

At a company away day last week, Rob H was extolling the virtues of Lean’s Single Piece flow over Iteration-based planning and development.  It provoked a lively debate with Rob’s compelling experience from IPC pitched against Nigel’s views from the Guardian project.   It’s difficult to argue that Single Piece Flow does not reduce waste; planning and review meetings are dispensed with and replaced with work in Play Limits and continual process refinement.  But is the structure created by iterations necessary to provide adequate focus and control? Conversely, do iterations lead to slop, lower quality and thrashing as the team strives toward the end of the period?

I remain undecided on the subject; clearly both approaches have merits that are better suited in certain situations.  I’m tempted to think that iteration planning provides a focal point for communication in larger teams and that Single Piece Flow will run into issues as projects scale, but equally I suspect I’m being disingenuous.  After all, it’s this type of lazy thinking that leads traditionalists to dismiss Agile.

The debate will no doubt continue.  Watch this space.