Epic Planning Poker
Within Agile Scrum, how do you provide an estimate when you could reach MVP/MMP?
In traditional project estimation, you might complete a full WBS, estimate each element, sum it all up to arrive at total effort, lay out resource and technical dependencies, and finally add in appropriate buffers to get a project completion date.
Since in Agile we iteratively build and refine the tasks and constantly adjust priorities, the traditional way doesn't work. But why do we need to? Because in most organizations, the external budgeting and planning processes have not yet adopted Organizational Agility. Annual cycles of budgeting and planning still wants overall project estimates. Epic Poker extends the Sprint Planning Poker concepts to collections of stories (Epics), and provides a analytic tool to predict how long it might take to get to MVP.
Once there, the Epic Points can then be used to calculate and monitor a modified form of EVM to show progress to stakeholders
Outline/Structure of the Lightning Talk
- You’re using Agile on your team, but leadership really really really wants to have an idea how long till MVP. How? First, deep breath.
- Create a very high level structure—groups of stories that make up an Epic. Plan a half day to talk through the Epics. When decently understood, play planning poker.
- Not the same scale as story points. Just rank them relative to each other
- Any Epic over 40 is worth considering breaking up
- Pick one Epic (small, and if it’s MVP all stories should have same priority), create all the stories and assign Story Points. Calculate an Epic Points Multiplier, EPM = SP/EP. Now you can estimate the total SP for all the Epics combined. That still doesn’t give a schedule—you need velocity
- Once you get through a couple sprints, you will need to rebaseline all the calculations
- Very rough estimations—recommend at least doubling the estimate to get projections
- Take a deep review of the Epics; missing a chunk of requirements can have serious impact
An adaptive tool for Agile-fall implementations
Product Owners, Project Manager, and ScrumMasters
Prerequisites for Attendees
Understand Sprint Planning Poker, traditional budgeting cycles
schedule Submitted 1 year ago
People who liked this proposal, also liked:
Donald Patti / Lisa Brown / Meghana Ekbote / Yogita dhond - Scrum in a Snap: Using Snap Circuits to Excite & Educate Scrum NewcomersDonald PattiCoach/ConsultantCedar Point ConsultingLisa BrownAVP, Sr. Systems AnalystSandy Spring BankMeghana Ekbote--Yogita dhondAgile CoachAccenture
schedule 1 year agoSold Out!
The best way to learn Scrum is by doing, but it can be difficult to simulate Scrum and see how well Scrum helps team overcome technical hurdles without actually building something technically challenging. Lego's have always been a fun option for introducing Scrum, but it's difficult to recreate technical impediments, the need for spikes and managing technical debt with our tried and true friend, the box of Lego's.
Arguably, a better alternative might be Snap Circuits, a toy designed to introduce children to electronics in a fun and easy-to-understand format. Like Lego's, adults gravitate toward Snap Circuits because they are colorful, quickly understood and snap together with ease.
But, Snap Circuits have the added advantage of requiring a small amount of technical learning during the simulation that make it a closer match to the technical obstacles faced by a typical Scrum team.
In this workshop, you'll learn one "Scrum in a Snap" simulation exercise. In addition, we'll provide you with a few other "Scrum in a Snap" ideas and encourage you to experiment on your own. Four lucky attendees will also win their own Snap Circuits kit so they can develop their own Scrum games.
Past participants in "Scrum in a Snap" have said "The best Scrum exercise I've ever done", "I can't believe how much it's like coding - without actually coding", "What a blast - I'll never forget this activity!" and "Where can I buy one?"
Attend this workshop to see why.