Related Content
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. |
||
How to Evaluate the Quality of a Research Study It’s wise not to accept a research report's findings just because they were published. You may discover the findings couldn’t be replicated, too small a sample was tested, or the results of studies that generated contrary results weren’t considered. Here are some questions you can ask to evaluate research. |
||
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. |
||
The Value of Service Virtualization for Agile and DevOps Teams If you’re looking to remove constraints, service virtualization should be high up on your list of things to take advantage of in 2017. The idea is to give both developers and testers the ability to create simulated services of production environments to develop and test. |
||
The Problem with Software Measurement and Metrics Many software practices rely on setting target numbers for the team to hit. But when a measure becomes a target, it ceases to be a good measure. People start gaming the system by changing their behavior in such a way to favorably adjust the measure in order to achieve the target. Don't get hung up on metrics. |