May 16, 2005
Principles behind the Agile Manifesto
Things are changing. Imagine a world in which IT followed the Agile Manifesto. Just read the priniciples below, wouldn't it be great to be in a collaborative relationship with the customers?
We follow these principles:
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business people and developers must work
together daily throughout the project.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Continuous attention to technical excellence
and good design enhances agility.
Simplicity--the art of maximizing the amount
of work not done--is essential.
The best architectures, requirements, and designs
emerge from self-organizing teams.
At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.
what a crock! that's how we are suppose to work around here - and all it does is produce mediocre resuts, at best. It becomes a poor excuse for the lack of planning, documentation, standards, etc.
Customers rarely see the big picture - they want a particular problem solved so if it means copying a bunch of code and making a small mod to it to make it work - that's fine by them - problem solved (for them).
But that creates multiple codebases whereas stepping back and looking at the whole series of problems - and then planning thouroughly - can create much better solutions.
To meet such short timelines and lack of thourough design, software is pushed out the door full of mistakes, bad or rough ideas, poor integration with existing or future modules and , more often than not, you're stuck with a bad implementation that you regret being rushed into.
IMHO, nothing beats full detailed planning and Agile is dragged up as an excuse not to do that.
as far as I'm concerned, Agile is discredited as a waste of time.
there is one upside - the more people beileve Agile will solve their problems, the harder it is to do with offshoring. A bit hard to "live in the customers pocket" when you're coding away in India...
my 2c
barry.b
Finally passed the test
Managing in light of McGregor's Theory X and Theory Y
CMMI
Kicking HIT Leadership Up a Notch
That's just some mumbo jumbo project management BS
Outcomes - The tactic to get to the strategy
Nurse Call, VOIP, and Wi-Fi: Its just cool when things come together!
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
August 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
November 2005
October 2005
September 2005
August 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
Joel on Software
David Ross
Edward Prevost
Martin Fowler
The Health Care Blog
The Tales of Hoffman
The Business Word
Medical Rants
Christina's Considerations
Paul Levy
HIS Talk
Appropriate IT
Candid CIO
RSS feed




