I was part of “Slicing Features into playable stories” session by Tarang Baxi in Agile 2012. Case studies Tarang presented were very effective in emphasizing the principles behind Slicing features into stories. Let me try to put down two case studies which he discussed.
First one was about an ipad app to allow users (travelers of an airline) to complete check in online via their ipad’s. This app is intended to support users in 12 countries. Also, most of biz logic is shared with website and other mobile apps which mostly is already in place.
General outline of the requirement was something like this
- Initiate check in
- Ability to search via last name,PNR
- Show a reminder letting user know that his flight is open for checkin (sort of check in notification)
- Login into account and use a dashboard page which displays booking history (My Trips) and check in button next to it (both already in place)
- Check in info
- Passport info etc for international travel
- Each country has its own UI layout e.g. Japan has last name then first name
- Country specify information if any
- Extra / check in luggage
- Add ons
- On board meal
- Payment for add on’s or luggage
- Seat selection
- Check in and send boarding pass based on user option/input Via email or To ipad
Now the question is what’s the best way to slice stories out of this feature (check in feature)? Product owner also mentioned that most revenue generating piece is obviously “Add ons”.
Principle: When slicing user stories, always ensure you get one thinnest slice end to end. In this case, first story team should focus on would be to get a base minimum flow to complete check in. It could look something like.
I’ll talk about next case study in my next blog.