• X
  • RSS
  • Articles by Story State
  • Templates
  • Take a Journey
  • Recommended Resources
AgileBI.Guru
MENUMENU
  • AgileBI Way
        • Introduction
          • The Journey
          • Leveraging the collective knowledge of others
          • Musings, Ramblings and Structure
        • Agile Overview
          • 5 Factors In Agile BI
          • Agile Myths
        • AgileBI Overview
          • AgileBI Team
            • The challenges and risks of being an Agile BI Manager
            • Product Owner vs Feature Owner
            • Architecture Owner
            • Project Managers who have done standups
          • AgileBI Discipline
            • No Meetings
            • Fit for purpose documentation
            • Making Retrospectives Fun
          • AgileBI Process
            • The Big Guess Up Front (BGUF)
            • The Danger of Pipelining and Time Slicing
        • AgileBI Portfolio
          • Scope
            • Mega Visioning
            • Vision
            • Vision and Scope
            • Value Mapping
          • Scaling with funding and resource
          • Information Product Roadmap
        • AgileBI Delivery
          • Gather
            • Information Products
            • Gathering Data Requirements
            • BEAM meets Data Vault
            • Wireframing to confirm requirements
            • Business Rules
        • AgileBI Automate
  • Templates
    • 1. AgileBI Gather
      • Information Product Template
      • BEAM Templates
    • 2. AgileBI Deliver
  • Patterns
  • Podcasts
  • Speak
    • DVEM Rising 2018
    • SAS Global Forum 2018
  • All Articles
    • By Story State
      • Done Done
      • Done
      • Underway
      • Backlogged
    • By Content Type
      • Concepts
      • Patterns
      • Process
      • Templates
      • Automation
    • By Tag Cloud
    • By Category
Select Page

Project Managers who have done standups

by Shane Gibson | 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.

I suggest you read Who should attend Steering Committees? next →

AgileBI Team Articles

This guy vs That Guy

Next Entries »

Submit a Comment Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Recent Drafts

  • AgileBI #17 – Flying the airplane while building it
  • AgileBI #16 – Plan Continuation Bias
  • AgileBI #15 – Leading agile data at scale
  • AgileBI #14 – Thoughts on the JAFAC conference
  • AgileBI #13 – A DataOps and Data Science Journey

Categories

Tags

Acquisition AgileBI AgileBI Delivery AgileBI Disciplines AgileBI Overview AgileBI Process Agile Fail Approach BEAM CDC Change Data Capture Code Template Data Template Fragile Games Incomplete Draft Information Products Introduction Methodology Myths Reqiurements Retrospectives SASGF Visualisation
  • X
  • RSS

Another Webbymade Site