Better Software - June 2008 - (Page 46)

Analysts’ Nightmare Phrases by Tim Lister “don’t Worry aBout the users. i’M their Manager. i knoW What they need.” Anytime you don’t have the handson users on board, you are taking a big chance. Most bosses aren’t experts on the detailed work of their employees. “What do you Mean this is not in scope? We alWays assuMed you’d Build it For this release.” Implied requirements are the work of the devil. Do whatever you can to ensure that the scope is clear for all stakeholders. Draw a diagram of the scope and make in-scope and out-of-scope lists for all to read, especially for each release when you plan multiple releases to full function delivery. “We knoW exactly What We Want.” Ah, they prefer to self-medicate! These are the hardest clients to deal with. They don’t want to talk about requirements; they know the solution. Try asking them, “If we build it exactly your way, what will you do with it?” Maybe you can find the underlying requirements by understanding its use. “don’t Worry, that Will never happen.” In analysis “never” equals “probability of occurrence is zero.” It does not mean “very rare.” “that’s not a spec change; it’s a clariFication.” Call it a change, call it a clarification—you have just discovered work you didn’t know existed. Usually these are variants or exceptions to a rule. Don’t try to catch these later. Work hard to find these as you find the main policy. “let’s get everyBody in on this decision.” No, let’s get together those who are subject matter experts and those who will be impacted. Nobody else matters. Analysis is not a spectator sport. “i’ll tell you later aBout What reports We Want out oF the neW systeM.” No, we need these now to be sure we hold the right data at the right level of granularity. “the neW systeM should do everything the old systeM does, and …” In other words, even though we have a chance to rethink it all, we decide to tear down the house, build it up just as it was, and add a new wing. This is an invitation to missed opportunity and mediocre outcome at best. Build a new system; everything is in play. “We’ll revieW the spec When it is coMpletely done.” Why? Not one person has the expertise and the authority to rule on every piece of the spec. Even if he did, what a task! As you build, get sign-off only by those who understand the specific requirements. See No. 6. “We don’t have tiMe For a detailed analysis; We need this up asap!” You can do the analysis now or do it later; you can’t skip it. Somehow it seems more reasonable to do the analysis work in analysis, rather than in testing or operation. 46 BETTER SOFTWARE JUNE 2008 www.StickyMinds.com http://www.StickyMinds.com

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

Better Software - June 2008 Contents Mark Your Calendar Contributors Technically Speaking eLightenment Code Craft Test Connection Management Chronicles Agile Model-Driven Development The Myth of Risk Management Stop the Insanity! Product Announcements 10 Things You Might Not Know About … The Last Word Ad Index

Better Software - June 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.