Related Content
 |
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 Dangers of Underplanning in Your Agile Projects Agile coaches often stress the importance of not overplanning because work is later changed or never done at all. But consequently, many teams then fall victim to underplanning and aren't equipped for a successful project. Here are some planning activities that are critical to do before your sprints start. |
|
 |
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. |
|
 |
How Do We Land This Thing? Planning for Go-Live and Beyond Some project managers have little experience bringing a project in for a landing, so they can be dismayed or just blindsided by organizational change needs and stakeholders’ expectations at delivery. Here is a checklist of some commonly forgotten items to address when a project goes live, so be sure to plan for them. |
|
 |
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? |
|
 |
Balancing Process and Tools The limits of a tool may lead us to realize that we are not working as effectively as we can, and often, changing a tool is part of the solution. But there are good and bad ways to select a tool and how you use it. In particular there are risks when you focus first on tools before considering the problem. |
|
 |
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. |
