Related Content
 |
The Art of Giving Feedback Your Team Will Act On Giving good feedback is hard. A common pattern we follow—especially when we have to give negative feedback—is starting with something positive, addressing the problem, and ending with something else positive. But it turns out this "feedback sandwich" method isn't the most effective. Here are some better ways. |
|
 |
Shake Up Your Software Processes: The Intermediate Disturbance Hypothesis Organizations that refuse to change will get left behind. But at the other end of the spectrum, too much change is also harmful. Revamping everything you do at once creates stress and can lead to your efforts failing. The right balance is shaking things up just often enough to experiment with new ideas. |
|
 |
The Essential Role of QA in Digital Transformation Many organizations are undertaking a total digital transformation in order to accelerate processes, innovations, and opportunities. But if you think you can update your development efforts without making a change to your QA program as well, your change will not be successful. QA is essential to reliability. |
|
 |
How to Build Credibility as a Tester Respect is a major player when it comes to creating and maintaining a cohesive team, and plenty of testers today feel they’re lacking the respect of their peers. With test automation sometimes being seen as some magical solution to fixing bugs, the usefulness of manual testers has come into question. |
|
 |
Is Our Innovation in Software Testing Keeping Up with Technology? The world of software testing has made many important advances in techniques and approaches, but is it keeping up with the leaps and bounds of technology's progress? Mike Sowers is an advocate for a revolutionary breakthrough in software testing, and to get there, we all need to become innovators. Here's how. |
|
 |
Scaling Product Agility: More Product, Not More Process Focusing on scaling product discovery that feeds product delivery is valuable to scaling frameworks. A cross-team product discovery cadence highlights work that's valuable to everyone and facilitates workflow for all the teams, helping them produce more of what they really need (and less of what they don’t). |
|
 |
What to Do When Bugs Are Found—Based on When They Are Found When executing test modules, an interesting question to ask is “What needs to happen with issues that are found?” Hans Buwalda suggests making a distinction between issues found during a sprint and after the team has declared the functionality under test "done"—and describes how to proceed from there. |
|
 |
Test Automation Is Mandatory, Thanks to Agile Unlike waterfall, where people had to do their best to explain the value of automation, agile more naturally promotes that need for these tools through its rapidity and integration of testing throughout the development process. Agile assumes automation is the key ingredient of your mission strategy. |
