In just a year, one test team reduced its test cycle by more than 50 percent. It took analysis, planning, and effort—first they looked into how they spent their time, and then they questioned whether they could reduce time in any of those areas. Once they knew where they could be more efficient, they could start tackling their blockers. Here's how you can, too.

Cross-functionality means having all the necessary people and skills on one self-organizing team. Unfortunately, the execution of cross-functionality is often biased. The main traps we fall into are misunderstanding the value of specialization, hero worship, and not “walking the cross-functional talk” as organizations. Let’s examine each of these pitfalls in the hope that your teams may avoid them.

Today’s mobile behaviors and expectations have radically changed, a result of the continuous evolution of mobile technology and the myriad new ways users can now interact with mobile. Because of this advancement in technology and user behavior, testing organizations must also advance their mobile testing solutions to ensure they continue to deliver the most intuitive, up-to-date experience possible.

Acceptance test-driven development is a whole-delivery cycle method that allows the entire team to define system behavior in specific terms before coding begins. These conversations align the expectations of the testers, developers, and product owners, forcing any silly arguments to happen before someone has to create the code twice. Here are some great beginner exercises for teaching ATDD.