As a < type of user >,
I want < some goal >
so that < some reason >.
Hypothesis is a supposition or proposed explanation made on the basis of limited evidence as a starting point for further investigation.
If < I do this > then < this will happen >
As a < type of user >,
I want < some goal >
so that < some reason >.
Hypothesis is a supposition or proposed explanation made on the basis of limited evidence as a starting point for further investigation.
If < I do this > then < this will happen >

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
Two of my colleagues came across a CRUD (Create / Read / Update / Delete) story, and asked me for advice on how to convince people on splitting stories.
I typically prefer to have smaller stories. In this case, instead of having one CRUD story, I would have one for Read, another for Create/Update and a story for Delete.
Here is an example.
As a online store owner, I want to Create / Read / Update / Delete products so that I can offer my customers the top rated products
Instead of having this CRUD story, I split it like this (I will add a few sample tasks for making it more illustrative):
As a online store owner, I want to Read (view) my products so that I can review what is current available on my site
Sample tasks:
As a online store owner, I want to Create / Update a product so that I can offer my customers the top rated products
Sample tasks:
As a online store owner, I want to Delete a product so that I can offer my customers the top rated products
Sample tasks:
Create DB table for deleted products
This sample is very specific for CRUD stories. There are other ways for splitting stories.
Mike Cohn's book, User Stories Applied is a must read on this subject.
Splitting (or deciding the size of a story) is controversial. Mike Cohn have popularized the INVEST acronym: Independent. Negotiable. Valuable. Estimatable. Sized appropriately. Testable
agree with the S in the acronym listed above: Sized appropriately.
But when I first read the INVEST acronym, the S was for small. I know Sized appropriately is not very specific, but it is more realistic. It is not about being small; it is about being sized appropriately. For this consider several reasoning on splitting your stories. The links below have more on this subject:
http://lassekoskela.com/thoughts/7/ways-to-split-user-stories/
http://agilecoach.typepad.com/agile-coaching/2010/09/ideas-for-slicing-user-stories.html