AgileAttitudes Article
 
 
 

Vol 01 Issue 01- Your Software Process

  
 
Back to the list of articles Agile Attitudes Volume 1, Issue 1 April 29, 2004 A free bi-weekly email newsletter Brought to you by Agile Rules consulting www.agilerules.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Welcome to Agile Attitudes, a newsletter of ideas, insights and technical tips that help people find better ways to develop software. Feel free to share this with anyone - just be sure you send or print the whole thing, including the copyright notice. NEWS FLASH: Mary Poppendieck, author of "Lean Software Development" will be speaking on Saturday, May 1, 7pm at New England Agile Bazaar meeting - at Pizzeria Uno, 287 Washington Place, Newton, MA. Cost $10.00 at the door covers pizza, refreshments. RSVP to vanschoo@rcn.com Directions for managing your subscription are below. O><O><O><O><O><O Your Software Process is What You Do When the Heat is On by Nancy Van Schooenderwoert During the job interview I asked what sort of software process they were following. When my interviewer replied sheepishly that yes, they had one but it's hard to really do everything by the book, I noticed - as if it was a sudden thing - how familiar that reply was. I expected it really. I did go to work there, and yes, they did have a problem with their software process. There is a mindset that goes something like this: "I know the right way to build high quality software but this release has to get out there absolutely immediately, so I have to do the fastest thing I know. I'll clean it up afterward." This thinking has two problems. First, 'afterward' never comes. Second, is the notion that since you have a correct software process tucked away somewhere, it's ok - just this once - to deviate from it in the interest of time. Do we let ourselves off the hook for doing "quick and dirty" by telling ourselves that it's not so bad, after all that isn't our REAL process? Our real process is that nice, logical one tucked in a manual on the shelf. I suspect so. I've come to call the dirty-little-secret process "slash and burn". Might as well name it. I've encountered it almost everywhere! Your software process is whatever you REALLY do when the heat is on - not what you do "if there is time". When put under pressure, people use the methods they believe in. Some really believe in "slash and burn". Others know it's bad but they see no way to make management understand. This belief that there is a difference between the "right way" and the "fast way" is pervasive and rarely put to a test. You can test it though. Start keeping track of the underlying causes of the bugs in your code. Especially how often those cleanups that didn't happen ended up causing a new bug. Whether you're a believer in "slash and burn" or not, a reality check will be worthwhile. Persisting in old ways while claiming some other process, is a total non-starter. It will keep you from ever seeing the real facts. Evidence you gather may convert the quick-fix believers and will give you a basis for talking constructively with your management about the issue. I used to think that a release was good if all the code worked. Now I know that there is a second criterion. The code also has to have been refactored to be a fit base for further software development. If it isn't, the stage is set for trouble. O><O><O><O><O><O More articles on Agile software topics at http://www.agilerules.com Within our company we have a sub-specialty in embedded systems. Our site has articles on embedded XP and we support a discussion list focused on the use of agile methods for building embedded software. The list signup info is at http://www.xp-embedded.com/mailman/listinfo O><O><O><O><O><O If you enjoyed this issue or found it useful, forward it to a friend! Help spread the word about better ways to build software - invite your friends and colleagues to join our growing reader community at http://www.agilerules.com/mailman/listinfo/agileattitudes O><O><O><O><O><O Looking for a speaker for your next corporate or society meeting? We present dynamic, informative programs on topics of interest to managers and technical staff in their transition to more flexible, robust ways to create software. O><O><O><O><O><O Want to reprint this issue in your company or society newsletter? For permission to reprint any of the articles, contact us at info@agilerules.com. O><O><O><O><O><O Public Appearances Currently none are scheduled. If you would like to receive an email as soon as we know of an event in the Boston area of interest to the agile software community, you can sign up for the announcements list at http://www.agilerules.com/mailman/listinfo/agileannounce O><O><O><O><O><O Your feedback is welcome! Send feedback to info@agilerules.com To manage your subscription: http://www.agilerules.com/mailman/listinfo/agileattitudes O><O><O><O><O><O Brought to you by Agile Rules consulting 162 Marrett Road, Lexington MA 02421 Copyright (c) 2004 Agile Rules info@agilerules.com O><O><O><O><O><O Privacy notice: We will not release a subscriber's address to any third party for any reason. This is a strictly opt-in newsletter. No one is ever subscribed without their explicit request. _______________________________________________ AgileAttitudes mailing list AgileAttitudes@agilerules.com http://www.agilerules.com/mailman/listinfo/agileattitudes </plaintext> </td id="bodytable_r1_c3_body"> </tr id="bodytable_r1"> </table id="bodytable">