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

Slides:



Advertisements
Similar presentations
Design Brief Example Your Name Here This is similar to what we use on the Cisco.com team.
Advertisements

Responding to Usability Issues Mary Chant, Certified Usability Analyst
STREAM ANALYSIS Diagnosing Organizational Change Peg Lucky & Tom Kriesel HPRCT 2010.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 1.
User problems, scenarios and storyboards
An introduction to personas
Copyright 2013 Proficientz, Inc. All rights reserved. The Most Fun & Rewarding Part of Product Management: Why Isn’t Anyone Doing It? John
Managing Difficult People
Renato Pinto López TUM18 - UPM. Sprint Planning Meeting ATTENDED BY PRODUCT OWNER (PO), SCRUM MASTER AND SCRUM TEAM PO DESCRIBES THE HIGHEST PRIORITY.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Calit2 approach to Community Projects Provide active support for Community projects Use of media technologies to understand the community Sponsor a course.
The team Definition: a group of people working together. Everyone who is to be part of a software development team, must have a good understanding of the.
[Title of meeting] [Name of sponsor] [Date] For guidance on working with PowerPoint and reformatting slides, click on Help, then Microsoft PowerPoint Help,
IAgile – iNetFrame’s framework for agile development Features Get to see a working product early Development shadows evolving requirements Pair programming.
Agile Teaming Concepts for and from the Facebook Generation Neil Rodgers NASA Enterprise Applications Competency Center (NEACC) 1.
 User assignments (product owner)  ‘circle’  1 st sprint: ◦ Scrum Boards (informative workspace)  Product -, release -, sprint -, defect backlog 
Muthu Swamy S, APSM, PMP, CSM, PM-2008 Friday, October 1, 2010
Berkeley’s User-Centered Design Process …a work in progress.
Sections2.4: Plan Business Analysis Communication 2.5 Plan Requirements Management Process 2.6 Manage Business Analysis Performance Kristee Watts May 7,
Defining Leadership.
William H. Bowers – Modeling Users: Personas and Goals Cooper 5.
User Modeling Lecture # 5 Gabriel Spitz 1. User-Interface design - Steps/Goals.
What is Scrum Process? Where is it used? How is it better?
Scrum’s Product Owner Role Jeff Patton Agile Product Design
Copyright David Churchville - XP and Agile Planning David Churchville ExtremePlanner Software XP Fishbowl.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Requirements Gathering this process determines exactly what is required (and not required) of a project Three key areas include: Identify and prioritize.
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.
Scrum Practices Sprint-2. Agenda Scrum Master Product Backlog Scrum Teams Daily Scrum Meeting Sprint Planning Meeting Sprint Sprint Review.
Theory and Practice of Games Dennis Meadows Uppsalla University
Ch. 6 Team Effectiveness. Here are some team building ideas, techniques, and tips you can try when managing teams in your situation.
1 Agile Release Management. 2 Recall - Highsmith’s remedies for schedule risk Team involvement in planning and estimating Early feedback on delivery velocity.
Goal-Setting for Success. OBJECTIVES 1.To understand what goal-setting is 2.To understand why goal-setting is important 3.To understand how to use the.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
Anatomy Ontology Community Melissa Haendel. The OBO Foundry More than just a website, it’s a community of ontology developers.
User Modeling Lecture # 7 Gabriel Spitz 1. User Interface Design Process Gabriel Spitz 2 Needs Assessment Competitive Analysis Persona Develop Task Analysis/
Quality Criteria : Are you and your team capable of communicating the shared vision to whom it may concern so that it make sense to all relevant stakeholders.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
DESIGNING FOR MOBILE EARLY STAGE UX DESIGN PROCESS.
Sprint Plans and Burndown Charts David Millard | davidmillard.org.
SCRUM.
End of Sprint Meetings (Ceremonies)
User Modeling Lecture # 7 Gabriel Spitz 1. User Interface Design Process Gabriel Spitz 2 Needs Assessment Competitive Analysis Persona Develop Task Analysis/
Intended for Knowledge Sharing only Optimizing Product Decisions with Insights THE PRODUCT MANAGEMENT & INNOVATION EVENT 2016 Jan 2016.
Lecture 5 17/9/15. What is Scrum? Scrum is one of the leading agile software development processes Agile framework for completing complex projects. Originally.
Over Contract negotiation over Processes and tools over Comprehensive documentation overFollowing a plan over.
Counting Change By: Hannah Leigh Reagan. Instructions: This assignment is an interactive quiz. Each slide will have a question and multiple-choice answers.
Introduction to Agile. Introduction Who is this guy?
Dr. Sean Wise, BA LLB MBA PhD
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
1 COACHING FOR IMPACT Stephanie Brodtrick MBA RN Learning Operations VUMC Human Resources Adult Enterprise Leadership Development Series: April 12, 2016.
Successfully Implementing Your Student Success Plans
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Add and subtract complex numbers
September 20, 2017 Agile Techniques Workshop Susan Futey
By: By: Agile Scrum Master Online Training.
Project & Program Governance
So You Want to Be a Product Owner
Introduction to Agile Blue Ocean Workshops.
Multiplying Multi-Digit Whole Numbers
Market problems & opport‘ies
Scrum Science NGSS: Engineering, Technology, Applications of Science
MODULE 5 Make the Plan & Test the Plan
Agile Development – a new way of software development?
Agile, Scrum and CMMI Methodologies
Product Development & Planning
Presentation transcript:

Gamify Release Planning

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

Level 1 Success – Personas Defined 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 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 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 1

Level 2 Success – Feature wish list defined 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. 1.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 Features wish list helps +Think about the whole product and set the future vision 2

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 WOW factor is +Simplified KANO model +Add if the feature will add to the Wow factor to the product or not 3 MoSCoW is +Must, Should, Could and Won’t have features

Level 4 Success – $ value attached to each feature 1.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 isn’t +Business Value 4 $ value is +IT development complexity measure +100$ is the relative measure of the development effort the team can spend in delivering the MVP.

Level 5 Success – Spend your $100 1.Real fun bit, the sponsors have it all to buy the features now. 2.Sponsors take a lead and decide how to spend their $ 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.

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