Related Content
 |
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. |
|
 |
Finding a Home for Specialists on Cross-Functional Agile Teams It may seem like the best team would be composed of all specialists, but due to their proficiency in only one area, they can actually hold up an agile workflow. You can keep specialists on your cross-functional teams; you just need to structure their work. Here are four options for making good use of a specialist. |
|
 |
Build the Right Things and Build Them Fast: Accelerate the Continuous Delivery Pipeline When most people think about continuous delivery, they think of improving the build-test-deploy-operate cycle. They don’t think about how to improve the intake process. Ensuring that quality is built into the application—not tested for after the fact—is the key to achieving accelerated continuous delivery. |
|
 |
Creating Your Organization’s Agile Culture Some organizations decide they can just “install” agile by simply telling the technical team members what to do. It never occurred to the managers that much of what makes agile successful is the organizational culture. It's important to recognize that agile is something you work toward—with the whole team. |
|
 |
Why You Need to Unify Agile Methodologies among Teams Agile software development is a complex initiative to undertake, especially when a dispersed team is involved. Organizations must establish a unified agile methodology to ensure that everyone is on the same page and understands what is expected of them in these efforts. |
