This post originated from an RSS feed registered with Java Buzz
by Michael Cote.
Original Post: PeopleOverProcess.com: The Smells of Agile
Feed Title: Cote's Weblog: Coding, Austin, etc.
Feed URL: https://cote.io/feed/
Feed Description: Using Java to get to the ideal state.
For those who don't want to download the PDF, here are the sniff tests, without the rest of explanation:
An Agile organization develops iteratively, verifying that the
software is going in the right direction at the end of each
iteration.
An Agile organization has very flat and open communications
paths.
An Agile organization arranges it's work to be done in
prioritized queues, allowing the ordering and content to
change over time as required by the business needs.
An Agile organization values putting off a decision for as long
as possible, but, still makes many decisions.
Agile developers tend to check in smaller, but still operational,
batches of code rather than larger, feature complete batches.
An Agile organization runs a large amount of tests on a daily, if not hourly basis.
An Agile organization builds and tests it's software at least
daily, fixing broken builds rapidly.
An Agile organization values frequent communication over
comprehensive documentation.
An Agile organization operates on trust, respect, and
delegation instead of command and control.
I guess 10 would have been a rounder number, but I wasn't counting at the time.
Further Revisions
As you know, dear readers, we like to practice open analysis, so if you see something missing, or bogus, just tell me or leave a comment, and we'll probably put it in the next revision of the note.
Previous Topic
