Agile planning and estimating

28
Agile Planning And Estimating Responding to change over following a plan

description

Planning is incredibly important for businesses to reduce risk and create value, but what happens when the plan is almost always wrong? Software development is inherently hard to plan, but there are some great Agile tools available to help us plan effectively. This brown bag explores some of these Scrum ceremonies and tools available in the Agile world.

Transcript of Agile planning and estimating

Page 1: Agile planning and estimating

Agile Planning And EstimatingResponding to change over following a plan

Page 2: Agile planning and estimating

About Me

• Google Plus: +BrettChild• Blog: www.bmchild.com

Page 3: Agile planning and estimating

Objectives

•Planning in Software•Tools for Planning•Product Mapping•Release Planning•Estimating Effort•Q&A

Page 4: Agile planning and estimating

Planning is hard

1994 1996 1998 2000 2002 2004 2009

Failed 0.31 0.4 0.28 0.23 0.15 0.18 0.24

Succeeded 0.16 0.27 0.26 0.28 0.34 0.29 0.32

Challenged 0.53 0.33 0.46 0.49 0.51 0.53 0.44

5%

15%

25%

35%

45%

55%

Software Project Failures and Successes

Standish CHAOS Reports

Page 5: Agile planning and estimating

Why Plan?

•Reduce Risk•Reduce Uncertainty•Support Better Decision Making•Establish Trust•Convey Information

Page 6: Agile planning and estimating

Agile Planning

•Focus on planning, not on the plan•Encourage Change•Plan is Easily Changed•Spread throughout the Project

One of the most destructive things we do is build something that no one wants.

Page 7: Agile planning and estimating

Agile Tools

Product Mapping

Release Planning

Sprint Planning

Product/Project

Release/Milestone

Sprint

Page 8: Agile planning and estimating

Product/Project Mapping• Impact Mapping• User Story Mapping

Page 9: Agile planning and estimating

Impact Mapping

impactmapping.org

Page 10: Agile planning and estimating

User Story Mapping

Page 11: Agile planning and estimating

The Walking Skeleton

User Tasks

Page 12: Agile planning and estimating

The Backbone

User Activities

Page 13: Agile planning and estimating

User Stories

Page 14: Agile planning and estimating

Release/Milestone Planning

•Minimum Viable Product•Evolutionary

Page 15: Agile planning and estimating

Minimum Viable Product• Eric Ries, author of The Lean Startup:

“A Minimum Viable Product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.”

• Customer interviews• Demo page• Teaser links• Release 1.0 • Concierge MVP• Wizard of Oz MVP

Page 16: Agile planning and estimating

BetterUX.it• A Community where startup founders can get expert feedback

from UX designers.

http://www.smashingmagazine.com/2014/04/10/a-guide-to-validating-product-ideas-with-quick-and-simple-experiments-2/

Page 17: Agile planning and estimating

BetterUX.it

“Bootstrapped startup founders have trouble getting UX feedback because they have no reliable sources to turn to.”

• Release 1• Interview startup founders

Page 18: Agile planning and estimating

BetterUX.it

“Would they pay for an online service to get feedback from UX designers?”• Release 2

Page 19: Agile planning and estimating

BetterUX.it

“Would designers consult with startup founders?”

• Release 3• Interview designers

Page 20: Agile planning and estimating

BetterUX.it

“Would new designers consult with startup founders?”• Release 4

Page 21: Agile planning and estimating

Evolutionary

Page 22: Agile planning and estimating

Estimating Effort

•Story Points and Velocity•Planning Poker•Affinity Planning

Page 23: Agile planning and estimating

Story Points and Velocity

• Story Points: Relative size/complexity to other stories• Have no other purpose other than planning• .5, 1, 2, 3, 5, 8, 13, 20, 40, 100

• Velocity: how many story points can be completed in an iteration• Historical data -> running average• Generally takes about 3 iterations before the velocity stabilizes

for a new team

Page 24: Agile planning and estimating

Story Point and Velocity• Example:• We have a backlog of these tasks

• 6 tasks @ 1 point each = 6 total points• 8 tasks @ 2 points = 16 total points• 36 tasks @ 3 points = 108 points• Grand total of 130 points

• Our team velocity averages 50 points for each 2 week cycle• How long will it take us to complete the 108 points?

• 130 / 50 = 2.6 iterations * 2 weeks = 5.2 weeks

Page 25: Agile planning and estimating

Planning Poker• Agree on an anchor• Good to allow in depth conversation about a story• Takes more time

Page 26: Agile planning and estimating

Affinity Estimating• Useful for large amounts of stories• Generally done silently• Very fast

Page 27: Agile planning and estimating

Review

• Planning in Software• Tools for Planning• Product/Project Mapping• Impact Mapping & User Story Mapping

• Release/Milestone Planning•MVP and Evolutionary

• Estimating Effort• Story Points, Velocity, Planning Poker,

and Affinity Estimating