This document outlines an agenda for an executive team presentation focusing on developing features for the second half of 2013. It includes several group exercises:
1. Listing potential new features on sticky notes and organizing them into themes.
2. Individual and group dot voting to rank features by perceived customer benefit.
3. Relative sizing and ROI calculation to estimate effort and organizational prioritize the backlog of features.
The presentation aims to have an interactive and hands-on discussion of real product needs and develop an agreed upon prioritized backlog for upcoming development.
7. Discuss H2 ‘13 Epic
Development (7 mins)
Exercise: small table discussion
8. Detailed Instructions:
– List all features (a.k.a Epics) you want built on sticky
notes provided
– Each person can have 0+N feature ideas / requests
– Features can be at ideation stage
– Put sticky notes on flip chart
10. Add Themes to Epics (4
mins)
Exercise: small table discussion
11. • Detailed Instructions:
– As a group create a ‘theming’ organization to your
features
– Add 0 + N themes per Epic on the flip chart(s)
Create Named Themes
14. Detailed Instructions:
– In silence, Using Dot-Voting vote for the Epic(s) that
you alone think will benefit our customer (CISO) the
most.
– You must utilize both of your votes
17. Detailed Instructions:
– Employing your best rhetorical style, Using a Dot-
Voting strategy vote for the Epic(s) that as a group
you think will benefit our customer (CISO) the most.
– Must utilize all group votes
21. Detailed Instructions:
– Using your (a) group based dot voting, (b) your
themes, and (c) my relative effort based sizing
create a ‘back of the napkin’ ROI calculator to help
organize your backlog
– Present to each other a stack ranked list of Epics to
do in H2 ’13 that matches to our story
24. What facilitator needs to bring
• Electrical Tape
• Poker Chips or Pennies (20)
• Pens, markets, sticky notes
Notes de l'éditeur
Over 70% of organizations fail to connect security to the business How can CISOs show value to their business organization in meaningful ways?
Humans are terrible at absolute estimation but quite good at relative estimationIt is generally faster - “What’s the use in being precise when you don’t even know what you’re talking about?”It gets a team thinking (and talking) as a group, rather than as individuals (group effort vs. individual person-hours)It encourages spending analysis time appropriately (analyzing and discussing)It is cost-effective
These are the types of metrics I will utilize to help you win