Tips to Apply Root Cause Analysis for Software Quality

April 18, 2016 2

Root Cause Analysis (RCA) is an approach used in software quality to identify the root causes of bugs or issues and address them instead of treating the symptoms. In this article, Mush Honda explains that RCA can be applied to end user feedback as well as software defects during software testing and provides some tips on how to apply RCA.

Using QA in Scrum From Day One

November 4, 2014 0

The increasing adoption of Agile project management frameworks like Scrum and short iteration schedule has a deep impact on the place of software testing and the activity of QA people. In this blog post, Chris Burns tries to answer the often-asked question: “what does QA do on the first day of a Scrum sprint?”

6 Common Mistakes When Setting Up a QA Department

October 13, 2014 2

As software development companies grow, it becomes more important to have a formal quality assurance (QA) process. In this article, Veronika Olshevskaya discusses six mistakes that you might do when you set up your QA department and suggests solutions to avoid making them.

Effective Software Developer Attitudes to QA People

January 13, 2014 2

Agile software development approaches encourage a collaborative setting in software development projects. Software developments and software testers and quality assurance people have to create a better context for working together. This article discusses how programmers can improve their relationships with the software quality assurance people.

Real-time Software Quality Assurance

February 13, 2013 0

How do you perform software testing in a continuous deployment environment where you have more than 10 releases a day? How can you be confident that the code running in production is still reliable? In this blog post, Andy Hume explains the software quality process the Guardian uses for continuous deployment mode.

Debug It!

February 20, 2010 0

This book “Debug It!” by Paul Butcher provides a structured approach that will help programmers to identify and remove bugs in code. It is based on a four steps process: Reproduce, Diagnose, Fix, Reflect. For each activity, the author provides practical material on how to perform it.

1 5 6 7