The Latest

In this interview, Melissa Tondi, senior QA strategist at Rainforest, discusses the foundation you need in order to have a positive introduction for new tools and technologies. She explains why the team leader has to understand what motivates each individual and how to get them excited about their job. Melissa says team members also have to realize that if they are in any way involved in testing software, they are a technologist, so they have to embrace the tools and technology that will continuously improve and streamline repetitive tasks.

Storytelling in business is about sharing the context—explaining different aspects of the same information through different perspectives, such as the customer’s wishes or various internal department needs. The more each person shares their point of view, the more the knowledge deepens, which provides a solid story in a business context. Here's how storytelling can help your agile team.

In this interview, Bob Galen, principal agile coach at Vaco Agile, talks about the importance of getting rid of silos by breaking down the barriers of “them and us” and becoming “we.” He also discusses the need for agile managers to steer away from a tactical management view toward a more strategic leadership view. That means leading their teams by setting expectations and guidelines and being available to help if needed, but ultimately just trusting their teams to get the job done.

Uncertainty has always been a key challenge for testers. But testing a chatbot adds a completely new level of uncertainty. There are a lot of platforms and tools available for chatbot development, but what we lack is a standardized chatbot testing strategy.

Having regular one-on-ones is the key to supporting employee performance. As a leader, you know regular conversations are important. When can you find time? How can you make them more productive?

Being a test manager is more than just being the boss. Sure, there is direction to set, issues to address, hiring, performance reviews, and status updates.

Many agile teams rework previously deployed stories, even after plenty of in-sprint testing. Well groomed, refined, stories framed with typical, alternate and error scenarios, gracefully described in well formed gherkin, continue to encounter all sorts of bugs.