Process

Articles

Can You Negotiate Quality?

XP teams have the right to do their best work. On the other hand, customers have the right to specify and pay for only the quality they need. How does one reconcile two potentially conflicting points of view? Is quality negotiable? If so, how do we go about negotiating it? This paper will explore the following questions: Is quality negotiable? How can we negotiate quality? What are internal and external quality, and are either or both negotiable? What's the XP tester's quality assurance role? How far should testers go in helping the customer define acceptance criteria?

Lisa Crispin's picture Lisa Crispin
The 11th Hour

Testers are often on the critical path for getting a software release out. They must plan carefully in order to minimize the critical path, while still doing a complete job of testing. This schedule pressure is taken to an extreme when a production server must be taken offline in order to deploy the software, and everyone is waiting for the final test results before the system can go live again. Karen Johnson describes her company's carefully planned and orchestrated method for doing a final check of an installed system. Her story is relevant to e-commerce companies as well as IT shops that are under pressure to keep systems updated while minimizing downtime.

Karen N. Johnson's picture Karen N. Johnson
Addicted to Adrenaline

Are you a manager who lavishes praise on those who can swoop in and save the day when a project hits the skids? Are you an employee who prides yourself on damage control and the ability to pull all-nighters? If so, industry expert Linda Hayes suggests that you or your organization may have a condition that masks an even more troubling underlying problem.

Linda Hayes's picture Linda Hayes
Testing Your Worth

There's no doubt that the current job market is tight and a little shaky for test professionals. In a climate where entire test groups are being laid off or trimmed to the bone, Johanna Rothman notices a trend in test management priorities that you might want to consider. Follow the story of how one test manager determined tester ROI and how testers might approach increasing their value.

Johanna Rothman's picture Johanna Rothman
The Seven Habits of Highly Effective Testing Organizations

Veteran software tester, manager, and instructor Lee Copeland offers a quick look through one of his lenses into seven hallmarks of successful software testing. Lee offers a list of organizational habits from effective change management to having a separate QA department. He explains the habits most likely to provide you with greater understanding and control of the testing process. How does your organization match up?

Lee Copeland's picture Lee Copeland
How Did I Get So Jaded?

Churning out medium-grade software to meet deadlines, and experiencing critically defective projects over the years, can easily wear down optimism till it gives way to cynicism in the software testing and quality professions. In this column, Eileen Strider empathizes with that tendency and offers ideas that may improve the quality of your experience.

Eileen Strider
Software Test Incident Report IEEE 829-1998 Format (template)

This Software Test Incident Report template is based on the IEEE 829-1998 test standard and additional information added from various sources—actual test plans, instructor experience, student comments, etc.

Wayne Middleton's picture Wayne Middleton
Measuring Performance Against Management Deliverables

Prompted by a comment from our sticky-minded audience, this week Johanna shares some ways test managers can assess their performance against specific management deliverables likely to be high on an organization's priority list.

Johanna Rothman's picture Johanna Rothman
A Hudson's Bay Start

The correlation between project size and project failure is well known in the software industry. Despite this well documented danger, companies continue to sponsor huge projects. It's unlikely we will talk executives out of their dreams of huge projects, but we can talk with them about ways to manage the inherent risks. Often a short story is worth a thousand words. The "Hudson's Bay Start" is one of these stories and a great risk reduction technique.

Eileen Strider
What You Don't Know May Help You

Some testers take it upon themselves to learn as much as possible about the inner workings of the system under test. This type of "gray box" testing is valuable, and most testers have the technical wherewithal to grasp much of what's going on behind the scenes. But it's important to recognize that sometimes "ignorance is strength" when it comes to finding problems that users will encounter.

Bret Pettichord's picture Bret Pettichord

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.