Dan Croak: Agile Principles in Practice - Part 3: Decide as Late as Possible

This post on "Agile" continues a mini-series on misunderstood terms in technology. Previous terms were the cloud and NoSQL.

Why Agile?

We want to make software that is valuable for people cheaply and efficiently. Ideally, the process is also pleasant for the participants.


 
Agile development achieves that goal. Agile teams build stuff customers want. They do it faster with fewer wasted cycles. Developers have more fun and write cleaner code. They do it at a constant pace that can be sustained forever.

Principles

The Agile Manifesto kicked off the movement with some lofty phrases like "people over processes". It proposes that we value "working software", "customer collaboration", and "responding to change" over some other stuff.

 

Sounds good, if a little vague. Getting a little more specific, the following subset of principles offered by the Poppendiecks in Lean Software Development are a helpful grouping:

  1. Eliminate waste (click to read)
  2. Deliver as fast as possible (click to read)
  3. Decide as late as possible (Today)

Principles are meant to be universal. The above list should apply to the software team of any entrepreneur reading this. (Editor’s Note: this is the 3rd and final part of Dan Croak's series on Agile)

Dan Croak: Agile Principles in Practice - Part 2: Deliver as Fast as Possible

This post on "Agile" continues a mini-series on misunderstood terms in technology. Previous terms were the cloud and NoSQL.

Why Agile?

We want to make software that is valuable for people cheaply and efficiently. Ideally, the process is also pleasant for the participants.

 

Agile development achieves that goal. Agile teams build stuff customers want. They do it faster with fewer wasted cycles. Developers have more fun and write cleaner code. They do it at a constant pace that can be sustained forever.

Principles

The Agile Manifesto kicked off the movement with some lofty phrases like "people over processes". It proposes that we value "working software", "customer collaboration", and "responding to change" over some other stuff.


Sounds good, if a little vague. Getting a little more specific, the following subset of principles offered by the Poppendiecks in Lean Software Development are a helpful grouping:

  1. Eliminate waste
  2. Deliver as fast as possible
  3. Decide as late as possible

Dan Croak: Agile Principles in Practice - Part I: Eliminate waste

This post on "Agile" continues a mini-series on misunderstood terms in technology. Previous terms were the cloud and NoSQL.

Why Agile?

We want to make software that is valuable for people cheaply and efficiently. Ideally, the process is also pleasant for the participants.


Agile development achieves that goal. Agile teams build stuff customers want. They do it faster with fewer wasted cycles. Developers have more fun and write cleaner code. They do it at a constant pace that can be sustained forever.

Syndicate content