Posted in my 2 cents

Scrum Master Service to the Product Owner

From the Scrum guide:
The Scrum Master serves the Product Owner in several ways, including:

  • Finding techniques for effective Product Backlog management;
  • Helping the Scrum Team understand the need for clear and concise Product Backlog items;
  • Understanding product planning in an empirical environment;
  • Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;
  • Understanding and practicing agility; and,
  • Facilitating Scrum events as requested or needed.

How much are you coaching the PO and the Dev Team? Are you just a secretary or a proactive SM? Are you stressing the PO to create right user stories or just accept everything he ask?

Posted in my 2 cents

Scrum Master Service to the Development Team

From the Scrum guide:

The Scrum Master serves the Development Team in several ways, including:

  • Coaching the Development Team in self-organization and cross-functionality;
  • Helping the Development Team to create high-value products;
  • Removing impediments to the Development Team’s progress;
  • Facilitating Scrum events as requested or needed; and,
  • Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.

How much of those point are you really working out on your daily basis?
In a scale from 1 to 5 try to vote yourself in all of those points.

Posted in my 2 cents

Scrum Master Service to the Organization

From the Scrum guide

The Scrum Master serves the organization in several ways, including:

  • Leading and coaching the organization in its Scrum adoption;
  • Planning Scrum implementations within the organization;
  • Helping employees and stakeholders understand and enact Scrum and empirical product development;
  • Causing change that increases the productivity of the Scrum Team; and,
  • Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.

How much of this rely truly on the SM shoulder? How much on the Agile Coach? What’s your experience? As SM are you practicing this part of your duties?

Posted in my 2 cents

Transparency vs Openness

Transparency (the definition by book)Significant aspects of the process must be visible to those responsible for the outcome. Transparency requires those aspects be defined by a common standard so observers share a common understanding of what is being seen.
Openness (the definition by book)

As we work together, we express how we’re doing, what’s in our way, and our concerns so they can be addressed.
What’s the difference (IMHO)

Transparency refers more on having a common language that everybody inside and outside the team understand.

For example sharing Goals, DoD, DoR, User Stories, Burn-down chart. 

Openness is about to say what have need to be said. Without blaming but with open and courage. I’referring when we describe an impediment or we reject a unready User story or propose a new breaking idea. 

It’s not about saying everything to everybody but the right things that could probably hurt a bit but are needed in order to reach goal and preserve values. 

That’s my opinion, what’s yours?

Posted in my 2 cents

Effective communication in a distributed Scrum team

Since I’m working in a distributed team for nearly 3 years I can share some thoughts

Scrum is simple, but is not easy to apply

let me add

…and it’s even more evident in a distributed team.

Let’s first take a look at the situation:

  • different timezones
  • non-native language speakers
  • different environment/infrastructure
  • poor communication

Continue reading “Effective communication in a distributed Scrum team”

Posted in books and articles, good resources, inspiration

How to improve scrum values in the team

I was reading this 2016 article from Dave West, which is very interesting since he suggests some simple ideas to improve scrum value in the team:

  1. Put the values on a wall and have each team member write up how they are going to demonstrate the value in their working day.
  2. Add a ‘values moment’ to your retrospective. This gives everyone an opportunity to inspect and adapt on their values.

you can 3 find more on the Dave’s article.


Posted in good resources, inspiration

Keeping Retrospective fresh

Today i was attending an interesting webinar about the topic “Keeping Retrospective fresh”, here my notes.

Why do we retrospect?

First of all it’s clear we make retrospectives not because the Scrum guide says we should, but because we want to understand and improve performance!


Warning signs of ineffective retrospectives & root causes

Because doing things is not the same as getting things done

Continue reading “Keeping Retrospective fresh”

Posted in inspiration

Inspire the change

One of the Agile value is “Responding to change” but how it’s possible if we suffer of inertia to change? Let’s be inspired by those wise words:

He who becomes the slave of habit,
who follows the same routes every day,
who never changes pace,
who does not risk and change the color of his clothes,
who does not speak and does not experience,
dies slowly.


Continue reading “Inspire the change”

Posted in my 2 cents

Be a role model, lead them by good examples

Let me be brutal: everyone wants the others do what he thinks is the best. Someone reach this goal with his authority, someone is authoritative. Someone over-rule others with power, others are well-informed and considered experts on their field.

A scrum master is an unpowered role by definition and while he should be well informed, hardly is an expert like a senior developer. How can we drive the team in the right direction? If you read the title you know yet: by good examples, be a good example for your team. Continue reading “Be a role model, lead them by good examples”