The Value Uncertainty Game

Slides:



Advertisements
Similar presentations
Iteration Planning.
Advertisements

Agile and Scrum: Executive Summary June 2, 2011 Bob Schommer, CSP, PMP, MCTS Senior Project Manager Skyline Technologies, Inc.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.
IAgile – iNetFrame’s framework for agile development Features Get to see a working product early Development shadows evolving requirements Pair programming.
ECE44x SCRUM Overview slides adapted from Marty Stepp
Agile Project Management with Scrum
Process and tools Individuals and interactions over Following a plan Responding to change over Comprehensive documentation Working software over Contract.
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
Scrum CS These slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
 User assignments (product owner)  ‘circle’  1 st sprint: ◦ Scrum Boards (informative workspace)  Product -, release -, sprint -, defect backlog 
Scrum 1.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
CSE Senior Design II Staged Delivery Instructor: Mike O’Dell.
Kanban and large-scale strategic planning
Change Request Management
Agile Methodologies for Project Management By – Komal Mehta.
Kanban “Signboard”.
© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Deeper Dive Into: User Stories.
What is Scrum Process? Where is it used? How is it better?
Copyright David Churchville - XP and Agile Planning David Churchville ExtremePlanner Software XP Fishbowl.
University of Sunderland COM369 Unit 8 COM369 Project Monitoring and Control Unit 8.
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
Release and Iteration Planning September 13, 2008.
Agile Concepts - II “Agile” Estimating & Planning Nupul Kukreja 5 th November, 2014.
Stand Back and Deliver With the Purpose Alignment Model Todd Little, VP Product Development at IHS.
04 | Define a Software Iteration Steven Borg | Co-founder & Strategist, Northwest Cadence Anthony Borton | ALM Consultant, Enhance ALM.
Copyright 2013 GHSP | A JSJ Company 2 Supply Chain Portal - Creating an ASN Discover, Align, Deliver. Worry Free. GHSP.
From why, to what, to how much FROM reality TOTO Kelley Horton.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
SCRUM.
CSE Senior Design II Staged Delivery Instructor: Manfred Huber Partially adapted from Mike O’Dell.
Planning Extreme programming
Text Firefox Metro Project Production Pipeline. Text Our Approach.
Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Barnes & Noble Alonda Morgan. Agile UX Agile.
PA Techcon: Project management
Change Request Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
COMM02 Project Monitoring and Control Unit 8
Project Management with VSTS
Scrum.
Scrum and TargetProcess
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Scrum Management
Materials: Three die Cup Medium-sized short container Directions: Shake the die in the cup and drop them in the container (this helps keep the dice from.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
To Estimate or #NoEstimates, that is the question
Mike Cohn - Agile Estimating and Planning
By: By: Agile Scrum Master Online Training.
Product Backlog List of things that needs to be done to make the product come into existence 
User Stories Applied, Mike Cohn Chapter 1: An Overview
Scrum MODULE 3 – Part 3.
Burn Down charts for Project Management
Johanna Rothman Agile Team Measurements Chapter 12
Summarizing Our Models to Date
Johanna Rothman Know What “Done” Means Chapter 11
The Value Uncertainty Game
© University of Liverpool
Introduction to Agile Blue Ocean Workshops.
Johanna Rothman Rank the Work Chapter 7
Daily Actions Start: Have a flow-planning meeting to plan day’s strategy Decide how to use your total effort points Pull in as many cards as you want and.
User Stories Applied, Mike Cohn Chapter 1: An Overview
Scrum in Action.
Scrum/Kanban Overview
Presentation transcript:

The Value Uncertainty Game Todd Little VP Product Development IHS

Estimation Exercise

Simulation Exercise ID: 1 Value: Sum of all dice Major feature   Test: Roll 3 dice - 2 or more dice are the same

ABC’s of Prioritization

The A/B/C List sets proper expectations MUST be completed in order to ship the product and the schedule will be slipped if necessary to make this commitment. B Is WISHED to be completed in order to ship the product, but may be dropped without consequence. C Is NOT TARGETED to be completed prior to shipping, but might make it if time allows. Only “A” features may be committed to customers. If more than 50% of the planned effort is allocated to “A” items the project is at risk.

A/B/C List Typical Delivery Backlog Plan A B C D C A B 50% 25% 25% A B C D Typical Delivery C A B Backlog Plan Target Delivery Date 50% 100%

A/B/C List Uncertainty Risk Backlog Plan A B C D C A B 50% 25% 25% B C D Uncertainty Risk C Need some explanation to go along with this slide and the previous one. --The idea is that there is uncertainty in the estimation process. A factor of 2X is a generally sufficient buffer if the team has gotten basic estimation down. Thus is it possible that what is actually delivered is only the “A” items. That is ok and actually expected. A B Backlog Plan Target Delivery Date 50% 100%

Estimation and Prioritization XL L M S Priority Value Cost

Simulation Exercise ID: 1 Value: Sum of all dice Major feature   Test: Roll 3 dice - 2 or more dice are the same

Example Story Fail Value = 3+1+3 = 7 ID: 1 Value: Sum of all dice Major feature   Test: Roll 3 dice - 2 or more dice are the same Fail Value = 3+1+3 = 7

Stories and Scoring We will run 3 iterations, with 10 rolls of the dice per iteration WIP limit of one story in progress Must commit to 6 stories for the release, and 2 stories per iteration ID: 1 Value: Sum of all dice Major feature   Test: Roll 3 dice - 2 or more dice are the same Points are scored for accepted stories. Value is just an estimate…the market will decide

Release Planning (5 minutes) Estimate how much time each story will take, S, M, L, or XL Estimate how much value each story will have. Map onto the value/cost chart Prioritize and commit at least 6 stories. Get 10 commit points per story committed and delivered. Miss any commitment and you will get 0 points. Mark committed stories with an “A” Mark remaining stories with a “B” or “C”

Estimation and Prioritization XL L M S Priority Value Cost

3 Iterations Estimation updates Story signup Estimate any new stories Tweak any of the prior estimates if desired Story signup Commit to at least 2 stories by pulling them into the Iteration Backlog You get 5 points per committed story delivered. If you miss any commitment you get 0 commit points for that iteration. If you deliver a story that is not committed you get 0 commit points for that story

Special Actions It is ok abandon a story It is ok to redo a story You can come back to it later It is ok to redo a story Pull it back into the backlog Work it just as before to pass the test If the new development is not better than the previous result, then revert to the previous result.

Estimation and Prioritization XL L M S Priority Value Cost

The Progress Board Backlog Committed In Work Accepted Committed for this release (A) Cutline Potential stories Committed for this iteration In Development Passes test criteria

Keeping Score Iter Day Story# Red Green White Blue Value Pts Iter Commit Rel Commit 1   2 4 4  5 3 60  1  3  7  6 7 8 9 10 Total

Keeping Score ID Category Value Test Priority (A/B/C) Rel Commit Iter Commit Rel Com Pts It Com Pts Cost 1 Major feature Sum of all dice Roll 3 dice - 2 or more dice are the same A     X  1 2 Sum of matching dice Roll 4 dice - 2 or more dice are the same B 3 Research product of dice Roll 2 dice - 2 or more dice are the same C  4 Major Research Roll 3 dice - Three consecutive integers (straight) 2  5 Moderate enhancement Sum of all (3) dice Roll 3 dice - No 1s 6 Roll 3 dice - No 6s 7 Enhancement Sum of all (2) dice Roll 2 dice - No 1s 8 Roll 2 dice - No 6s 9 Incremental feature Sum of all (1) dice Roll 1 die - No 1s 10 Roll 1 die - No 6s Total