Quality isn’t something one person or role can deliver alone.
Janet Gregory and Lisa Crispin recently discussed how it takes contributions from across your whole team, including developers, testers, product managers, operations, and more. Each role brings something different to the table, and when collaboration works well, quality improves.
This activity is your chance to reflect on how different roles contribute to continuous quality in your team and how small improvements in collaboration could strengthen those contributions even more.
Your challenge:
-
Map the contributions of at least three key roles on a software team.
You can use a diagram, table, or list. For each role, describe one or two specific ways they support continuous quality in practice. -
Spot a common collaboration issue.
Think of at least one problem that can occur between the roles you’ve mapped. This could be a misunderstanding, a missing detail, or misaligned priorities. -
Propose a small experiment.
Suggest one low-risk action your team (or a hypothetical team) could take to improve collaboration. Keep it small and practical — something your team could try without needing major changes or permission. -
Share your map and experiment idea!
Post your map, your issue, and your collaboration idea in reply to this thread. Then take a moment to review at least one other person’s post and leave a thoughtful comment. Could you suggest a new role to include? An extra way they support quality? A way to strengthen the experiment?