One week inception workshop – Porto Alegre Oct 2013

Please find below a few photos from the One Week Inception workshop at Porto Alegre on October 2013.

Here is the presentation (and reference guide for the activities).

Andre Faria wrote a great blog post (in Portuguese) about the One Week Inception AgileBRazil 2013 session.

More links:

• Energizer: Zip Zap Zoom 
• Collaborative Product Vision activity 
• Back to the basics: What made this Agile Inception especial?

Note to self:

•  A full day workshop will be even better than half day
•   Rename Day 4 activity from Flow and Estimation to Estimation and User Journey
•  Keep Doing: no presentation; whiteboard and hands on instead
•   Keep Doing: refer to past Inceptions and projects, but select one of the participants project to incept on
• Pair up with TC Caetano and Mauricio Sanchez for the next one

Thank you!

One Week Inception - presentation

Below is the one week inception presentation that Taina Caetano and I (Paulo Caroli) have delivering on a few events, including the AgileBrazil 2013.

The coolest thing about this presentation: it is a sequence of photos taken on real Inceptions.

Agile br one_week_inception from caetano_tc

A great Ice breaker for Energy Boost and memorizing names

Paulo: Zip Roger

Roger: Zip Marco

Marco: Zoom Mathias

...

Zip Zap Zoom is a great energy boost ice breaker. I made a small addition to it for helping the team memorizing each other names.

After the Z__ command (Zip, Zap, or Zoom), the person passing the imaginary relay has to say the target person name.

This keeps the energizer fun while helping the team memorize each other names.

Inception activity for discovering User Stories

On this blog post I share an activity I used on my last Inception.  I found this activity very useful to kick start the User Stories creation.

What are the goals of this project?

This question  triggered the conversation about the business goals for the project. 

Who will use this system? What are their roles?

These questions disclosed the personas (with their roles) for the project. Goals and personas were written on post-its. Large pink post-it was used for goals, and small colorful post-its were used for personas. This is shown on the photo below.

After having written a few goals and personas, the team started brainstorming for creating User Stories.

As a X, I want Y so that Z.

Note that X and Z were already known variables (personas and goals). We were now looking for the Ys.

So, what does X want from the system in order to achieve Z?

For example: What does an OPS dude want from the system in order to monitor the browser against system overflow?

User stories were being written...

Soon these stories were combined into features (blue post it). Usually a feature would have from two to eight stories.

This whole process was not linear and definitive. Index cards (for stories) and colorful post-it (goals, personas and features) were written and re-written a few times. Below are a few photos showing index cards and post-its.

Back to the basics: What made this Agile Inception especial?

The following two pictures depict the latest Inception I participated at.

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