Project Management

Articles

Tester and developer shaking hands across a table How to Collaborate on a Brand-New QA Team

As a quality analyst, when you raise a bug, developers sometimes react as if you were personally attacking their job. The situation can be even more difficult if you are starting a new QA team, where you will work with people who have never had the quality assurance component. Here is some advice for ways you can be effective when you’re starting on a team that has never worked with quality analysts before.

Juan Pablo Aguirre's picture Juan Pablo Aguirre
Woman wearing a hard hat and working with a machine Blending Machine Learning and Hands-on Testing

As your QA team grows, manual testing can lose the ability to focus on likely problem areas and instead turn into an inefficient checkbox process. Using machine learning can bring back the insights of a small team of experienced testers. By defining certain scenarios, machine learning can determine the probability that a change has a serious defect, so you can evaluate risk and know where to focus your efforts.

James Farrier's picture James Farrier
Car dashboard with various meters and dials 5 Key Elements for Designing a Successful Dashboard

When you’re designing a dashboard to track and display metrics, it is important to consider the needs and expectations of the users of the dashboard and the information that is available. There are several aspects to consider when creating a new dashboard in order to make it a useful tool. For a mnemonic device to help you easily remember the qualities that make a good dashboard, just remember the acronym “VITAL.”

Nels Hoenig's picture Nels Hoenig
Cards and chips at a casino Risk Coverage: A New Currency for Testing

In the era of agile and DevOps, release decisions need to be made rapidly—preferably, even automatically and instantaneously. Test results that focus solely on the number of test cases leave you with a huge blind spot. If you want fast, accurate assessments of the risks associated with promoting the latest release candidate to production, you need a new currency in testing: Risk coverage needs to replace test coverage.

Wolfgang Platz's picture Wolfgang Platz
Pawn chess piece with a king's crown on top Zero to SME: Quickly Becoming Your Own Subject Matter Expert

On a new project, we often lack the luxury of having a subject matter expert available to answer our questions. When that’s the case, we have to become our own SME. Here are a few key methods from the writings and presentations of experts in various fields that deal with information gathering and rapid learning. You can easily use these methods, right now, to quickly gain the knowledge you need in order to move forward.

Thomas Sullivan's picture Thomas Sullivan
Laptop screen showing test data analytics Applying Data Analytics to Test Automation

Testers gather lots of metrics about defect count, test case execution classification, and test velocity—but this information doesn't necessarily answer questions around product quality or how much money test efforts have saved. Testers can better deliver business value by combining test automation with regression analysis, and using visual analytics tools to process the data and see what patterns emerge.

Harsh Vardhan's picture Harsh Vardhan
Computer showing data analysis Rookie Mistakes in Data Analytics

It's easy to make simple mistakes in data analysis. But these little mistakes can result in rework, errors, and—in the worst case—incorrect conclusions that lead you down the wrong path. Making small process changes can help you steer clear of these mistakes and end up having a real impact, both in the amount of time you spend and in your results. Here are some tips for avoiding rookie mistakes in data analytics.

Nels Hoenig's picture Nels Hoenig
Developers and testers giving each other useful feedback Improve Tester-Developer Relationships with Helpful Feedback

Testers and developers often have a strained relationship. Each side has a certain level of expectations as to what the other side should know and do, while there is little understanding of the constraints, conditions, and requirements that the other team has to work within. But it does not have to be this way. A little effort in giving more specific and helpful feedback can go a long way toward improving attitudes.

Michael Stahl's picture Michael Stahl
Score being shown at a baseball game More Than a Score: Taking a Deeper Dive into Your Metrics

One key benefit of metrics is that they can be measured using a standard process; we can explain the numbers, and leadership can understand what that means. The downside is that it is only a measurement, so issues can easily hide until they become problems, and great work can also go unrepresented. Sporting events are a great example: The end score tells you who won, but not the details of the game. We need to look deeper.

Nels Hoenig's picture Nels Hoenig
Team members fitting puzzle pieces together Whole-Team Testing for Whole-Team Quality

Whole-team testing means the whole team understands and participates in testing, using testing education as a tool to support quality efforts. And to be able to support testing in a meaningful way, team members must experience how testing is done by professional testers. Understanding skilled testing can help non-testers realize what quality criteria should be there and what elements of a product contribute to great quality.

Lalit Bhamare's picture Lalit Bhamare

Pages

StickyMinds is a TechWell community.

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