Integration Team in Multi-team Scrum


If one team in Scrum not enough, it’s advisable use Multi Team. But here you get one more problem – how to manage more than one team. And the answer: use the Integration team. With Multi Team your Scrum will look a little bit different.

Multi-team Sprint Planning

  • All the teams or at least representatives from each team get together
  • Product Owner gives the vision for the Sprint
  • Representatives figure out dependencies
  • Representatives figure out how to minimize cross-team dependencies
  • Then each team make their usual Sprint Planning meetings

Integration Team’s Daily Scrum

Not the same as a regular team’s Daily Scrum – not “3 Questions”
This meeting kann last less than 15 minutes
Goal: Is the integration on track?
– “Did we have any trouble integrating yesterday?”
– “Are there any likely integration troubles facing us today?”

Multi-team Sprint Review

Goal: Show off the done, working, integrated software and gather feedback

Multi-team Sprint Retrospectives

  • Representatives from the teams come together
  • Discuss and identify any cross-team problems
  • Representatives go into their regular Sprint Retrospectives

Related Post

Scrum with Multiple Teams Scrum says a team should be 3 to 9 people. But sometimes you want or need to go faster, so you add more teams. This process calls Multi-team Scrum or Scaled Scrum. Challenges of Multi-team Scrum Now you need to coordinate not only a single tea...
What characteristic should requirement possess? All significant requirements included. No items have been left for future definition. Incompete if: - Non functional requirements missing; - Hidden assumptions; - Too general statements Conflicting terminology, contradictory required ac...
3 Levels of requirements in Agile development In Software Development Requirements have 3 levels: - expanded description of customers business - business point of view requirements - functionalities which should be made in our application Example: “We need a tool for selecting big data...
Story Points in estimating work One of effective way to estimate the work in software development is to use Story points. The story points are based on size and complexity, not duration.  They are also become unitless, they not measured by time or another units. One other good ...