Challenge your product development department by a challenging contest with LEGO bricks: "Who Delivers Value First?" - Agile or Waterfall?
Product Owner Challenge is an agile game w/ Lego bricks. Its about challenging the product development to communicate clear objectives, requirements, and vision.
Slidedeck contains playing instructions, examples, and further info.
Material needed: (a) "Presentation User Stories for POChallenge", (b) "Process Cards for POChallenge" - both on my SlideShare account
2. www.plays-in-business.com
-2 - 29.09.2016
I’m Your Session Host Today
Michael Tarnowski
www.plays-in-business.com
URL: http://bit.ly/ProductOwnerChallenge
Downloads:
• http://de.slideshare.net/emte69/product-owner-challenge-30-agile-cambridge-2016
• http://de.slideshare.net/emte69/product-owner-challenge-30-process-cards
• http://de.slideshare.net/emte69/product-opoc-user-stories-v40
SW Engineer & Coder (C++, Linux)
Project manager (Air Traffic Management
IT consultancy:
• QA, PM, ReqEng, Testing, SDLC
• SW process improvement (CMMI, ISO 15504)
• Scrum Master, Agile Coach
Evangelist in Serious Play @ Work:
• Play@Work
• Cert. LEGO Serious Play Facilitator
• Cert. Innovation Games Facilitator
• Agile Games Fan
3. www.plays-in-business.com
-3 - 29.09.2016Minimum Viable Product… in a Nutshellhttp://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp
Not adding
components
incrementally
Instead adding
stand-alone
solutions – value –
incrementally
The Most Mysterious Thing…
4. www.plays-in-business.com
-4 - 29.09.2016Minimum Viable Product… in a Nutshellhttp://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp
Not
adding components
incrementally
Instead
adding stand-alone
solutions
– value – incrementally
The Most Mysterious Thing…
5. www.plays-in-business.com
-5 - 29.09.2016
The Minimum Viable Product
“MVP is a concise summary of the smallest possible group of features that will
work as a stand-alone product while still solving at least the “core” problem
and demonstrating the product’s value.”
-Steve Blank
From the “Gurus”
1. A tool to manage risk and maximize return on investment for new products – Frank Robinson
2. A tool to maximize learning from customers in high-uncertainty markets – Eric Ries
3. A tool to accelerate time-to-market by targeting the least demanding customers first – Steve Blank
“MVP is that unique product that maximizes return
on risk for both the vendor and the customer”
-Frank Robinson
Minimum Viable Product is that version of a new product
which allows a team to collect the maximum amount of
validated learning about customers with the least effort.
-Eric Ries
6. www.plays-in-business.com
-6 - 29.09.2016
Meaning of “Minimum Viable”
1. “Minimal” is as important as “viable”!
Most people concentrate on one at the expense of the other.
2. A solution that you can most quickly come up with, which will solve the
problem.
Does not matter if it is crappy.
Quickly means it is minimal and if it is solving the problem even in a poor
way, it means it is viable.
3. Whole point of a MVP is to show value enough to attract early adopters and
collect feedback. This feedback is what everything is all about. – MVP is a
tool for generating maximum customer learning in the shortest possible time.
12. www.plays-in-business.com
-12 - 29.09.2016
The Setuphttps://www.flickr.com/photos/wwworks/7291403658/in/dateposted/
For Each Table
Teams à 4 persons: 1 Product Manager/PO, 2 developers, 1 time-keeper
Each team select a Product Owner / Product Manager
Product Owner / Product Manager opens white envelope – and read:
Team Waterfall Team Agile
Product Owner / Product Manager picks a LEGO set and decides which
product will be built
Product Owner Challenge
14. www.plays-in-business.com
-14 - 29.09.2016
https://www.flickr.com/photos/wwworks/7291403658/in/dateposted/
Rules
Only Product Owner / Product Manager has the building instructions
Product Owner / Product Manager is not allowed to show the instructions
to DevTeam, nor to make pictures or scribbles
Product Owner / Product Manager is allowed to return to the plan as
often she needs to inspect
DevTeam has Lego bricks only, and no building description
URL: http://bit.ly/ProductOwnerChallenge
15. www.plays-in-business.com
-15 - 29.09.2016
https://www.flickr.com/photos/wwworks/7291403658/in/dateposted/
Game Objectives
Product Owner / Product Manager:
share product vision with your
DevTeam clearly and instruct team
as precise as possible to build the
product right
Process Objectives
Team Agile:
estimate how many sprints;
for each sprint do a planning
and a retrospective after to
improve
Team Waterfall:
PO/PM: try to slice your
deliverables in stand-alone
usable chunks
DevTeam: re-ensemble the
model as less as possible
16. www.plays-in-business.com
Twitter: @M_Tarnowski, @PlaysInBusiness
Facebook: http://bit.ly/PiB-FB
LinkedIn: http://bit.ly/MT-LinkdIn
Xing: http://bit.ly/MT-Xing
SlideShare: http://bit.ly/MT-SShare
Or call me:
+49-172-69 152 61
You Enjoyed It? – Drop me a note:
info@plays-in-business.com
This document may be further distributed free-of-charge in its original, complete form only. Please credit Plays-in-Business.com.
All images used are – if not stated otherwise – taken from flickr.com under Common Creative License.
Julien GONG Min, https://www.flickr.com/photos/bfishadow/3634884928/
Hinweis der Redaktion
Winston Walker Royce (August 15, 1929 – June 7, 1995) was an American computer scientist, director at Lockheed Software Technology Center in Austin, Texas.
He was a pioneer in the field of software development, known for his 1970 paper from which the Waterfall model for software development was mistakenly drawn.
Winston Walker Royce (August 15, 1929 – June 7, 1995) was an American computer scientist, director at Lockheed Software Technology Center in Austin, Texas.
He was a pioneer in the field of software development, known for his 1970 paper from which the Waterfall model for software development was mistakenly drawn.
Winston Walker Royce (August 15, 1929 – June 7, 1995) was an American computer scientist, director at Lockheed Software Technology Center in Austin, Texas.
He was a pioneer in the field of software development, known for his 1970 paper from which the Waterfall model for software development was mistakenly drawn.