Related Content
How Software Testers Can Stay Relevant Testers have an important responsibility to protect and further their craft. Many people who want to be considered testers should engage in career development more than they might have in the past. Hans Buwalda highlights four areas that testers need to understand to stay relevant. |
||
Make Your One-on-One Meetings More Effective One-on-one meetings between managers and the people on their teams can be a very powerful tool, but it's also all too easy for these meetings to become routine, simply turning into regular status reports. One-on-ones should address career development, identify obstacles, and look at the big picture. |
||
How Retrospective Meetings Can Improve Your Team's Software Quality Efforts Many software professionals think they won't get anything out of retrospective meetings and want to cut them out entirely. However, retrospective meetings are a necessary part of project progression, and they can significantly improve your team's software quality efforts. |
||
Overcoming Resistance to Change in Agile Teams For agile software developers, acknowledging that change is inevitable is a core principle in how we work. Yet we often resist change—for a variety of reasons. By understanding human nature and being systematic about how we evaluate decisions, we can give ourselves a way of identifying changes that add value. |
||
The Difference between Plans and Planning As former president Dwight Eisenhower said, "In preparing for battle I have always found that plans are useless, but planning is indispensable." The fact that plans may have to change does not mean planning is a waste of time. In projects, it's always valuable to consider budgeting, resources, and timelines. |
||
Are You Doing the Important Work, or Do You Just Think You Are? “Playing work” is when we do activities that look like work—they may even feel like work—but deep down, we know we aren’t being productive. These diversions are dangerous because they don't actually generate value and distract you from real work. Have you fallen victim to any of these deceptive time-wasters? |
||
Why You Should Build Your Software How Boeing Builds Planes Instead of building each individual part of a piece of software, putting it all together, and testing it to see the results, maybe we should look to how planes are assembled. By testing each aspect of the product in isolation first, problems are discovered earlier and software can be delivered faster. |
||
Reviving the Master Test Plan in the Age of Agile In the competitive environment of delivering software more quickly, many teams have abandoned detailed test plans. Michael Sowers argues for bringing back the overarching master test plan—not to have more documentation, but for the questions, creative test designs, and critical thinking the planning brings. |