Related Content
How to Stay Challenged in Your Testing Career On one hand, testers have to keep their heads down while working to meet tight schedules. But on the other, technology is advancing at a rapid pace, and testers have to ensure they are not lagging in their skills. Testers need to constantly strike a balance between these demands to stay challenged. |
||
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. |
||
Using Estimated Reading Time as a Productivity Enhancer In so many activities, you know before you start how long it will take. When you're planning a trip, your GPS will tell you when you'll arrive. When you watch a movie or video, you typically know how long it is. Why not know the same for reading? Here's how estimated reading times can help you. |
||
7 Biases That Impact Testing We tend to judge based on biases that are a result of our environment, background, culture, and experiences. This is even true for our roles as testers. Here are seven biases that could alter the impartiality in your testing and QA practices. See if you have any inclinations you should correct. |
||
Rule Number 6: Don’t Take Yourself So Seriously When you've got way too much to do and not nearly enough support, it seems only natural to take things seriously—and to react accordingly. Yet, a case can be made not to take yourself overly seriously. After all, worrying isn't productive and your time is limited. Learn how to lighten up a little. |
||
Five Techniques for Creating Testable Requirements Documenting user requirements is always a challenging phase in software development, as there are no standard processes or notations. However, communication and facilitation skills can make this activity easier. Here are five techniques for converting user stories into testable requirements. |
||
Become an Estimation Leader Single-point estimates, whether they are for a budget or a schedule, are never correct. Things happen. Demanding that your team provide you an exact number and then treating that as a guarantee is not being a good manager—or being agile. What if you could provide a different estimation leadership? |
||
Does Agile Really Have Staying Power? It’s crazy to think just how far we’ve come since the term "agile" was introduced into software development back in 2001, as it seems like just about every company is incorporating these faster, more collaborative techniques into development and testing teams. But can agile be considered a fad? |