Related Content
![]() |
Optimizing Testing: Moving Faster without Compromising Quality At some point as a tester, you’ve probably been urged by management to reduce the amount of time required for testing without compromising product quality. How can you possibly do that? Weighing the added value and relative importance of each testing task can help you optimize your testing strategy. |
|
![]() |
Ignore the Data at Your Own Risk At work, the evidence of something worth paying attention to is often front and center, and yet we dismiss it. If you ignore the data—negative survey results, team member absences, an increase in bugs, stakeholders who repeatedly miss meetings, etc.—you could be overlooking signs of trouble. |
|
![]() |
DevOps Can Be Secure and Agile at the Same Time When it comes to DevOps, the goal is to move applications from development, to test, and then eventually to deployment as quickly and efficiently as possible. However, you can still be agile while having a safe, properly security-tested DevOps environment. |
|
![]() |
Test Automation Gets No Respect The conventional approach to software automation for quality creates a losing situation for the people doing the work. When tests are reliable or take more time than first estimated, management and the rest of the team lose confidence. How can you produce consistently quick, quality information? |
|
![]() |
The Word “Automation” Has Led Us Astray The misunderstanding that automation for software quality is just doing what humans do (i.e., manual testing), but faster and more often, causes business risk. Unless you’re very clear, the quality measure is incomplete. The word automation distracts from the real value: measuring quality. |
|
![]() |
4 Frequent Feedback-Gathering Flaws If organizations really want customer feedback, why do they make it so difficult for customers to provide that feedback? Naomi Karten gives four examples from her own experience that suggest some things to keep in mind when gathering feedback from your customers. |
|
![]() |
Testing Nonfunctional Requirements in an Agile Lifecycle As organizations embrace agile, requirements become a challenge because they must be considered and validated in each (short) sprint. Ideally, nonfunctional requirements should be a continuous focus throughout the project. Here are some ways to better address NFRs in an agile development lifecycle. |
|
![]() |
Agile, Waterfall, and the Blending of Methodologies Agile doesn’t always require you to throw the baby out with the bathwater. Just because you plan to incorporate agile into your team (or even your entire organization), that doesn’t mean you need to scrap whatever other practices, such as outsourcing, or methodologies you’re using. |