14
WORKING DRAFT Last Modified 5/10/2016 4:33 PM India Standard Time Printed Gamify Release Planning

Gamified release planningvf_for share

Embed Size (px)

Citation preview

Page 1: Gamified release planningvf_for share

WORKING DRAFTLast Modified 5/10/2016 4:33 PM India Standard TimePrinted

Gamify Release Planning

Page 2: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

RULES OF THE GAME

1. Self-organize into small teams no larger than 8 2. Identify the team roles (multiple business sponsors, product

owner, architect, dev team, ScrumMaster)3. PO is the decision maker 4. Scrum Master will oversee all exercises and keep time check5. At the end of each exercise, teams will present their work

Page 3: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

Cross 5 levels to get to the release backlog/MVP features

1

2 3 345

MVP features in

5 steps

Page 4: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

Level 1 Success – Personas Defined

Personas areArchetypal users

Based on observed behaviors patterns and goals

Represent the needs of many

Persona definition must have visual, role, tagline, goals or top features as s/he sees in the product

1. Split into teams. Come up with relevant user personas

2. Reconvene as a group and finalize personas

3. Team has personas defined? If yes then Level 1 completed

Personas helpProvide focus

Determine what the product should do and how it should behave

Communicate with stakeholders and colleagues

Get people committed to the design

Measure the design’s effectiveness

1

Page 5: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

Let’s Play:Level 1 (10 minutes)

Page 6: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

Level 2 Success – Feature wish list defined

21. Split into teams and role model a persona each.

2. Come up with top X features as that persona

3. Reconvene as a group, discuss and merge feature wish list and identify the personas it applies to.

4. Team has feature wish list defined? If yes then level 2 completed

Feature wish list isAll the features that will be useful for a persona

No prioritization is needed

X can be 10 or 15 or as many as the team feels is relevant.

Features wish list helpsThink about the whole product and set the future vision

Yvannova Montalvo
In business, a product feature is one of the distinguishing characteristics of a product or service that helps boost its appeal to potential buyers, and might be used to formulate a product marketing strategy that highlights the usefulness of the product to targeted potential consumers.Read more: http://www.businessdictionary.com/definition/product-feature.html#ixzz47poChvaf
Page 7: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

Let’s Play:Level 2 (15 minutes)

Page 8: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

Level 3 Success – MoSCoW and KANO (Wow factor) added

1. As a team take a feature

2. Add Must, Should, Could and Won’t as per MoSCoW.

3. Add if the feature will add to the Wow factor

4. Team has feature wish list with MoSCoW and Wow? If yes then Level 3 completed

MoSCoW isMust, Should, Could and Won’t have features

WOW factor isSimplified KANO model

Add if the feature will add to the Wow factor to the product or not

3

Page 9: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

Let’s Play:Level 3 (10 minutes)

Page 10: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

Level 4 Success – $ value attached to each feature

1. Architect and development team takes the lead.

2. Give a $ value to each feature as per IT development complexity.

3. Sponsors are only listeners here

4. Team has dollar value for each feature? If yes then Level 4 succeeded.

$ value isIT development complexity measure

100$ is the relative measure of the development effort the team can spend in delivering the MVP.

$ value isn’tBusiness Value

4

Page 11: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

Let’s Play:Level 4 (10 minutes)Sponsors think about prioritization!

Page 12: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

Level 5 Success – Spend your $100 and create release plan1. Real fun bit, the sponsors have it all to

buy the features now.

2. Sponsors take a lead and decide how to spend their $100.

3. Team has the MVP backlog now

4. Now you are ready to map the features into sprints for your release plan.

5. Do you have your release plan ready? If yes, then you just won a jackpot!!!

Buy features helps inDeciding what feature is worth spending dollars

Also with personas, MoSCoW, Wow factor and dollar value at one place sponsors know what will be the business value achieved.

5

Story mapping your release plan ensuresDependancies of stories are taken into consideration

Time factor is taken into account

Page 13: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

Let’s Play:Level 5 (20 minutes)

Page 14: Gamified release planningvf_for share

Last Modified 5/10/2016 4:33 P

M India S

tandard Time

Printed

McKinsey & Company

THANK YOU

Email: [email protected]

Email: [email protected]