Related Content
3 Must-Read Books for a Good Agile Foundation If you are searching for agile knowledge, there are many books outside the current literature that may enlighten you. Some discuss the underpinnings of concepts we consider agile, while others are contemporary business books that present compelling ways to use agile effectively. Here are three Jeff Payne recommends. |
||
Make Time for Learning with Deliberate Practice As software professionals, we need to work continuously to improve our skills. But two common challenges are how to best work to improve, and how to find the time to learn when we’re busy. The answer is deliberate practice—practice with a clear goal and defined measures for success that pushes your usual boundaries. |
||
What’s Our Job When the Machines Do Testing? It’s a safe bet that testing jobs won't be taken over by machines anytime soon. However, those of us in the test industry would be wise to heed cross-industry applications of analytics and machine learning and begin staking out the proper role of the machine in our testing domain. What could AI mean for testing? |
||
The Spectrum of Negotiation: Using the Right Skills for the Context Negotiation occurs on a spectrum, and different tactics apply in different situations. For instance, you’d treat a one-time transaction differently from an ongoing client relationship you want to nurture. Have you developed effective negotiating skills? Are you applying negotiating skills appropriate for the context? |
||
Do Testers Really Need to Learn How to Code? Because automation, AI, and agile have changed how we test software, the thought is that testers need to understand a certain amount of coding so that they can make themselves more well-rounded and better able to adapt within a software project. But there are other things testers can focus on before learning to code. |
||
Testing the Requirements: A Guide to Requirements Analysis Everyone knows testing requirements is important, and everyone says they do it, but it seems like no one knows exactly how. The best way to solve this problem is to introduce a requirements analysis stage that has to be done before coding starts. No one knows a product as well as a tester who works with it every day! |
||
Interface Grief: Is It Agile, or Just Bad Software Engineering? There are people who will use "being agile" to justify software engineering practices that could be perceived as lazy or even bad. The specifications are going to change, they say, so it would be a waste to engineer more to begin with than the minimum viable product. What's expediency and what's just poor practice? |
||
A Tester’s Guide to Choosing a Programming Language Many testers want to learn a programming language, but how should they decide which one? Justin Rohrman suggests finding an authentic problem to solve and moving from there to determine which language would be best. You can also ask developer coworkers for suggestions and help—take advantage of available resources. |