Better Software - May 2008 - (Page 13)

Technically Speaking What’s the Deal with Investigators? by Lee Copeland my alley. Apparently you don’t have to be sure of anything and the pay is good. But as I was reading the Google search results, it occurred to me that this sounds a lot like information systems work. In our business, we are the investigators, and we aren’t sure of a number of things: • Business analysts aren’t sure they understand the totality of what the stakeholders expect the system to do. In fact, they aren’t sure the stakeholders understand the totality of what the stakeholders expect the system to do. • Stakeholders aren’t sure business analysts understand enough of the details of their business to really understand the details. • Developers aren’t sure why they’re required to write code before the requirements are complete, correct, and consistent. They’re not sure why those least qualified to make technical decisions have the authority to do so. • Testers aren’t sure about either the documented requirements or the system under test. They aren’t sure what they can safely assume about the requirements. They aren’t sure which are the most important parts of a system to test. They aren’t sure if they have created test cases with the capacity to detect hidden defects. They aren’t sure if they have created sufficiently Now, this “Investigator” varied data. They aren’t job sounds like it’s right up Recently, a British Airways B777 crashed just short of the runway at Heathrow Airport near London. Due to the skills of the pilots and the proximity to the airport, tragedy was averted. The British Air Accident Investigation Branch announced, “The autothrottle demanded an increase in thrust from the two engines but the engines did not respond.” The announcement continued, “Investigators aren’t sure of the reason.” As I read, “Investigators aren’t sure,” the phrase echoed in my brain. Haven’t I read that before? So I Googled “investigators aren’t sure” and got more than 3,300 hits. Examples include: • Investigators aren’t sure what instigated an attack. • Investigators aren’t sure whether the fire was set intentionally. • Investigators aren’t sure how long the body was in the area. • Investigators aren’t sure if the same crew is responsible for all of the breakins. • Investigators aren’t sure what kind of gun was used. • Investigators aren’t sure how long they will look for evidence. • Investigators aren’t sure what she (Britney) is wearing now. • Investigators aren’t sure if that’s the whole story. • Investigators aren’t sure they believe it either. sure why all the people on the front end of the project get paid more than they do. Project managers aren’t sure if they’ll be given the resources they really need to carry their project to a successful conclusion. saying—some attribute it instead to Josh Billings [1] while others claim it was Will Rogers [2] who penned it. So what’s the secret to success in an “aren’t sure” world? It’s no secret. It’s the Plan-DoCheck-Act (PDCA) process cycle invented by Walter Shewhart, popularized by W. Edwards Deming, and incorporated into every iterative/incremental software development process model today [3]. Plan and do are ubiquitous. Everyone does that part. It’s the check the results of your planning and doing for effectiveness and then the act of improving the process that is the magic. Measure your results objectively. Set aside what is not effective in favor of something else. Try again, repeating the PDCA cycle. With regard to acceptance of new ideas in physics, Max Planck wrote, “A new scientific truth does not triumph by convincing its opponents and making them see the light, but rather because its opponents eventually die, and a new generation grows up that is familiar with it.” I hope that we as software development professionals we do not fight against improvements in the same manner. Remember, what we set aside is not failure; it is learning and improving. And that’s what good Investigators do. {end} referenceS: [1] en.wikipedia.org/wiki/Josh • We live in an ‘aren’t sure’ world, so I’m constantly surprised at how many people are ‘totally sure’ of their positions on anything and everything. • All aren’t sure why the others don’t recognize the intellectual creativity and prowess required to do what they do. We live in an “aren’t sure” world, so I’m constantly surprised at how many people are “totally sure” of their positions on anything and everything. In software development, people are sure of this elicitation process, this requirements notation, this programming language, this test technique, and this project management approach. Giving us fair warning about our “aren’t sure” world, Mark Twain wrote, “It ain’t what people don’t know that hurts them, it’s what they know that ain’t so.” But “aren’t sure” applies even to this oft-quoted _Billings [2] www.plumbingsupply.com/ quotes-ourteamfavorites.html [3] en.wikipedia.org/wiki/PDCA BETTER SOFTWARE www.StickyMinds.com MAY 2008 13 http://en.wikipedia.org/wiki/Josh_Billings http://en.wikipedia.org/wiki/Josh_Billings http://www.plumbingsupply.com/quotes-ourteamfavorites.html http://www.plumbingsupply.com/quotes-ourteamfavorites.html http://en.wikipedia.org/wiki/PDCA http://www.StickyMinds.com

Table of Contents Feed for the Digital Edition of Better Software - May 2008

Better Software - May 2008 Contents Mark Your Calendar Contributors eLightenment Technically Speaking Code Craft Test Connection Management Chronicles Cover Story: It's A Bug! The Chivalrous Team Member Let's Talk Agile Product Announcements 10 Things You Might Not Know About... The Last Word Ad Index

Better Software - May 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.