The Latest

Where's Charlie?![article]

Are you inadvertently setting up a one-dimensional team? Managers regularly make statements to recruiters like, "I need another test engineer just like Charlie." Sometimes hiring people with very similar qualifications makes sense, but sometimes breaking the mold makes a better team.

Johanna Rothman's picture Johanna Rothman
Approach to Implementing Risk Based Testing[article]

Implementation of Risk Based Testing starts with an understanding of the importance of the same. A pilot approach can be developed and implemented by any project. Templates and data developed can be applied to subsequent projects. Having a quality metric on a software projects gives a very good advantage for the project manager to make decisions. By reducing risks of the project the project can be a big success. Risk based testing approach eliminates ambiguity in status of test project and injects confidence into the process.

Sreeram Kishore Chavali's picture Sreeram Kishore Chavali
The Bug Life Cycle[article]

While attending testing seminars, I noticed that there was a gap in what was being taught. There's a lot of theory presented, a lot of 'why test' classes and a lot of classes on specific techniques--but nothing on a couple of practices that will go a long way towards improving the testing process in a company, specifically, setting up a defect tracking system and enforcing policies and procedures to resolve those defects. Setting up these two things, more than anything else, will put a company on the road to organizing its testing and QA effort. To fill that gap, I've come up with the 'Bug Life Cycle' presentation. While I can't claim it as my own, it is what I've learned over the years as a tester; many of you will find it familiar.

Lisa Anderson's picture Lisa Anderson
e-Talk Radio: Highsmith, Jim, 15 March 2001[article]

Ms. Dekkers and Mr. Highsmith talk about adaptive methodologies and agile software development and the importance of the people behind the processes. Mr. Highsmith also introduces the Manifesto created by the Agile Alliance.

Carol Dekkers
The Software Productivity Crisis[article]

This article is intended for Sr. Management or those involved with driving change within their organizations. The paper provides insights on why companies should be concerned about managing software risks and presents a foundational set of recommendations in getting started with addressing what the author views as a "Productivity Crisis in Software."

TechWell Contributor's picture TechWell Contributor
Quality: What a Fuzzy Term[article]

Most people in the software field don't seem to understand even the basics of what software quality means, even those who are labeled as quality "experts." They see it as being error free, satisfying users, meeting requirements, or hitting cost or schedule targets. But in reality, it's only partly about some of those things, and not at all about others. In this column, I try to set those erroneous viewpoints aright.

Robert L. Glass
e-Talk Radio: Zubrow, David, 1 March 2001[article]

Ms. Dekkers and Dr. Zubrow talk about the global perspective on high-level maturity organizations.

TechWell Contributor's picture TechWell Contributor
Fast Software Development Needs Fast Reviews[article]

Inspections are hard to do for small and immature organizations. This paper shows a way to introduce author reader cycles without going all the way to extreme programming practices.

Hans Schaefer
e-Talk Radio: Extreme Programming, 1 February 2001[article]

Carol reviews some of the characteristics of extreme programming (test first, pair programming, user stories, etc.) and talks about where metrics fit into the extreme programming process.

Carol Dekkers
e-Talk Radio: Hendrickson, Elisabeth, 15 February 2001[article]

Ms. Dekkers and Ms. Hendrickson talk about Elisabeth's five-step process for choosing a tool for your organization: Defining Initial Requirements; Investigating Options; Refining Requirements; Narrowing the List Down by Priorities; and Evaluating the Final List, Bringing in the Tool Vendors.

Elisabeth Hendrickson's picture Elisabeth Hendrickson
The Wonderful World of Software[article]

Former STQE magazine Technical Editor Brian Lawrence shares a tale about why a commitment to quality and paying close attention to detail are critical elements in building better software. It's all about careful planning and anticipating customer behavior. Go with Brian on a stroll through one of the oldest, best-known amusement parks to find out more.

Brian Lawrence
Management of Test Case Aging: The Generation of Fine Varieties of Tests[article]

This papers on an analysis of a suite of tests and methods that have matured over many years. The author examinea aspects of testing from initial through mature stages of an in-use software product.

Jon Hagar's picture Jon Hagar
A Tester’s Tips for Dealing with Developers[article]

Is the tester doing a good job or a bad job when she proves that the program is full of bugs? It’s a bad job from some developers’ points of view. Ridiculous as it seems, there are project managers blaming testers for the late shipment of a product and developers complaining (often jokingly) that “the testers are too tough on the program.” Obviously, there is more to successful testing than bug counts. Here are some tips about how testers can build successful relationships with developers.

Yogita Sahoo's picture Yogita Sahoo
e-Talk Radio: DeMarco, Tom, 22 February 2001[article]

Staff turnover, mis-sizing a project, inflation of size during the project, failure to specify, and variation in delivery rates are the top risks common to all IT projects. Listen as Ms. Dekkers and Mr. DeMarco talk about coming face to face with risks in software development projects.

TechWell Contributor's picture TechWell Contributor
Q&A about QA[article]

"What do you do for a living?"
"I'm in QA."
"Oh. What's QA?"

Bernie Berger

Pages

StickyMinds is a TechWell community.

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