Archive for the ‘ScrumOfficer learnings’ Category

Mission statement creation

October 24, 2010

One of my biggest challenges when I was assigned to be the ScrumOfficer at Abril Digital was how to unite the ScrumMasters and make them feel confortable following my lead, once I was younger than them all. I had the simplest idea one could have: why not build a mission statement for this team and with their own ideas? And that was what I did and it worked really well!

The brainstorming sessions

I organized a couple of sessions where each and everyone of them helped with their ideas of what our mission was. During this sessions not only they worked as a team, but also I was able to learn what each one of them was feeling about my leadership.

The result

After some sessions, the team finally agreed with this mission statement: “Orchestrate the realization of our organization’s business requeriments following the agile principles.”


After the mission statement creation no one had any doubt that I could lead them to a better future in our company, a future where the agile principles would start to be better understood.


A little help from a good friend!

August 20, 2010

They say that every people you happen to know in your life is there for a reason. If there is one person that I need to mention here is Guilherme Komel (@gkomel). A few weeks before our transition to our new job positions, he told me about a book that could help me fill the gaps to be able to accomplish my new tasks with ease. The book was: “How to win friends & influence people“, by Dale Carnegie.

The book

Yes, this book definitively had an impact on me. I recommend its reading for anyone in a position of influence. It teaches the right ways to approach people so that everyone will want to follow you and accomplish things in your name, once that things are related to a noble cause. A must read for every Agile Coach.

The Return of the Jedi

August 19, 2010

It was a long time since my last post. To be short: in a certain point in time I was a ScrumMaster and suddenly I was the manager of an entire ScrumMasters team, being responsible for the entire company’s software development process. Today I will start a series of posts about the learnings and insights that I had during this awesome period.

The Team

Our team was composed by 8 ScrumMasters and known as “ScrumOffice”, and I, the ScrumOfficer. Our main objective was to optimize the value chain between the business requirements conception until its delivery to the production environment, passing through development, of course. Our main pillars were: planning, conduction and optimization.

The Shepherd

My job was to guide the team in how to achieve excellency in our company’s Agile implementation, respecting the company’s constraints and trying to change/break/push/pull some of those constraints, paradoxically. And the tale started…