Related Content
 |
Flattery Can Get You (and Everyone Else) Everywhere The difference between flattery and a compliment seems to be a matter of motives. A compliment represents a genuine acknowledgement of another person, while flattery, by contrast, is driven by the desire to gain some advantage. This is important to keep in mind when you’re on the receiving end. |
|
 |
The Value of Falling into Software Testing To become a software tester, there are generally no required degrees or certifications. Consequently, many testers sort of "fall into" the job. But that doesn't mean they won't do outstanding work. Coming from all walks of life and having varied work experiences can help testers find problems no one else can. |
|
 |
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. |
|
 |
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. |
|
 |
3 Ways to Foster Enthusiasm in a Software Team Enthusiasm can’t be forced on you. If you’re not passionate about software, it’s difficult for someone to get you to the point where you wake up in the morning excited to develop a mobile application. However, the conditions of your software team can change your level of enthusiasm drastically. |
