Related Content
 |
Start the New Year with a Retrospective This new year, instead of a resolution, consider a retrospective. Rather than just setting one large goal for yourself, you review what you've been doing, what's been working and what hasn't, what you want to accomplish, and what small steps you can take every day to reach your objective. |
|
 |
Getting Started with Risk-Based Testing For software development, risk-based testing is becoming a major necessity to guarantee that users are getting the best experience possible without encountering too many issues. Quality assurance teams need to effectively gauge products based on the potential risk they bring. |
|
 |
The Tester as Product Owner A lot of the bugs we find were never thought through in the first place. Many of these situations are preventable, yet instead of prevention, we get the tester playing the role of the product owner—and playing it late. Why is it that we never have time to do it right, but we always have time to do it over? |
|
 |
Why Your Agile Team Needs to Slow Down in Order to Speed Up If you find yourself rushing through development or accelerating your testing process to a speed that’s not conducive to the nature of your software or project, it might be time to take a step back, examine your methods, and find a new solution. |
|
 |
The Ethical Responsibility of Defect Severity Classification When dealing with defect classification, it's important to not blindly adhere to the criteria without consideration for real business or human implications. If your software does safety-critical work, do the defect levels reflect that? Or could something go live with potentially disastrous consequences? |
|
 |
Cyber Threat Predictions for 2016 and Privacy Protection Tips The growing proliferation of digital dust is one of the key findings from the 2016 Emerging Cyber Threats Report issued annually by the Georgia Tech Information Security Center and Research Institute. |
|
 |
Six-Hour Workdays: As Great As They Sound? Companies in Sweden are experimenting with shifting to a six-hour workday. If employees have less time to do their work, they won't dabble in personal, time-wasting activities, so the same amount of work will still get done as in an eight-hour workday—or so the thinking goes. Would you try a six-hour workday? |
|
 |
What Do You Believe? Many people in the agile community believe their way of doing agile is the only right way. This is supported by confirmation bias, which lets us only see facts that support our beliefs. We deserve data-based approaches to determine what leads to the best outcomes. Can you look beyond your personal beliefs? |
