basysKom Toolbox

17 – Agile – Interdisciplinary Teams

An agile team is an interdisciplinary team


Build a high performing team


Traditionally teams are split along professions rather than their relation to each other. In order to create high performing teams, you have to bring all disciplines together into one SCRUM team. A SCRUM Team is responsible to deliver an sprint, increment and release. Such a team is rougly 3-7 people in size, they are self organized, self contained and they can make decision for them self. No one, not the stakeholder, not the Product Owner, not the Scrum Master will (should) tell a team how a story should be implemented; as long as the team take up their responsibility to fulfill the acceptance criteria and definition of done. (Our experience is: A team that can technical decide upon their experience is faster, happier and delivers higher quality. Or in other words, self organisation is a core principle of SCRUM.)

It is important that a SCUM team is stable, changing the team will reduce the performance and to be expected quality of the results.

How you can figure out if your team is an interdisciplinary, self contained team? Here are some checkpoints:

  • They have all the competences to implement the backlog – there is no „we have to wait for department # to finalize this.“
  • They can decide what they can deliver within the next sprint
  • They are self organized
  • They are working closely together with the Product Owner
  • They can estimate the vision and stories


Agile Projects



Implementation effort

Depending on the current situation this requires coaching


New projects. But can be applied to entire organisations.


Sometimes it is complicated to break up known structures and workflows.

See also

About the Toolbox

The basysKom Toolbox is a state-of-the-art collection of best practices in agile management and software development and a valuable tool for every kickoff meeting.

These cards can be used during a project kickoff in order to select best fitting good practices from the very start of your project, but also as a reminder during the course of a project implementation. Every card holds a QR code with additional information related to the specific tool, the tools’ applicability, known constraints and additional tips on how to implement it in a project setup.

You can provide us feedback on GitHub.


basysKom Newsletter

We collect only the data you enter in this form (no IP address or information that can be derived from it). The collected data is only used in order to send you our regular newsletters, from which you can unsubscribe at any point using the link at the bottom of each newsletter. We will retain this information until you ask us to delete it permanently. For more information about our privacy policy, read Privacy Policy