First of all: what is a Scrum Master
The scrum master is the team role responsible for ensuring the team lives agile values and principles and follows the processes and practices that the team agreed they would use.Agile Alliance
When was the Project Manager time over?
I’ve been working at Santander Bank for the last 20 years. That make me a Black Screen Boy. Also Know As a technologist whose professional career has been developed by programming in languages that are now dinosaurs.
About 6 months ago my career had an unexpected twist. I was proposed a new challege: how many times have you joked with friends saying: “if I got caught with what I know now and a few years less, they were going to find out”?
Well, this was the challenge: do the same as 8 years ago, but in another way. More efficient, with new technologies and improving the Time-to-Market (T2M). I was asked to work with another methodology instead. They wanted me to forget about the traditional Waterfall methodology and use the Agile Framework methodology.
👉 If you have no clue about Agile, read our post: What is the Agile methodology?
What are Agile Ceremonies
So, I accepted the challenge. My first surprise: the whole responsibility for what happened during the project was no longer of the Project Manager. The team was the one who got involved and established how much time and at what time they made the deliverables. And the Agile ceremonies appeared.
💡 You must know: in Agile, meetings are called “ceremonies”.
- Daily Meeting: At the same time each day the team meets so as to bring everyone up to date on the project. Here the Scrum Master normally asks three questions: What I did yesterday, What I plan to do today, What is getting on my way.
- Sprint Planning: In this ceremony, the Product Owner tells the team the User Stories, previously prioritised – this is the Product Backlog.
- Sprint Review: In this ceremony, the team shows to the Product Owner the functionalities that have been developed.
- Sprint Retrospective: In this ceremony the Product Owner, the Scrum Master and the team analyze what has been done in the Sprint presented and decide concrete measures to improve the results.
This made me discover that the Project Manager role has nothing to do with the Scrum Master role. The success of a Project Manager lies in the success of the project. The success of a Scrum Master or Agile Coach lies in setting up a high performance team. And for this, my brain had to “deprogram” what I had learned from project management.
Reinventing yourself in the Agile methodology
I had to reinvent myself to stop using predictive methods of project planning and estimation, and focus on what ultimately matters: people. They are what make things go from a blank page to something tangible, palpable and real.
As Lyssa Adkins says in her book Coaching Agile Teams in the episode The road from Project Manager to Agile Coach: “Breaking mindset with some radical thoughts…”
|PROJECT MANAGER||SCRUM MASTER|
|We can plan the work and work the plan||Planning is essential; plan are useless|
|The triple constraints can be traded off for one another to correct for unknowns||Time and budget (people) are held constant. Only scope flexes.|
|The plan gets more accurate over time as we flesh out the project through phases of activity: requirements, design, development, testing, and so on||A plan gets more accurate over time because it is constantly revised and trued up to the team’s actual performance|
|Delivering on time, within budget, and on scope equals success||Clients getting the business value they need is the only measure of success|
|Scope can be locked down with later discoveries being handled as change requests against the scheduled end date||Scope remains flexible, and changes of any kind are welcomed even late in the project|
|Controlling through the project plan is my job||Controlling through a plan is not possible; releasing the team into the safety of agile is my only measure of control. So, I coach the team to use agile well|
|Completing tasks and delivering deliverables indicate progress and value delivered||Only delivered end products indicate progress and value delivered|
What have I learned?
I have learned from collaborative work, how each person in the team emerged their own character to help the common goal of the project.
To be honest, it took me a lot to understand the Scrum Master role. It was hard for me to understand this role is passive and not reactive. Understand that is a role of facilitator who is available to the team, just waiting for them to raise the needs, and not to anticipate them. This I have understood and internalized.
Once here, I could join the Agile Framework. To his way and methodology of doing things. The MVP (Minimum Viable Product) delivery arrived; defined by the team and that had its climax in the last Sprint Review, when all stakeholders applauded and showed their satisfaction. And my satisfaction was to see the smile and the joy of that great team to be aware of a well done job… and that the “roller” in which they had become as builders of a product had just started.