Skip to main content
Project Management

Return to Answer

fixed some grammar and spelling, as well as capitalization of the phrases in the bulletpoints and first words after the colons.
Source Link
jmort253
jmort253
  • 9.5k
  • 7
  • 42
  • 88

I suggests to change how the Scrum of Scrum meeting is facilitated. Instead of talking about usual stuff and about the three questions, I would focus only on the following key points and have a discussion about them:

  • whichWhich team is going to deliver today: heHere other teams shall know that something new (package, code etc.) will arrive at their desk.
  • isIs there a mentionable change in the burn-down charts: anotherAnother indicator that a team will receive something earlier or later than expected.
  • isIs there any change in the backlog: againAgain, an important global change.

The idea is to focus only on those things which affect other teams. In order to do it effectively, the teams shall discuss what to bring to the Scrum of Scrum meetings. It shouldn't be something the ScrumMaster finds out. If the team has nothing to say, that the SM shall say that there is nothing to add to the meeting. If it happens on multiple occasions, then something is going on at the team level, which is worth checking out.

Additionally, there is something else which is worth checking out. How come that Agile people turn their own meeting into a status meeting? Don't get me wrong, our ScrumMasters do it all the time, but you may be able to find thea good reason and fix it. We still don't know why they do it, and neither do they.

Here I blogged about some daily stand-up variants, you may find something useful there too.

I suggests to change how the Scrum of Scrum meeting is facilitated. Instead of talking about usual stuff and about the three questions, I would focus only on the following key points and have a discussion about them:

  • which team is going to deliver today: he other teams shall know that something new (package, code etc.) will arrive at their desk
  • is there a mentionable change in the burn-down charts: another indicator that a team will receive something earlier or later than expected
  • is there any change in the backlog: again, an important global change

The idea is to focus only on those things which affect other teams. In order to do it effectively, the teams shall discuss what to bring to the Scrum of Scrum meetings. It shouldn't be something the ScrumMaster finds out. If the team has nothing to say, that the SM shall say that there is nothing to add to the meeting. If it happens on multiple occasions then something is going on the team level, which is worth checking out.

Additionally, there is something else which is worth checking out. How come that Agile people turn their own meeting into a status meeting? Don't get me wrong, our ScrumMasters do it all the time, but you may be able to find the good reason and fix it. We still don't know why they do it, and neither do they.

Here I blogged about some daily stand-up variants, you may find something useful there too.

I suggests to change how the Scrum of Scrum meeting is facilitated. Instead of talking about usual stuff and about the three questions, I would focus only on the following key points and have a discussion about them:

  • Which team is going to deliver today: Here other teams shall know that something new (package, code etc.) will arrive at their desk.
  • Is there a mentionable change in the burn-down charts: Another indicator that a team will receive something earlier or later than expected.
  • Is there any change in the backlog: Again, an important global change.

The idea is to focus only on those things which affect other teams. In order to do it effectively, the teams shall discuss what to bring to the Scrum of Scrum meetings. It shouldn't be something the ScrumMaster finds out. If the team has nothing to say, that the SM shall say that there is nothing to add to the meeting. If it happens on multiple occasions, then something is going on at the team level, which is worth checking out.

Additionally, there is something else which is worth checking out. How come that Agile people turn their own meeting into a status meeting? Don't get me wrong, our ScrumMasters do it all the time, but you may be able to find a good reason and fix it. We still don't know why they do it, and neither do they.

Here I blogged about some daily stand-up variants, you may find something useful there too.

Source Link
Zsolt
Zsolt
  • 11.9k
  • 1
  • 27
  • 60

I suggests to change how the Scrum of Scrum meeting is facilitated. Instead of talking about usual stuff and about the three questions, I would focus only on the following key points and have a discussion about them:

  • which team is going to deliver today: he other teams shall know that something new (package, code etc.) will arrive at their desk
  • is there a mentionable change in the burn-down charts: another indicator that a team will receive something earlier or later than expected
  • is there any change in the backlog: again, an important global change

The idea is to focus only on those things which affect other teams. In order to do it effectively, the teams shall discuss what to bring to the Scrum of Scrum meetings. It shouldn't be something the ScrumMaster finds out. If the team has nothing to say, that the SM shall say that there is nothing to add to the meeting. If it happens on multiple occasions then something is going on the team level, which is worth checking out.

Additionally, there is something else which is worth checking out. How come that Agile people turn their own meeting into a status meeting? Don't get me wrong, our ScrumMasters do it all the time, but you may be able to find the good reason and fix it. We still don't know why they do it, and neither do they.

Here I blogged about some daily stand-up variants, you may find something useful there too.