A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

Multiple Scrum teams on the same project – handling the timing of meeting separately ..

Typically, the normal concept of a the Daily Scrum team meetings is that only those people who are Scrum team members would attend the meeting along with the Scrum Master. Others who could attend the meeting include the Product Owner and designers who work with the PO and the team. At the same time, there is a discouragement of having others attending the meeting such as senior management and so on. But there are times when other people can attend the scrum meeting, although it is better if they attend the meeting but don’t cause interruptions in the meeting.
What are these cases where the meeting can have other people attending ? Well, consider the case where there are more than 1 Scrum teams working on the same product. There can be a total of 30 people working on the product, divided into 4 Scrum teams and with each feature team looking at different features on the same product. Given that they are working on the same product, there will be many inter-dependencies between the Scrum teams and a number of workflows where data flows from part of the product to the other, and these areas may be handled by different Scrum teams.
When we talked about this situation with the different Scrum teams and tried to figure out a solution for these dependencies, there was a need for many design meetings (these being outside the Daily Scrum discussions) with the output from these meetings being added to the Backlog and then being handled in due course by the Scrum teams. Another suggestion that was there was about making sure that the Daily Scrum meetings were open, with members of other teams (or rather, there was a request that there be only one member from the other Scrum team) coming into the Daily Scrum meetings. However, it was also expected that these other team members would listen to the Daily Scrum meeting but not interrupt. If there was any query about the information that was talked about in the Daily Scrum meeting, it could be taken up after the Daily Scrum meeting, either through normal conversation with the person concerned. If the discussion required more people, then a formal meeting could be called.
This kind of solution worked well for us, with very few occasions where teams objected to other team members attending the Daily Scrum meeting. We had a couple of cases where the external team member did try to interrupt the Daily Scrum meeting by trying to ask a query about some of the information presented, but this was handled fairly easily. The only logistical issue that we had was to time the Daily Scrum meeting of each Scrum team separately, but discussions with the team had also talked about this issue and it was solved fairly easily. However, the Daily Scrum meeting was not planned to be a substitute to 2 developers having a discussion among themselves, whether they were in the same Scrum team, or across different Scrum teams. That was encouraged, with Scrum not trying to prevent any changes in the communication levels between team members.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>