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
The Big Guess Up Front (BGUF)
The way we used to deliver Business Intelligence projects was to do what I call the “big guess up front” (BGUF). No more!
Boil boil toil and trouble – 3 Data Mining recipes
As part of the work we are doing to develop our one-day workshop titled 'from data analyst to data scientist', we have been researching the CRISP-DM methodology as it's a core part of one of the workshop modules. There are three main data mining methodologies that are...
The death of the 100 page BI Strategy
The AgileBI approach has fundamentally changed the way and the more importantly the focus of why we deliver Business Intelligence strategies.
AWS – Remember to check your Region
We play with a lot of the new stuff in AWS when it comes out to see what it does, how it works and to think about how we can incorporate it into what we do to remove manual effort. Every now and again we see a feature documented and for some reason can't seem to find...
Retrospective – No Meetings
As I outlined in my earlier blog AgileBI fundamentally changes the team’s traditional view of meetings. It’s interesting watching how new teams adapt to this change. An example from one of the teams I worked with recently is …
AgileBI Culture Change – No Meetings
One of the biggest challenges of using Agile methods to deliver BI projects, is the massive change in the way the team has to work.
3 Free Things
I was talking to somebody recently who had been dropped into the deep end in the world of Business Intelligence (so to speak) at their organisation and wanted to know what was required to be able to deliver information and some advanced analytical models. I was...
Gartner Magic Quadrant 2016 – The BI Landscape has finally changed.
Gartner have released their Magic Quadrant for 2016 and OMG the BI market has substantially changed according to Gartner. In fact, for those of us who love more emotive sentences, you could say there has been a blood bath! The first thing to notice is that...
Agile Data Engineering – Hyper Adoption
Ralph Hughes covers extensively in his book the concept of delivering Agile Data Engineering using Hyper Normalisation and Hyper Generalisation modelling techniques.