1 / 8

Gamify Release Planning

Gamify Release Planning. Cross 5 levels to get to the release backlog/MVP features. MVP features in 5 steps. 1. 2. 4. 5. 3. 3. Level 1 Success – Personas Defined. Split into teams. Come up with relevant user personas Reconvene as a group and finalize personas

kalb
Télécharger la présentation

Gamify Release Planning

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gamify Release Planning

  2. Cross 5 levels to get to the release backlog/MVP features MVP features in 5 steps 1 2 4 5 3 3

  3. Level 1 Success – Personas Defined Split into teams. Come up with relevant user personas Reconvene as a group and finalize personas Team has personas defined? If yes then Level 1 completed 1 • Personas help • Provide 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 • Personas are • Archetypal 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

  4. Level 2 Success – Feature wish list defined Split into teams and role model a persona each. Come up with top X features as that persona Reconvene as a group, discuss and merge feature wish list and identify the personas it applies to. Team has feature wish list defined? If yes then level 2 completed 2 • Features wish list helps • Think about the whole product and set the future vision • Feature wish list is • All 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.

  5. Level 3 Success – MoSCoW and KANO (Wow factor) added As a team take a feature Add Must, Should, Could and Won’t as per MoSCoW. Add if the feature will add to the Wow factor Team has feature wish list with MoSCoW and Wow? If yes then Level 3 completed 3 • WOW factor is • Simplified KANO model • Add if the feature will add to the Wow factor to the product or not • MoSCoW is • Must, Should, Could and Won’t have features

  6. Level 4 Success – $ value attached to each feature Development team takes the lead. Give a $ value to each feature as per IT development complexity. Sponsors are only listeners here Team has dollar value for each feature? If yes then Level 4 succeeded. 4 • $ value isn’t • Business Value • $ value is • IT development complexity measure • 100$ is the relative measure of the development effort the team can spend in delivering the MVP.

  7. Level 5 Success – Spend your $100 Real fun bit, the sponsors have it all to buy the features now. Sponsors take a lead and decide how to spend their $100. Team has the MVP backlog? If yes then you just won a jackpot. Your release backlog is READY!!! 5 • Buy features helps in • deciding 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.

  8. What next? • MVP features are handy, now • Prioritize • Deep dive and get going with your release • ALL THE BEST!!! • Help or feedback for the creator? Need the ready-made game? • @sharmajisha • https://jishasharma.wordpress.com/

More Related