Related Content
 |
Who’s the Boss? Let Agile Teams Manage Themselves This idea of a team in charge of itself is difficult for many people to accept. Traditional practices condition us to wait for someone to tell us what to do, and managers are accustomed to controlling everyone’s work and knowing everyone’s status. But agile teams can manage themselves—in fact, it's essential to agile. |
|
 |
Thanks to Agile, You Can No Longer Be a Selfish Tester You achieve much greater things if you trust your testing team and focus on the entire software lifecycle rather than your own personal goals. Over the years, agile has made it difficult to be both selfish and successful as a tester. |
|
 |
What’s in the Spring 2017 Issue of Better Software Magazine This is the second issue of Better Software magazine for 2017, and it has the largest page count of the last few years. With close to one hundred thousand subscribers worldwide, Better Software is fulfilling a real need in the software development community. As always, this issue has some thought-provoking articles. |
|
 |
An Agile Mindset: Learning Early, Not Failing Fast Agile encourages teams to continuously improve through learning. One of the phrases associated with this process is "failing fast"—trying new things and taking lessons from mistakes as you go. But Johanna Rothman thinks "learning early" is a better phrase. That change in terminology can give you a happier mindset. |
|
 |
The Difference between Software Testing and Hardware Testing Hardware and software have become a necessary part of virtually every company and household, and the vendors that serve these audiences must ensure that their products work as they should. Sanjay Zalavadia looks at the difference between software testing and hardware testing. |
|
 |
The Value of Experimentation in Testing With new concepts, platforms, methodologies, and devices being introduced at a rapid rate, it’s critical to both initiate and establish a culture of experimentation within your testing team. You need to experiment and take risks in order to keep pace and hopefully surpass the competition. |
|
 |
3 Common Collaboration Problems for Teams Transitioning to Agile A shift toward working in smaller teams on tighter releases forces organizations adopting agile to rethink what successful delivery looks like. It can be a big change for those used to silos. Here are three key symptoms of agile teams that don’t have close collaboration—and some solutions you can implement to fix them. |
|
 |
3 Reasons Exploratory Testing Is Great for Agile Teams Specification-based testing is critical for determining whether a user story is “done done.” But that doesn’t ensure a positive user experience. Coherence, comprehension, and usability are beyond the scope of automated functional testing. Here are three reasons agile teams should embrace exploratory testing. |
