Related Content
Quality in Quantity: How App Quality Is Now Everyone’s Responsibility Quality has increasingly become a responsibility for not just one single segment of the team, but the team as a whole. It’s important for each member of a team to have some hand in making sure that what’s being developed works as intended as it goes through each individual progression. |
||
The Importance of Agile Source Code Management If agile teams do not effectively utilize source code management, they can miss out on key benefits and sometimes even lose essential source code used for application deployment. But done well, a source code management solution can provide the best platform for effective agile practices. Bob Aiello explains. |
||
Jelly Beans and Defect Classification: Different Strategies for Success When there’s a bowl of jelly beans, some people grab a few at random, but most of us have favorites. If you're crafty and have flexible standards, you can maximize consumption by adjusting your criteria as colors dwindle. Classifying defects should not be like choosing jelly beans; you need firm standards. |
||
Handling a Check Failure in Test Automation What happens on your team when a check (what some call “automated test”) fails? Regression tests or checks that are effective toward managing quality risk must be capable of sending action items outside the test/QA team quickly. How do you provide fast, trustworthy quality communications from your team? |
||
A Tester’s Guide to Dealing with Scrummerfall If you’ve been a tester on an agile team, you’ve probably experienced “Scrummerfall” behavior—a cross between Scrum and waterfall. There isn’t really any collaboration, and there's too much work in progress during each sprint. Bob Galen tells you how planning can help you avoid it. |
||
Stronger, Faster Quality with Simple, Focused Checks Imagine focusing on prioritized business requirements at the software layer closest to where those business items are implemented. Writing just one check—that is, a programmed verification—per business requirement makes for simple, focused checks, supporting stronger, faster quality around the team. |
||
What Are You Measuring? Many teams do single-point measurements in their projects. But that doesn't give you a good long-term picture. When you look at multiple-dimension measurements—especially trends over time—you learn more. You can take those trends into a retrospective to investigate how your team could work better. |
||
Reliability Is Possible with Environment Management To have completely reliable systems, we must have effective IT controls in place that help to identify risks before they turn into incidents. Change management meetings are very helpful for coordination. Effective environment management and change control can keep your systems reliable and secure. |