Tuesday, September 2, 2014
Sarajevo Special Scrum.org Product Owner Training
Wednesday, January 15, 2014
The Antibiotics of Software Engineering - Agile Testing
Monday, June 3, 2013
Leader, your team is not in the meeting room!
Monday, April 1, 2013
fire prevention and firefighting
Moving around large Agile projects, I came across a common situation that hinders the team performance. Individuals cannot allocate time for improving their work (and avoid future problems) because they are constantly firefighting current issues.
Everyone is busy putting out fires -> no time to improve (and avoid future fires) -> more fires
It takes discipline! Finding the balance between fire prevention and firefighting is not easy. You still need the fire sirens. But some experienced firefighters should be out of the fire department before the fire siren alert. Think preventive and proactively!
Monday, August 27, 2012
Agile in the Large-scale GSD: Success or Sudden Death?
- Darja Smite, Blekinge Institute of Technology
- Nils Brede Moe, SINTEF
- Casper Lassenius, Aalto University
- Paulo Caroli, ThoughtWorks
- Jude Fernandez, Infosys
- Miikka Penttinen, Tieto
Thursday, March 29, 2012
Timeline activity for retrospective
Below is a deck for a timeline activity I used on my last retrospective.
Previously I have used this approach for a collocated retrospective. I would draw a timeline on a white board, create 4 areas on the board (people, process, tools/technology, and other), and use two colors of notes (well – green /not so well - gray) to start with, followed by a third color for action items (yellow).
Here is the snapshot of the retrospective activity (this picture was generated by Google Drawing):
Friday, February 3, 2012
Back to the basics: What made this Agile Inception especial?

A little bit of history: For the past two years I have participated directly in 3 Inceptions, and indirectly in 5 inceptions. By directly, I mean, I was sitting in the war room for most of the Inception sessions. And by indirectly, I mean, I was participating on the Inception sessions over video from a Nearshore location (onshore is San Francisoc, USA, nearshore is Porto Alegre, Brazil).
I attribute the success of the last Agile Inception to 3 things: collocation, war room, and colorful post-it.
Collocation
Don’t under estimate the value of a face to face interaction. I am currently in Brazil and I am used to having effective meetings over video and phone with USA. I know that technology can bring people closer together, and, perhaps, we can work together without sitting next to each other. However, the face to face during Inception will bring the team together in a way that it will be worth each penny spend for making the collocated Inception a reality.
I compare it to dating and internet dating. Relationship development goes to another level when the whole team is at the same room. Think creatively on how to save on costs. In our case we were able to reduce the collocated period by having a pre-Inception period before the collocate Inception. Spikes, research, data gathering, codebase analysis were the sort of activities we did in the pre-Inception week.
War room
Keep a single room for the team during the intense Inception period: the war room! The room should fit all team comfortably. It must have a clean table and wall space. The room should also have a cabinet or a box with index cards, colorful post-its and pen.
The war room makes the environment for collaborative sessions. It also avoids the waste of time of people moving from one room to another. Another important point is about carrying the information between rooms. You can either carry all hand-written notes (index cards, post-its, flip-charts, etc) and put them back in the wall and tables, or upload them on a digital format and carry it on your laptop. The former option is a waste of time. The later lessens people interaction. There is no replacement for writing on and tearing apart colorful post-it or index cards. Once the information goes to the computer, it will not get back to paper. People interaction reduces as there is nothing on the table to gather around.
colorful post-its
Do not bring a list of existing user stories to the Inception. I am sure there is a list somewhere (excel, Jira, or alike). Use it for reference, but don’t use it for driving the Inception sessions. Print a few copies and bring them to the war room. Let people consume it if required. Try not to read items from a list during a collaborative session. In fact, do not build a list while in a collaborative session.
Group people around colorful post-its. Write and place post-its either on the table or at the wall.. Talk about them. Write a few more. Tear them apart. Make use of colors. Reorganize it. The collaboration from using such basic, low-fi technology— colorful post-its and pen—cannot be matched by any digital alternative (file sharing, projector, spreadsheets, etc).
The picture below depicts a great example from my last Inception. Without a previous encoding, the team decided to use the colored small post-its for personas. User Stories (in green post-its) were placed on white index cards containing numbers and estimated (with notes on the back).
On future posts: user story mapping for driving Inception, and a few notes on Inception facilitation



