Fabio Pereira

Retrospectives are usually conducted in order to keep the continuous improvement engine wheels working properly on a project. It is present on most of the agile processes I have worked with, such as Extreme Programming (XP) and Scrum.

The image below describes retrospective that most of us are used to:

On my last project at ThoughtWorks I had the opportunity to introduce to our client, together with Jason, a new type of retrospective, the Goal Driven Retrospective.

Goals and Actions

The Goal Driven Retrospective brings the idea that we should be much more focused on creating actions to achieve common goals shared and agreed within the team and also that will definitely add business value to the client.

Examples of goals:

• Zero bugs in UAT
• Productivity x 2: If a similar feature is required, the team should be able to implement it in at least half the time that they took at the first time
• Improve work environment

Examples of actions:

• Showcase and run selenium tests on IE to decrease number of browser dependency bugs in UAT
• Refactor JSP’s and create a DSL to specify exactly what varies from one story to the other
• Team lunch to improve work environment

It is essential that the person who is facilitating the retrospective, usually the Scrum Master, XP Coach, or Iteration Manager is aligned with the goals of the organization.

Values

In order to prevent conflict of interest, all the goals are defined based on values:

• Productivity
• Cost
• Quality
• Morale

By following these values the actions will make the team:

• Faster
• Cheaper
• Better
• Happier

All the actions must be aligned with all the values.

Some examples of actions that would not be acceptable because they go against values:

Where is morale?
What if someone suggests that in order for the team to be twice as productive they need to work 16 hours a day? If you just had that face and thought: “Come on, we know that this doesn’t work…” you are smart aligned with the values, but remember: this is not common sense.

Slow slow slow… what about productivity?
Or what if to achieve zero bugs in UAT we try to test and automate every single possible scenario in the whole application?

The picture below shows the output from the retrospective we had on the client:

I strongly encourage everyone to give it a go and try this new way of improving.

Technical Agile, AgileWall, IterationMgmt, Photo, Retro, Scrum, ThoughtWorks, XP

If you won the lottery and you saw 10 million dollars in your bank account tomorrow, what would you do? You would probably buy a lot of things… right? But actually you do not need everything you would buy, do you? Ok, you would have a lot of spare money, so there’s no problem.

But what if you had only a hundred dollars in your account? What would you buy? You would have to think about it more carefully and prioritize.

The product owner needs to define what is really important for him.
If you ask him what does he want for a 2 years project (10 million) he will say: “I want everything!”, but if you break down the project into small iterations (sprints) and ask him to prioritize what does he want for a small chunk of time, that’s when the important things come up.

A good way to show the product owner that he does not have 10 million available is making him buy features with a limited amount of money.

How does it work?

Before starting the poker chips session, we need a list of estimated user stories. We call it Master Story List (MSL), or Product Backlog. There are many ways of facilitating an estimation session, I like planning poker. But always remember: The team gives the estimates.

Basically you need to define how much a story point costs and give a certain amount of poker chips to the client according to the size of your iteration. And then ask him to buy what he wants for the next iteration.
It is interesting because from my experience as long as he has money, he buys everything, but then when he starts running out of chips, that’s when the real process takes place.

The output will be a list containing the most important user stories at that time.

Technical Agile, IterationMgmt, Photo, Prioritization, Scrum, ThoughtWorks

Last week I took the last pill from my Roaccutane treatment… At last…

Now I can have my glass of wine and also I can go to the beach… As you can see on the photo, now I can also get pregnant … lol

Personal

We had 8 user stories and we came up with this quick way of sorting them in the office. It was pretty quick… and simple.

Technical Agile, IterationMgmt, Photo, ThoughtWorks