Teams come in all shapes and sized, but our workshop and exercises are currently made for a single software delivery team. This allows us to be effecient with our time and allow us to explore more deeply with your teams.
At the most fundamental level, the researchers sought to distinguish a “work group” from a “team:”
- Work groups are characterized by the least amount of interdependence. They are based on organizational or managerial hierarchy. Work groups may meet periodically to hear and share information.
- Teams are highly interdependent - they plan work, solve problems, make decisions, and review progress in service of a specific project. Team members need one another to get work done.
The team should respond to the survey and attend the Discovery Session. Here’s some tips that will help determine who is a part of what we are considering a team:
- These are people who attend the daily stand-up. To be more specific this would likely be the product owner, team/tech lead and the developers.
- No one in the process should be responsible for the performance reviews of the team members.
- The team members should be rallied around the same workflows. If there are team members with a unique workflow, you may need to consider splitting them for this process. Grouping multiple software teams will not make this process any more streamlined. It will actually do the opposite.
- This should be the core team for the team members. If the person works across multiple teams (for example, a traditional Product Manager), they should not partake in this process.
