/var/log/tumbles » agile

Is documentation more important or answers ?

Dhananjay Nene — Fri, 19 Sep 2008 06:00:58 +0000

When people are looking for documentation are they “really” looking for documentation ? This article argues that what people are really looking for is “answers”. So long as you are able to get them, documentation per se may not be the criteria.

James Shore: The Documentation Myth.

Agile or Lean ?

Dhananjay Nene — Tue, 02 Sep 2008 05:35:13 +0000

So as you can see, lean and agile are deeply intertwined in the software world. You can’t really talk about them being alternatives, if you are doing agile you are doing lean and vice-versa. Agile was always meant as a very broad concept, a core set of values and principles that was shared by processes that look superficially different. You don’t do agile or lean you do agile and lean. The only question is how explicitly you use ideas that draw directly from lean manufacturing.

MF Bliki: AgileVersusLean.

Agile Journal – Software testing in an Agile environment

Dhananjay Nene — Tue, 12 Aug 2008 11:48:57 +0000

Agile Journal – Software testing in an Agile environment

Agile Software Development: Disadvantages of Agile Software Development

Dhananjay Nene — Sat, 28 Jun 2008 06:33:48 +0000

Agile Software Development: Disadvantages of Agile Software Development
Nice article. If you are getting into agile .. this indicates some potential issues that you may have to deal with and allows to get into it with your eyes open.

Agile Software Development: 20 Qualities of an Agile Leader

Dhananjay Nene — Sat, 28 Jun 2008 06:02:00 +0000

Agile Software Development: 20 Qualities of an Agile Leader
Not sure where agile fits in … but a v. nice list for what it takes to be a leader. *cough* some things I need to work on *cough*

There is No Bug. It is Not the Bug That Bends, It is Only Yourself

Dhananjay Nene — Thu, 26 Jun 2008 05:11:42 +0000

There is No Bug. It is Not the Bug That Bends, It is Only Yourself

Some interesting snippets : They [.. the bugs ..] are not separate and isolated, they are actually flaws in the process itself. The problems lie within. Only when we acknowledge this (“there is no bug”) and accept it can we hope to affect real change. Agile development is an excellent platform for seamlessly incorporating the required introspection and continual improvement.

and in one of the comments :

“There is no bug” is a good shorthand for the first realization. An agile process lets you more easily respond to the shortcomings (bugs) that will inevitably be found in the implementation of the requirements.

The difference between an average developer and an excellent one is their ability to look past quick-fixes to root causes, and past root causes to systemic, architectural flaws.