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 – Just try it
So you have a good idea, but your not sure if it will work? It probably is, just try it. But make sure you minimise what you lose if it goes wrong. Want to hire somebody but your not sure they are a perfect fit? Who is perfect, just try them. But tell them your not...
SFT – Steering Committees Details Not Needed
Steering Committees are not there to discuss anything in detail, review any documents, or negotiate an outcome. Steering Committees are there as a governance group to ensure the project is on time, on budget, doing the right things, delivering the outcome that was...
The world of software licenses is changing
Apple shakes it up again The latest player to shake up the world of software licensing is Apple. They have released their latest OSX version, Mavericks and have decided to make the upgrade free. And it means no more having to pay to upgrade to the latest features on...
SFT – Customers Buy, you don’t actually sell
You never actually sell anything, a customer always buys something. You can't (legally) make a customer buy what you want to sell. But you can convince them that the thing you would like to sell, will solve a problem they have, at a value that makes sense, from people...
SFT – Accountability
So when a project fails, who gets fired or who doesn't get paid? When a job isn't done properly and a customer decides to go somewhere else, who is impacted apart from the customer and the shareholders? Or when an employee leaves to work somewhere else because a...
SFT – What makes you remarkable?
Seth Godin wrote in his book Purple Cow about being remarkable. He blogged how to be remarkable here. Being remarkable makes you different, it means you will be remembered and means your customers will (often) come back again. Today I had a remarkable experience from...
Why don’t we stick a label on “the business”
Im sat here writing a blog post about why data warehouses die, and I was about to write about that person called "the business". How many times have you worked on a a project where team members talk about "the business"? Its not a person, its not a organisational...
What makes a data warehouse die?
There have been a few different threads for me over the last couple of weeks all around what makes a reporting platform survive and thrive or die. A data warehouse by any other name (By reporting platform I mean data warehouses, analytical data marts, operational...
TDWI Putting the BI into BA and the 3 e’s
As I have blogged before I am a great fan of classifying what we deliver as a company by the 3 e's of Expertise, Experience and Efficiency. For me its a very simple way to focus a discussion on whether the thing we are taking to market will be "cheaper & faster",...