Related Content
 |
What Aircrews Can Teach DevOps Teams Aircrews learn a set of skills involving a structured way of communicating that breaks down barriers and forces an honest evaluation of the issues. They also automate what they can but still practice their craft over and over again, including what to do during failures. DevOps teams can learn a lot from aircrews. |
|
 |
Why the Minimum Viable Product Matters The MVP brings tremendous value to a team’s ability to effectively implement agile practices. It also allows us to better understand what “value” actually means to our users and how context changes the meaning. Your MVP must move through your validation and release cycles while still being valuable to your users. |
|
 |
Stop Hoarding Bugs and Clean Up Your Backlog Many testing organizations have bugs sitting in their bug-tracking tool gathering dust. The issues aren't high-priority enough to fix immediately, but no one wants to close them because they might get around to fixing them eventually. This is a hoarder mentality! You need to organize and declutter your bug backlog. |
|
 |
The Testing Practices and Metrics That Really Matter in Agile and DevOps Scaled agile and DevOps change the game for software testing. It’s not just a matter of accelerating testing; it’s also about fundamentally altering the way we measure quality. The test outcomes required to drive a fully automated release pipeline are dramatically different from the ones most teams measure today. |
|
 |
A Tester’s Role in Requirements Exploration Agile is supposed to get people to talk to each other in real time. However, many teams still lack a shared understanding of what they are going to build, even as they start coding. As testers, we can explore feature specifications early, contributing to successful and timely delivery through defined requirements. |
|
 |
Testing at 43,000 Feet: Reporting Risk That Matters Many teams' daily testing gets broken down into numbers. If you're used to dashboards, it can be easy to forget the prime objective: to raise up quality issues—or, in the case of safety-critical devices, potential hazards. Graphs are comfortable, but do they really provide the information we should be looking for? |
|
 |
Signs of a Project Headed for Trouble Projects rarely get in trouble suddenly. More often, the descent into trouble is gradual, and the signs are easy to miss—but they are there. If you detect any of these potential signs of possible failure, it would be wise to take steps sooner rather than later to address them and get the project back on track. |
|
 |
Improving Requirements with Preemptive Testing Most product defects are created during requirements definition. To significantly reduce and prevent requirements problems, consider making their management your software testers' responsibility. They can identify requirements defects as they are being developed, as well as work out mitigations for their root causes. |
