Management Scrum Team – Part 4

This is the last of 4 parts. See here for the first part. Links to all four parts are there, or search to the right.


Retrospective. Again, telling the truth here can be difficult.

The whole MST comes to this meeting at the end of every Sprint. For a two-week Sprint, maybe two hours. The purpose: To get better.

What do we do in the meeting?

We discuss the good and the bad. Some of the bad gets added to the impediment list (a list of things we want to fix or mitigate to make things work better here).

I suggest we give the SM (the ScrumMaster for the team) a 10 minute time-box to explain what he has done this past two weeks. Which impediments he has worked on, what solutions they have gotten implemented, how much the Velocity has increased because of his efforts (or efforts he drove). People say things like, “Wow, I guess he did something useful!” This is kind of like a ‘demo’ for the SM.

We identify the biggest impediment for the MST itself. As of NOW. We do this quickly.

And we spend most of the time working together to fix the top impediment for the team. As examples, the MST might:

  1. devise a solution together
  2. plan the execution of the solution
  3. build a business case (e.g., to justify spending some money). Is it clear now that the benefits are much higher than the costs? Etc.

The business case might go to the CEO or even the board for a decision. Often the business case simply enables the team to work through the information and convince themselves of the best solution. Often, also, the MST starts a business case, and someone else (the SM?) refines it, improves it, fleshes it out and completes it later.

Who ‘fixes’ the impediments? Well, it depends. The SM, the MS Team or people outside the MS Team. Depends on several factors.

The key thing is that the Retrospective enables them to get better each Sprint. Better can be measured many ways, but typically as higher Velocity for the team.

This is more effective, in a bigger way, than the SM working in isolation, and more useful than just identifying the (usually smaller) day-to-day impediments in the Daily Scrum meetings.


How much difference could an MST make?

Hard to say. We do not have enough experience in enough situations to know well.

My experience suggests that in about three Sprints, the MST is working at ‘normal’ level. Maybe four Sprints — typically — but the problem is you had no ‘before’ metrics on the ‘Velocity’ of the MST. So, there is nothing to compare the new Scrum Velocity to.

The good news is you now have a metric for the productivity of the MS Team. They may not estimate the ‘Story Points’ well yet, but they are learning.

Usually you find that ‘the Velocity is lower than we wanted.’ Is that really a surprise? (CEO, you did know that already! Right?)

Now you have an approach to getting better as a team, for avoiding your weaknesses (of individuals) and for drawing on your strengths (as a team).

The difference can be huge if people engage, if you allow yourselves to see the truth and if you have the courage to take reasonable actions.


One key issue. I think it is typical to find that the people you have in the ‘management team’ are not the right balance of people for a good MST. The MST must be balanced against the vision and the items in the PB. Often you see an imbalance.

Thus, you often need to move some of these people outside the MST and probably add some other ‘skill-sets’ to the MST (new people).

This is a feature, not a bug. Meaning: Seeing what kinds of people you really need in the MST is a big help.


Those are my simplified and initial ideas on an MST.

I hope my humor about the problems of life and the problems we often have being managers was taken the right way. Manager work is hard, and being a manager is hard. I do have sympathy, despite my sometimes sarcastic tone.

One could cry about the situation, cry at the measureless waste in the lives of the managers and the people they manage and the impact on the customers. Or one could laugh. I choose to laugh.

This problem of measureless waste and ‘not good enough yet’ is true for all of us, and it is sad and we can be sarcastic. Just to be sarcastic is not good enough. We must act to improve things as best we know how.

In this vein, one must have sympathy for managers. In my opinion, they are usually not trained well to be managers. In fact, they are generally mis-trained (trained wrongly), and the Peter Principle (they rise to their level of incompetence) is too true. Their ‘boss’ is too… hmmm… lacks the courage to fix it when the Peter Principle occurs. These are good people, some of our best usually, but badly trained and often badly positioned. To the degree we can fix this (and I think we can, at least some) it can make for a big improvement.


Please give me and us your feedback and suggestions.

That covers the main things in Scrum that the MST must do. It gives a quick overview. It definitely does not answer every question you will have.

Folks: Careful doing this at home. It may look easy on paper, but you will want to get all the help you can to learn how to do it semi-professionally as soon as possible. Get training. Get coaching, at least.

Now, please send me your reactions and comments.
Joe at




« « Management Scrum Team – Part 3 || Executive Action Team » »


3 thoughts on “Management Scrum Team – Part 4

  1. Pingback: Management Scrum Team - Part 3 - Lean Agile Training

  2. Pingback: Management Scrum Team - Part 1 - Lean Agile Training

  3. JIm Dowling

    Before offering some closing comments, Thank you for initiating this. Providing air cover for Agile/Scrum is a challenge at most organizations. We chose to start at the top and work down while others started in the middle and worked up. With you, I ask others to jump in here and help our teams succeed.

    In my last post, I described our method for Sprint Reviews. We do the same for Sprint Retrospectives. We bring the ultimate customers into the review process. We also break the review into to parts: Report and Collect Feedback first then Impediments Resolution so that we can release our customers who, by the way, rarely mind being called chickens, clever chickens who can write a Post-It Note.

    When working at the level of Strategy Execution, more than some Impediments need a Sprint or Two to resolve. For that reason, we may require that Executive Leaders participate to expedite authorizations that might be required.

    Although we do not generally discuss this with clients beforehand, we make individual behavioral and technical performance as transparent as possible throughout. Our position is that low-performing managers and leaders are long-term impediments for organizations and they need to deal with them. Sometimes, this does require individual coaching to the Team Member, Scrum Master or Product Owner but often, we need to have the discussion with our client who is often not directly involved in much of the teams work. Feedback on Behaviors and Results is valuable. We start every team of with a Team Effectiveness Workshop to declare expectations.

    We also note remarkable variations in team dynamics with cultural mix. This has been a challenge for even experienced Scrum Masters. To address this, we address Behavioral Norms, Cultural Preferences, Inclusion and Conflict Management explicitly in our Team Effectiveness Workshops.

    You have helped me and I hope this helps others.

Leave a Reply