Better Software - June 2008 - (Page 13)

From a development perspective, we want to prevent errors due to this root cause from recurring in future products or development activities. This means we must look for the underlying situation that allowed us—or Quotables You raise an excellent point about business executives learning how to better pick the brains of their techies. Asking just a few good questions could immeasurably help those who are attempting to persuade, both by drawing pertinent information out of them and by giving them insight about what kinds of information they should be prepared to present—if not this time, then next time around. naomi Karten responding to a comment posted on her article “the art of persuading management.” www.stickyminds.com/quotables10-5a It is the proliferation of just these types of inefficiencies that got me into development. I want to do my part to eradicate them. But as a tester, I find I am often too late. even encouraged us— I suggest we ask the business owner some questions. When do you want to identify these problems? After the system has been designed, to make the error. coded, unit-tested, validated, accepted, and deployed to the field? Or before system development has begun? Do you want to put more resources into finding these problems during validation or would you prefer to put that effort into finding solutions to these problems during the analysis? I agree that it is better to unearth problems before they get into the field. But I also think that it is more likely that the problems will be addressed if they are identified from the outset. sticKyminds.com member Ken taylor commenting on michael bolton’s “learning the hardware lessons” www.stickyminds.com/quotables10-5b Negotiation is a process that searches for a way to satisfy people who have competing needs. While some people frame negotiation as a power struggle or competition, it is often helpful to reframe negotiation as a problem-solving exercise that seeks the best available solution. payson hall, “proJect negotiations and the iron triangle.” www.stickyminds.com/quotables10-5c DON’T BE SHY www.StickyMinds.com JUNE 2008 BETTER SOFTWARE 13 http://www.stickyminds.com/quotables10-5a http://www.stickyminds.com/quotables10-5b http://www.stickyminds.com/quotables10-5c http://www.mountaingoatsoftware.com/better 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.