Format: Tutorial
Duration: 90 minutes
Abstract
This tutorial will give answers to the following questions:
- What is a Product backlog (PBL)?
- Who owns the Product backlog?
- Where do the input come from?
- What format should the items of a Product backlog have?
- How to prioritize a Product backlog?
- Detailed description and timetable
- The tutorial will focus on how to create and maintain a Product backlog according to Scrum. The strategies and methods possible to use will be explained and the participants will get the opportunity to practice some of them in short exercises.
- Among the things to be covered are: user stories, user role modelling, story writing workshops, granularity of the PBL, * how much should the PBL cover, prioritization techniques.
They will also get the opportunity to discuss important aspects of the Product backlog creation.
Timeschedule (minutes):
- 0-5 Introduction of presenter
- 5-15 Introduction of topic (general overview)
- 15-25 Discussion exercise: challenge! what to do when given a list of requirements of 1800 items?
- 25-40 Presentation of strategies (how to create a PBL, how to get input to a PBL, how to maintain a PBL)
- 40-50 Discussion around strategies
- 50-65 Presentation of techniques and methods (formatting and organizing a PBL, PBL iceberg, prioritizing a PBL)
- 65-80 Exercise: use of selected technique
- 80-90 Summary and conclusions
Biography
Arne Åhlander is a Senior Consultant using Agile and Lean methodologies to improve product development and management for several larger software organizations.
Arne has 15 years of experience from the software industry, to a great part in the area of product management where he have held several senior positions. Arne has managed Scrum projects, helped customers start Scrum initatives, and was appointed Certified Scrum Trainer in November, 2008. He became one of Sweden's first Certified Product Owners in November 2006.
Arne is based in Malmö, Sweden, employed by Softhouse and an active member of the SW Business Improvement team. He holds a Master of Science in Electrical Engineering at Lund University, Sweden.
Comments (3)
Jul 21, 2009
Vasco Duarte says:
Even if the Abstract mentions several possible issues people may face when manag...Even if the Abstract mentions several possible issues people may face when managing/using a backlog, the agenda seems to focus only on dealing with a Product Backlog that has grown too long (too much inventory of requirements?).
The agenda or the abstract should be a better reflection of each other.
Specifically on the issue of a backlog that grows too large there are some issues that are interesting but none of them are mentioned in the abstract (e.g. themes/epics à la Cohn ,the granularity of each item, how far should we look into the future, etc.).
Jul 31, 2009
Marko Taipale says:
A quote from a product owner of my previous customer: "15% of my work is about g...A quote from a product owner of my previous customer: "15% of my work is about getting items down to a product backlog (in correct format and size), all the rest is about figuring out what actually should be there and why". Getting into that why would be really interesting but maybe it is not part of the tutorial?
Anyway, I like your promise about questions answered :o)
Aug 03, 2009
Vasco Duarte says:
This page was updated. Read through it again if you have commented/read it befor...This page was updated. Read through it again if you have commented/read it before