Geeks With Blogs
AJ Warnock This Page Left intentionally Blank

Thanks Joe Healy and Mike Wells!

If you were fortunate enough to attend either the Sarasota Developers Group meeting or the new Sarasota SQL developers group meeting on Tuesday night, I am sure that you will join me in thanking both of the speakers.  I have been told that there are plans to ensure that the meetings are scheduled on different evenings in the future.

 

I also was reminded that I have been negligent in maintaining my blog, so I will again resolve to do a better job in the future.  My current responsibilities both professional and personal leave little time lately to experiment, write or even keep up with the reading list. A balance must again be found.

 

So speaking of balance;   I was recently confronted with a question that truly intrigued me.  How does one know that they have achieved agility nirvana?  So many times I hear of people skipping necessary processes, testing and deliverables all in the name of agility.  Yes, according to the agile manifesto, agility stresses individuals and interactions over processes and tools; working software over comprehensive documentation, customer collaboration over contract negotiation and responding to change over following a plan BUT it does not give license to ignoring common sense and required-processes, -documentation and -requirements contracts.

 

I know I that many shops require unnecessary steps and processes to be performed regardless of the need or relevance; however, I can not conceive of a case where a secondary code review either manual or automated would be optional.  Even if this is merely a single line change, an informal check by another developer would meet this requirement.  But, I hear from many that code reviews are omitted since they are useless since our development staff is highly adept and agile. Besides, code quality, implementation methodology and appropriateness are quite subjective, controversial and irrelevant if it meets the customer communicated functional requirement (BTW, that was a verbal or email request because written change documents are excess documentationJ ).  Is this agility or fragility?

 

What about security reviews, usability reviews and regression testing?  Are these merely excess and unnecessary processes?  I am sure that each case is different, however, what about coding-, -development, -deployment and UI-standards and best practices.  Does your development team possess, maintain and require the use of these documents or concepts in an easily accessible repository?

 

So many people use agility as an excuse to cut corners, skip required processes and produce deliverables in an exaggeratedly rapid but haphazard manner.  This is not agility or agile development.  We cannot forget that the appropriateness, quality, usability and performance of the deliverable every bit as important as minimizing development time and expenses.  We must continue to remember to apply agile practices to our development processes and remain both agile and adept at ensuring that our deliverables meet the dynamic requirements.

 

So, are you an AGILE developer or a FRAGILE developer?  If you think you have reached agile nirvana you may want to reconsider…

 

 

Posted on Thursday, August 16, 2007 1:53 PM | Back to top


Comments on this post: Agile Nirvana?

Comments are closed.
Comments have been closed on this topic.
Copyright © AJ Warnock | Powered by: GeeksWithBlogs.net