My partner Mel and me went on a short trip to Barcelona. We created a backlog with things to do, used backlog refinement and 1-day sprints to manage ourselves in the 3,5 days there. The following post describes our experiences.
A backlog for the trip?
Similar to an Agile software development project you normally want to get the best possible ROI (Return of Invest) from your holiday. The holiday ROI, of course, is different for everyone and not neccessarily connected to a monetary value.
Similar to a lot of projects out trip had a fixed time (in our case 3,5 days).
Mel and me have never been to Barcelona before, so we populated our backlog with sightseeing tips and places to eat from a city guide book as well as asking family and friends who have been in Barcelona before. (Asking my Facebook friends resulted in at least 15 Backlog items…\o/) And that was already the first version of the backlog! A very rough list with items on Post-Its like “Stroll through Barri Gotic”, “Eat Churros” or “Familia Sagrada”, but good enough to start our trip.
I experienced a lot of Agile projects that started the same way: An appropriately detailed list of user stories with no guarantee of completeness or sufficiency. That’s why we want the backlog to be emergent. For Mel and me this provided the best flexible way to travel and also the chance for serendipity.
Some of the backlog items were described with more details, information or restraints (our “acceptance criterias”) like “Get tickets online to avoid queues.” or the adress of the restaurant; mostly as a result of talking with each othet or reading the city guide. We also used diffferent Post-It colors for different types (sight, eating place, transport, …).
The first prioritization of the backlog and Sprint Planning was done at the hotel bar after we arrived late night in Barcelona.
Our Scrum Flow in a way then was then every night: Review (“What did we do today?”, “What was your highlight?”), Retrospective (“What can we do different tomorrow to have an even more awesome trip?”), Planning (“What do we want to do tomorrow.”). Backlog Refinement took place almost all the time, either because we read new stuff or liked places we wanted to re-visit (definitely El Born, “Looks like a nice restaurant/bar.”) or recognized we will not have enough time to do it and therefore threw away the Post-It.
Stakeholder, Product Owner, Scrum Master, Dev-Team
In a way the Scrum roles were implicitly realized:
Mel acted more like the Product Owner because she read the city guide more seriously than I did. Therefore she had better arguments on he ROI. I was more the Scrum Master because I pointed out several times that we can’t do all of the sights or made clear the consequences.
The Dev-Team was the people and the city of Barcelona. At least in a way: They not only offered us a wide range of possibilities on how to maximize our ROI but also “delivered” awesome sights. 🙂
Stakeholders or users were Mel and me ourselves, but also our family and friends (“Have you visited the place I told you to?”) or our employer (“Have fun and relax to be happy back at work.”).
[OK. The role comparison is a bit lame.]
Mel an me had a great time in Barcelona. It was the first time that we organized the things we want to do with a backlog, but both of us really loved it. Every evening we were happy and sometimes astonished how many sights we visited (moving Post-Its in “Done”). We gained very clear insights that we can never see all sights within those 3,5 days and felt OK with that.
We also understood that we should do a little more planning next time to avoid standing in front of a closed museum (although it was mentioned in the city guide… :)).
Molt de gust y fins ara!