Project Managers who have done standups
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
SFT – The art of Innovation – break it and then fix it
Innovation is a popular word these days in business. Good old Wikipedia defines it as "Innovation is the application of better solutions that meet new requirements, inarticulated needs, or existing market needs." But being innovative is not simple. And often the...
Day 1 – Overview, Vision, Scope and Accountability
So day one is down and it was a day of setting the vision and starting the definition of the scope (the Dev team were off sick, so it was only a 1/2 a day) The Process The day started with a quick whiteboard overview of the entire Agile Scrum Framework and this...
I’m getting flexible – a week of Agile ahead
I love learning new stuff! The six months I spent at Xero has probably been my most intensive learning experience I have had, and in retrospect it was due to the fact it was total immersion, completely focussed on delivery (having Rod Drury walking the floor behind...
Dynamic Data Driven Urls coming in SAS VA 6.3
Kathryn has just spent part of last week mentoring a SAS VA customer in Australia. We love this type of work because we help out customers help themselves (rather than black boxing delivery and forcing them to pay us for every change) and because we always learn new...
SFT – Watch the end of the runway
Often in a project we focus on the wrong things. Lets look at a project with the goal of building a plane that will take off. The challenge is that while we are building the plane it is slowly moving towards the end of the runway. Once we run out of runway the...
SFT – What is cloud computing?
Cloud computing is the latest buzz word and in true IT style, we have invented a raft of TLA's to explain what it is (and isn't) as well as a myriad of versions to confuse people even more. PaaS, IaaS, SaaS, DaaS, public cloud, private cloud, hybrid cloud, BIaaS, How...
SFT – Don’t complain, suggest something better
When you find something you don't like a natural reaction is to complain. The people you complain to will often listen politely, but they won't typically do anything about it. (Unless you have something they really want, that they will lose if they don't rectify what...
SFT – Its not the idea, its the execution
Your idea probably isn't unique. But then again you probably haven't found anybody that has done it the way you plan to do it. So don't spend your time asking people to sign NDA's or telling them half of the story. Just go execute on it. If you not sure, or need help,...
Deloitte Fast50 2013 – Infographic
So have you heard that the Deloitte Fast50 for 2013 has been announced and we came 22nd 😉 Check out our Badge Well one of the cool things about the Fast50 is that there are a myriad of different companies, doing different things and all at different stages of their...