Project Managers who have done standups

by | 3.1 - AgileBI Team, Concepts, Done Done

As a Stakeholder or Product Owner
I want to understand what experience and skills a Project Manager needs
So that I know if they are suitable as a Scrum Master

Often you will get somebody join your team as a Scrum Master who has in a previous life been a Project Manager.  It seems to be the natural transition, to move from a being Project Manager to being a Scrum Master.

In my experience they often make the worse Scrum Masters.

I often see a Project Manager joining the Agile Team as a Scrum Master because they have “done standups” before.  Unfortunately, lots of organisations seem to think that running standups is all you need to do to be Agile.

In an AgileBI approach there are a number of ceremonies that need to happen in each sprint:

  • Daily standups
  • Sprint planning
  • Prove it session
  • Retrospective
  • Backlog grooming

Like all roles to be a good Scrum Master you actually need experience in running all these ceremonies.  Especially if you have a delivery team that is new to an Agile approach.  Taking the team successfully through these ceremonies for the first few times takes skill and experience.

A novice Scrum Masters natural reaction is to introduce all the complexities of these ceremonies to the team in the first go.  This approach tends to overwhelm the team, it is much better to gradually introduce the concepts of each ceremony as the Agile Team participates in them, effectively allowing them to learn by doing.

Another key skill a Scrum Master needs to have is to be able to facilitate the Agile Team so that they form and storm and become self organising.  A Project Manager acting as a Scrum Master will either “talk at” the team, running through the list of tasks inplay and maybe at the end doing a “round the table” to see if the team need to add anything.  Or they will structure the standup so that the Agile Team are “reporting” to the Scrum Master rather than talking to each other.

A classic fail “tell” is when the standup goes from being less than 15 minutes to becoming a 1 hour talk fest.

A Project Manager is used to creating the plan themselves and assigning tasks to team members, rather than helping a team to become self organising.  They are focussed on the success of the outcome not the success of the team.  Helping an Agile Team to become self organising is the primary goal of the Scrum Master.  Once the Agile Team is operating successfully, the outcomes pretty much take care of themselves.

Out of interest, in my experience I have found a Data or BI Analyst often makes the best Scrum Master, and as well as a Project Manager, a Business Analyst doesn’t.

If I can’t get an experienced Scrum Master for a new Agile Team, then I would much rather identify a capable person who is a permanent of the organisation, with the right aptitude, and find a great Agile Coach to help them upskill.

AgileBI Team Articles

Benevolent Dictator

As a AgileBI Guru I want to understand what a Benevolent Dictator is So that I know when one is needed   The team have discussed it "to death" and are now constantly repeating the same arguements "around and around" More informaiton is neded to progress...

Remote Scrum Masters

As a Stakeholder or Product Owner
I want some examples of things that can fail in AgileBI
So that I know what to watch out for

Coaching the Product Owner

[[make them succesfull]] [[make them safe]] [[teach them what they don't know]] [[guide them in the right direction]] [[dont do it for them]] [[dont let them abdicate]]

AgileBI Team

As a BI Practitioner I want to understand what an AgileBI team is and isn't So that I know how to form and storm one Building a self organising team is one of the key factors required to deliver in an AgileBI way. Creating a team with T-Skills and helping...

Retrospective – Transferring Team Maturity

[[moved form one project to new one]] [[started at the place i left off]] [[hadnt taken new team on the journey]] [[new team also picked up some things faster and other things slower than last team]] [[art is reading people]]

Agile Team Maturity

[[teams go at different paces]] [[have to learn as they go]] [[may have had bad experience with agile]] [[need to fail to fix]]  

6 + 2 = 4

We get taught during our life that 1 + 1 can equal three when we leverage the power of a team. This is often true and in AgileBI ... [[scrum teams deliver more]] [[velocity]] But [[adding people mod sprint makes every thign slower]] So at the beginning 6 + 2 will...

Multiple Scrum teams

[[scrum of scrubs nope]] [[ two stand ups , inner and outer rings]] [[archutect sits on all planning sessions]]