Better Software - May 2008 - (Page 30)

In Dynamics of Software Development, Jim McCarthy suggests that project teams should “triage ruthlessly” to make all decisions that shape a product. Although they are dramatically different domains, labor triage offers a lot of valuable lessons that we can apply to software testing projects. Testers can model some of their workflow based on the stages and activities the triage nurse uses to guide decisions. Just as a labor triage nurse must know when to send a patient home, when to start treatment, and when more knowledge is needed, the tester should learn to decide which bugs to fix, which bugs to keep, and when to get more information before making a decision. Triage helps testers react and adapt to the critical context drivers on our testing projects and helps us focus on delivering the value that makes a difference. {end} final Words PATIENT ADVoCACy IN TRIAgE NURsINg All expectant mothers do not need the same blend of tests, interventions, and medical care. The triage nurse does not just kick off processes. The triage nurse also actively represents the patient to the other practitioners called upon to consult or act in the case. The triage nurse gives other medical professionals a heads up on the upcoming delivery. The triage nurse communicates the relative urgency of the patient’s situation and ensures that everyone knows what may be required. In many ways the triage nurse must be aware of the work required by all medical professionals involved in the delivery process. Miscommunication can result in serious and potentially fatal problems. Triage nurses cannot exaggerate situations to draw too much attention to a case. To succeed the triage nurse must be credible. Consistency in objectively identifying the severity and priority of the case leads to this credibility. This earned credibility then triggers people to prepare and act based on the request of the triage nurse. Without credibility the triage nurse would be ineffective because nobody would listen. BUg ADVoCACy IN TEsTINg Testers without credibility find it difficult to influence projects. Testers build credibility in many ways. Testers should not exaggerate the potential impact of bugs, nor should they trivialize bugs. Testers can advocate bugs effectively by consistently providing clear and objective input about the issue being described. Testers should anticipate the type of information needed by all members of the development team. Just showing that the bug exists may be insufficient. Testers can provide information that may be useful in evaluating the priority of the bug, such as the consequence to the user community if the problem is not corrected. Testers can provide information that may be useful to the developer such as the technical state of the application and actions that took place before the bug was observed. The tester can anticipate the type of questions that may arrive from the help desk or customer support departments. The tester can provide a pithy summary of the bug, which helps non-technical executive stakeholders understand the nature of the concern. 30 BETTER SOFTWARE MAY 2008 www.StickyMinds.com http://www.aculis.com http://www.aculis.com 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.