Over a million developers have joined DZone.

Testing in Team Collaboration

What does team collaboration mean for your testing teams? Where do they fit when it comes to collaboration across teams? How do you boost collaboration?

· DevOps Zone

Discover how to optimize your DevOps workflows with our cloud-based automated testing infrastructure, brought to you in partnership with Sauce Labs

The following article is a guest post to Zephyr from Chelsey Lang, Clearvision. Clearvision is a partner of Zephyr that helps software teams and IT programs implement tools and processes that bring high-quality software to the market.

The recent Atlassian Summit played host to seven different tracks featuring 75 different talks, meaning that there was plenty of discussion taking place. Talks covered a wide range of subjects, but the most prominent theme throughout was team collaboration. What does this mean for your testing teams? Where do they fit when it comes to collaboration across teams? How do you boost collaboration, starting with your testers?

Testing as the Center

In recent years, we’ve seen consumers shift from buying products to renting services, which has, in turn, led to a shift in the way teams work and scale. Now, instead of yearly releases of products, we see teams regularly releasing on a monthly or even weekly basis and getting feedback day-to-day that they then incorporate into their next release.

In light of this, the collaboration between developers and testers is more important than ever. Customers expect quick releases, but not at the expense of quality.

“Testing teams sit right in the middle of what's going on,” confirmed Samir Shah, President and Founder of Zephyr. “So if they don't collaborate, then it's not going to work. You're not going to get a solid high-quality product out on time.”

The Silo Challenge

The “collaborating as a team” challenge is an old one. In fact, it’s the pain point Atlassian founders Scott Farquhar and Mike Cannon-Brookes were determined to start tackling with Atlassian’s first product, JIRA. Fourteen years later, it’s a problem that we know businesses are still struggling with, especially now that global and distributed teams are facing ever faster release cycles.

It’s all about having the right tools and the right practices in place. Both are equally important when it comes to teamwork; both can change the way teams collaborate together.

“Teams need shared information, goals, and tools,” said Atlassian’s Didier Moretti at the Summit. Without these, communication suffers and there’s a lack of overall visibility of a project. More importantly, the software suffers.

The key point to take away from the Summit was clear: whether it’s testing, development, operations or customer service, all teams need to share information and work together in real time. They may be in different departments, but they can’t work efficiently in silos.

Overcoming Collaboration Pain Points

Despite its obvious significance, we’ve found that when surveyed, enterprise businesses consistently cite collaboration as their biggest challenge.

 

collaboration.jpg

For tips and tricks on breaking down silos and boosting collaboration across your teams, covering everything from your testers to your company culture, The Future of Team Collaboration is full of collaboration advice from the experts building the software your teams rely on to work together.

Download “The DevOps Journey - From Waterfall to Continuous Delivery” to learn learn about the importance of integrating automated testing into the DevOps workflow, brought to you in partnership with Sauce Labs.

Topics:
devops ,software testing ,teamwork

Published at DZone with permission of Chelsey Lang. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}