SlideShare a Scribd company logo
Jeffrey D. Mansfield
Project Management/Program Management/Portfolio Management Professional
jeffreydmansfield#@gmail.com
http://www.linkedin.com/in/jeffreydmansfield/
December 2018
Answering these questions are a challenge as changes
in scope and priority will occur during development.
The following Agile planning and tracking process can
help answer these questions.
1. Break backlog into epics/stories
2. Assign story points
Part of prioritization process
Use Fibonacci numbers (1, 2, 3, 5, 8, 13, 21) for t-shirt sizing of effort
3. Define MinimumViable Product - MVP
Product Owner defines the minimum functionality to be released
4. Add additional story point contingency to account for:
Changes in requirement (new functionality)
Resolving technical debt (rework)
5. Estimate team capacity in story points
Estimate number of story points (velocity) to be completed for each sprint
▪ Velocity will improve as team matures
▪ Velocity will change as team changes
6. Develop an initial sprint plan
Number of sprints required until MVP + Contingency < sum of velocity
Sprint 1 2 3 4 5 6 7 8 9 10
Sprint End Date 2/15/19 3/1/19 3/15/19 3/29/19 4/12/19 4/26/19 5/10/19 5/24/19 6/7/19 6/21/19
Plan
Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600
Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500
Original Total MVP & Contingency Story
Points 600 600 600 600 600 600 600 600 600 600 600
Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40
Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600
Original Remaining Story Points (Incl Backlog) 450 390 330 260 190 120 50
Original Remaining MVP & Contingency Story
Points 550 490 430 360 290 220 150 80 40
1. After every sprint, assess the following:
What was the actual velocity of the team?
The number of story points the team completed
Is the planned velocity too high or too low based on actual?
Can any changes be made to increase velocity?
Has the story points required to meet MVP changed?
Does the contingency need to be adjusted?
Has the team capacity changed?
Have people been added or removed?
2. Reforecast the sprint plan based on the assessment
1. First 3 sprints on plan, additional stories added to
backlog, but backlog is less than MVP and
Contingency planned.
Sprint 1 2 3 4 5 6 7 8 9 10
Sprint End Date 2/15/19 3/1/2019 3/15/2019 3/29/2019 4/12/2019 4/26/2019 5/10/2019 5/24/2019 6/7/2019 6/21/2019
Plan
Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600
Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500
Original Total MVP & Contingency Story
Points 600 600 600 600 600 600 600 600 600 600 600
Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40
Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600
Original Remaining Story Points (Incl
Backlog) 450 390 330 260 190 120 50
Original Remaining MVP & Contingency Story
Points 550 490 430 360 290 220 150 80 40
Actual/Forecast
Actual Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600
Actual Total Story Points (Incl Backlog) 500 550 600 600 600 600 600 600 600 600
Actual Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600
Actual Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40
Actual Total Completed Story Points 50 110 170 240 310 380 450 520 560 600
Actual Remaining Story Points (Incl Backlog) 450 440 430 360 290 220 150 80 40
Actual Remaining MVP & Contingency Story
Points 550 490 430 360 290 220 150 80 40
Adjusted total story points based on backlog.
Total story points still within team capacity.
Still on target for 10 sprints.
1. First 3 sprints on plan, additional stories added to
backlog, but backlog is less than MVP and
Contingency planned.
2. Loss of team member for 3 sprints reducing velocity
and MVP cannot be met as originally planned.
Sprint 1 2 3 4 5 6 7 8 9 10
Sprint End Date 2/15/19 3/1/2019 3/15/2019 3/29/2019 4/12/2019 4/26/2019 5/10/2019 5/24/2019 6/7/2019 6/21/2019
Plan
Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600
Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500
Original Total MVP & Contingency Story
Points 600 600 600 600 600 600 600 600 600 600 600
Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40
Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600
Original Remaining Story Points (Incl Backlog) 450 390 330 260 190 120 50
Original Remaining MVP & Contingency Story
Points 550 490 430 360 290 220 150 80 40
Actual/Forecast
Actual Team Capacity Story Points 570 570 570 570 570 570 570 570 570 570 570
Actual Total Story Points (Incl Backlog) 500 550 600 600 600 600 600 600 600 600
Actual Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600
Actual Team Velocity for Sprint 50 60 60 60 60 60 70 70 40 40
Actual Total Completed Story Points 50 110 170 230 290 350 420 490 530 570
Actual Remaining Story Points (Incl Backlog) 450 440 430 370 310 250 180 110 70 30
Actual Remaining MVP & Contingency Story
Points 550 490 430 370 310 250 180 110 70 30
Adjusted team velocity to reflect loss of team member.
Team velocity will no longer cover MVP.
1. First 3 sprints on plan, additional stories added to
backlog, but backlog is less than MVP and
Contingency planned.
2. Lose team member for 3 sprints reducing velocity
and MVP cannot be met as originally planned.
3. Added additional velocity to later sprints to keep to
current sprint plan.
Sprint 1 2 3 4 5 6 7 8 9 10
Sprint End Date 2/15/19 3/1/2019 3/15/2019 3/29/2019 4/12/2019 4/26/2019 5/10/2019 5/24/2019 6/7/2019 6/21/2019
Plan
Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600
Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500
Original Total MVP & Contingency Story
Points 600 600 600 600 600 600 600 600 600 600 600
Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40
Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600
Original Remaining Story Points (Incl Backlog) 450 390 330 260 190 120 50
Original Remaining MVP & Contingency Story
Points 550 490 430 360 290 220 150 80 40
Actual/Forecast
Actual Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600
Actual Total Story Points (Incl Backlog) 500 550 600 600 600 600 600 600 600 600
Actual Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600
Actual Team Velocity for Sprint 50 60 60 60 60 60 70 70 55 55
Actual Total Completed Story Points 50 110 170 230 290 350 420 490 545 600
Actual Remaining Story Points (Incl Backlog) 450 440 430 370 310 250 180 110 55
Actual Remaining MVP & Contingency Story
Points 550 490 430 370 310 250 180 110 55
Decision taken to reduce number of team members planned to be released for
sprint 9 and 10.
Increased forecasted velocity to reflect additional team members for these
sprints.
MVP is now being met.
1. First 3 sprints on plan, additional stories added to
backlog, but backlog is less than MVP and
Contingency planned.
2. Lose team member for 3 sprints reducing velocity
and MVP cannot be met as originally planned.
3. Added additional velocity to later sprints to keep to
current sprint plan.
4. Product Owner adds additional stories to MVP.
Sprint 1 2 3 4 5 6 7 8 9 10
Sprint End Date 2/15/19 3/1/2019 3/15/2019 3/29/2019 4/12/2019 4/26/2019 5/10/2019 5/24/2019 6/7/2019 6/21/2019
Plan
Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600
Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500
Original Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600 600
Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40
Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600
Original Remaining Story Points (Incl Backlog) 450 390 330 260 190 120 50
Original Remaining MVP & Contingency Story
Points 550 490 430 360 290 220 150 80 40
Actual/Forecast
Actual Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600
Actual Total Story Points (Incl Backlog) 500 550 600 600 600 650 735 735 735 735
Actual Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 700 700
Actual Team Velocity for Sprint 50 60 60 60 60 60 70 70 55 55
Actual Total Completed Story Points 50 110 170 230 290 350 420 490 545 600
Actual Remaining Story Points (Incl Backlog) 450 440 430 370 310 300 315 245 190 135
Actual Remaining MVP & Contingency Story
Points 550 490 430 370 310 250 180 110 155 100
Product Owner adds 100 story points to MVP.
MVP now exceeds team capacity.
MVP can no longer be delivered within current sprint plan.
1. First 3 sprints on plan, additional stories added to
backlog, but backlog is less than MVP and
Contingency planned.
2. Lose team member for 3 sprints reducing velocity
and MVP cannot be met as originally planned.
3. Added additional velocity to later sprints to keep to
current sprint plan.
4. Product Owner adds additional stories to MVP
5. Additional Sprint is added to complete MVP.
Sprint 1 2 3 4 5 6 7 8 9 10 11 12
Sprint End Date 2/15/19 3/1/2019 3/15/2019 3/29/2019 4/12/2019 4/26/2019 5/10/2019 5/24/2019 6/7/2019 6/21/2019 7/5/2019 7/19/2019
Plan
Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600 600 600
Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500 500 500
Original Total MVP & Contingency Story
Points 600 600 600 600 600 600 600 600 600 600 600 630 700
Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40
Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600 600 600
Original Remaining Story Points (Incl
Backlog) 450 390 330 260 190 120 50
Original Remaining MVP & Contingency
Story Points 550 490 430 360 290 220 150 80 40
Actual/Forecast
Actual Team Capacity Story Points 700 700 700 700 700 700 700 700 700 700 700 700 700
Actual Total Story Points (Incl Backlog) 500 550 600 600 600 650 735 735 735 735 735 735
Actual Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 700 700 700 700
Actual Team Velocity for Sprint 50 60 60 60 60 60 70 70 70 70 70
Actual Total Completed Story Points 50 110 170 230 290 350 420 490 560 630 700 700
Actual Remaining Story Points (Incl Backlog) 450 440 430 370 310 300 315 245 175 105 35 35
Actual Remaining MVP & Contingency Story
Points 550 490 430 370 310 250 180 110 140 70
Decision taken to keep team fully staffed and to add an additional sprint.
Updated forecasted velocity based on decision.
MVP is now being met.
Some additional backlog items will not be delivered (35 story points).
Jeffrey D. Mansfield
Project Management/Program
Management/Portfolio Management Professional
Driving Business Strategy Implementation
through Projects
http://www.linkedin.com/in/jeffreydmansfield/
http://www.twitter.com/jeffmansfld
Resume -
http://www.slideshare.net/jeffreydmansfield/resume
-mansfield-jeffrey-ppm-jan272014-31143481

More Related Content

Similar to Agile estimating

Start up it co financial model
Start up it co financial modelStart up it co financial model
Start up it co financial model
Prasad Garimilla(G.R.K.Prasad)
 
Scrum Drawing Game 2.0 - Draw Your Dream House (Chao-Kung Liu)
Scrum Drawing Game 2.0 - Draw Your Dream House  (Chao-Kung Liu)Scrum Drawing Game 2.0 - Draw Your Dream House  (Chao-Kung Liu)
Scrum Drawing Game 2.0 - Draw Your Dream House (Chao-Kung Liu)
AgileTour@TW
 
Scrum Drawing Game 2.0 for Agile Tour 2017
Scrum Drawing Game 2.0 for Agile Tour 2017Scrum Drawing Game 2.0 for Agile Tour 2017
Scrum Drawing Game 2.0 for Agile Tour 2017
Juggernaut Liu
 
Salary and pricing analysis in Vietnam Lab. Type development
Salary and pricing analysis in Vietnam Lab. Type developmentSalary and pricing analysis in Vietnam Lab. Type development
Salary and pricing analysis in Vietnam Lab. Type development
Hiroshi KURABAYASHI
 
Money Projection PowerPoint Presentation Slides
Money Projection PowerPoint Presentation Slides Money Projection PowerPoint Presentation Slides
Money Projection PowerPoint Presentation Slides
SlideTeam
 
Ben Hogan - Extending scrum adoption with visual managment
Ben Hogan - Extending scrum adoption with visual managmentBen Hogan - Extending scrum adoption with visual managment
Ben Hogan - Extending scrum adoption with visual managment
Scrum Australia Pty Ltd
 
Scrum Drawing Game for Scrum Gathering Tokyo
Scrum Drawing Game for Scrum Gathering TokyoScrum Drawing Game for Scrum Gathering Tokyo
Scrum Drawing Game for Scrum Gathering Tokyo
Juggernaut Liu
 

Similar to Agile estimating (7)

Start up it co financial model
Start up it co financial modelStart up it co financial model
Start up it co financial model
 
Scrum Drawing Game 2.0 - Draw Your Dream House (Chao-Kung Liu)
Scrum Drawing Game 2.0 - Draw Your Dream House  (Chao-Kung Liu)Scrum Drawing Game 2.0 - Draw Your Dream House  (Chao-Kung Liu)
Scrum Drawing Game 2.0 - Draw Your Dream House (Chao-Kung Liu)
 
Scrum Drawing Game 2.0 for Agile Tour 2017
Scrum Drawing Game 2.0 for Agile Tour 2017Scrum Drawing Game 2.0 for Agile Tour 2017
Scrum Drawing Game 2.0 for Agile Tour 2017
 
Salary and pricing analysis in Vietnam Lab. Type development
Salary and pricing analysis in Vietnam Lab. Type developmentSalary and pricing analysis in Vietnam Lab. Type development
Salary and pricing analysis in Vietnam Lab. Type development
 
Money Projection PowerPoint Presentation Slides
Money Projection PowerPoint Presentation Slides Money Projection PowerPoint Presentation Slides
Money Projection PowerPoint Presentation Slides
 
Ben Hogan - Extending scrum adoption with visual managment
Ben Hogan - Extending scrum adoption with visual managmentBen Hogan - Extending scrum adoption with visual managment
Ben Hogan - Extending scrum adoption with visual managment
 
Scrum Drawing Game for Scrum Gathering Tokyo
Scrum Drawing Game for Scrum Gathering TokyoScrum Drawing Game for Scrum Gathering Tokyo
Scrum Drawing Game for Scrum Gathering Tokyo
 

Recently uploaded

Removing Uninteresting Bytes in Software Fuzzing
Removing Uninteresting Bytes in Software FuzzingRemoving Uninteresting Bytes in Software Fuzzing
Removing Uninteresting Bytes in Software Fuzzing
Aftab Hussain
 
DevOps and Testing slides at DASA Connect
DevOps and Testing slides at DASA ConnectDevOps and Testing slides at DASA Connect
DevOps and Testing slides at DASA Connect
Kari Kakkonen
 
20240607 QFM018 Elixir Reading List May 2024
20240607 QFM018 Elixir Reading List May 202420240607 QFM018 Elixir Reading List May 2024
20240607 QFM018 Elixir Reading List May 2024
Matthew Sinclair
 
Mind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AIMind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AI
Kumud Singh
 
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
James Anderson
 
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FMEEssentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Safe Software
 
Large Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial ApplicationsLarge Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications
Rohit Gautam
 
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the  Possible with Graph - Q2 2024GraphSummit Singapore | The Art of the  Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Neo4j
 
By Design, not by Accident - Agile Venture Bolzano 2024
By Design, not by Accident - Agile Venture Bolzano 2024By Design, not by Accident - Agile Venture Bolzano 2024
By Design, not by Accident - Agile Venture Bolzano 2024
Pierluigi Pugliese
 
Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !
KatiaHIMEUR1
 
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
DianaGray10
 
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdfFIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
FIDO Alliance
 
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing DaysClimate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
Kari Kakkonen
 
20 Comprehensive Checklist of Designing and Developing a Website
20 Comprehensive Checklist of Designing and Developing a Website20 Comprehensive Checklist of Designing and Developing a Website
20 Comprehensive Checklist of Designing and Developing a Website
Pixlogix Infotech
 
A tale of scale & speed: How the US Navy is enabling software delivery from l...
A tale of scale & speed: How the US Navy is enabling software delivery from l...A tale of scale & speed: How the US Navy is enabling software delivery from l...
A tale of scale & speed: How the US Navy is enabling software delivery from l...
sonjaschweigert1
 
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 daysPushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
Adtran
 
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Neo4j
 
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
James Anderson
 
Generative AI Deep Dive: Advancing from Proof of Concept to Production
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionGenerative AI Deep Dive: Advancing from Proof of Concept to Production
Generative AI Deep Dive: Advancing from Proof of Concept to Production
Aggregage
 
Introduction to CHERI technology - Cybersecurity
Introduction to CHERI technology - CybersecurityIntroduction to CHERI technology - Cybersecurity
Introduction to CHERI technology - Cybersecurity
mikeeftimakis1
 

Recently uploaded (20)

Removing Uninteresting Bytes in Software Fuzzing
Removing Uninteresting Bytes in Software FuzzingRemoving Uninteresting Bytes in Software Fuzzing
Removing Uninteresting Bytes in Software Fuzzing
 
DevOps and Testing slides at DASA Connect
DevOps and Testing slides at DASA ConnectDevOps and Testing slides at DASA Connect
DevOps and Testing slides at DASA Connect
 
20240607 QFM018 Elixir Reading List May 2024
20240607 QFM018 Elixir Reading List May 202420240607 QFM018 Elixir Reading List May 2024
20240607 QFM018 Elixir Reading List May 2024
 
Mind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AIMind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AI
 
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
 
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FMEEssentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
 
Large Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial ApplicationsLarge Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications
 
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the  Possible with Graph - Q2 2024GraphSummit Singapore | The Art of the  Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
 
By Design, not by Accident - Agile Venture Bolzano 2024
By Design, not by Accident - Agile Venture Bolzano 2024By Design, not by Accident - Agile Venture Bolzano 2024
By Design, not by Accident - Agile Venture Bolzano 2024
 
Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !
 
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
 
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdfFIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
 
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing DaysClimate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
 
20 Comprehensive Checklist of Designing and Developing a Website
20 Comprehensive Checklist of Designing and Developing a Website20 Comprehensive Checklist of Designing and Developing a Website
20 Comprehensive Checklist of Designing and Developing a Website
 
A tale of scale & speed: How the US Navy is enabling software delivery from l...
A tale of scale & speed: How the US Navy is enabling software delivery from l...A tale of scale & speed: How the US Navy is enabling software delivery from l...
A tale of scale & speed: How the US Navy is enabling software delivery from l...
 
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 daysPushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
 
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
 
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
 
Generative AI Deep Dive: Advancing from Proof of Concept to Production
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionGenerative AI Deep Dive: Advancing from Proof of Concept to Production
Generative AI Deep Dive: Advancing from Proof of Concept to Production
 
Introduction to CHERI technology - Cybersecurity
Introduction to CHERI technology - CybersecurityIntroduction to CHERI technology - Cybersecurity
Introduction to CHERI technology - Cybersecurity
 

Agile estimating

  • 1. Jeffrey D. Mansfield Project Management/Program Management/Portfolio Management Professional jeffreydmansfield#@gmail.com http://www.linkedin.com/in/jeffreydmansfield/ December 2018
  • 2. Answering these questions are a challenge as changes in scope and priority will occur during development. The following Agile planning and tracking process can help answer these questions.
  • 3. 1. Break backlog into epics/stories 2. Assign story points Part of prioritization process Use Fibonacci numbers (1, 2, 3, 5, 8, 13, 21) for t-shirt sizing of effort 3. Define MinimumViable Product - MVP Product Owner defines the minimum functionality to be released 4. Add additional story point contingency to account for: Changes in requirement (new functionality) Resolving technical debt (rework) 5. Estimate team capacity in story points Estimate number of story points (velocity) to be completed for each sprint ▪ Velocity will improve as team matures ▪ Velocity will change as team changes 6. Develop an initial sprint plan Number of sprints required until MVP + Contingency < sum of velocity
  • 4. Sprint 1 2 3 4 5 6 7 8 9 10 Sprint End Date 2/15/19 3/1/19 3/15/19 3/29/19 4/12/19 4/26/19 5/10/19 5/24/19 6/7/19 6/21/19 Plan Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600 Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500 Original Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600 600 Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40 Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600 Original Remaining Story Points (Incl Backlog) 450 390 330 260 190 120 50 Original Remaining MVP & Contingency Story Points 550 490 430 360 290 220 150 80 40
  • 5. 1. After every sprint, assess the following: What was the actual velocity of the team? The number of story points the team completed Is the planned velocity too high or too low based on actual? Can any changes be made to increase velocity? Has the story points required to meet MVP changed? Does the contingency need to be adjusted? Has the team capacity changed? Have people been added or removed? 2. Reforecast the sprint plan based on the assessment
  • 6. 1. First 3 sprints on plan, additional stories added to backlog, but backlog is less than MVP and Contingency planned.
  • 7. Sprint 1 2 3 4 5 6 7 8 9 10 Sprint End Date 2/15/19 3/1/2019 3/15/2019 3/29/2019 4/12/2019 4/26/2019 5/10/2019 5/24/2019 6/7/2019 6/21/2019 Plan Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600 Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500 Original Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600 600 Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40 Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600 Original Remaining Story Points (Incl Backlog) 450 390 330 260 190 120 50 Original Remaining MVP & Contingency Story Points 550 490 430 360 290 220 150 80 40 Actual/Forecast Actual Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600 Actual Total Story Points (Incl Backlog) 500 550 600 600 600 600 600 600 600 600 Actual Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600 Actual Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40 Actual Total Completed Story Points 50 110 170 240 310 380 450 520 560 600 Actual Remaining Story Points (Incl Backlog) 450 440 430 360 290 220 150 80 40 Actual Remaining MVP & Contingency Story Points 550 490 430 360 290 220 150 80 40 Adjusted total story points based on backlog. Total story points still within team capacity. Still on target for 10 sprints.
  • 8. 1. First 3 sprints on plan, additional stories added to backlog, but backlog is less than MVP and Contingency planned. 2. Loss of team member for 3 sprints reducing velocity and MVP cannot be met as originally planned.
  • 9. Sprint 1 2 3 4 5 6 7 8 9 10 Sprint End Date 2/15/19 3/1/2019 3/15/2019 3/29/2019 4/12/2019 4/26/2019 5/10/2019 5/24/2019 6/7/2019 6/21/2019 Plan Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600 Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500 Original Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600 600 Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40 Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600 Original Remaining Story Points (Incl Backlog) 450 390 330 260 190 120 50 Original Remaining MVP & Contingency Story Points 550 490 430 360 290 220 150 80 40 Actual/Forecast Actual Team Capacity Story Points 570 570 570 570 570 570 570 570 570 570 570 Actual Total Story Points (Incl Backlog) 500 550 600 600 600 600 600 600 600 600 Actual Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600 Actual Team Velocity for Sprint 50 60 60 60 60 60 70 70 40 40 Actual Total Completed Story Points 50 110 170 230 290 350 420 490 530 570 Actual Remaining Story Points (Incl Backlog) 450 440 430 370 310 250 180 110 70 30 Actual Remaining MVP & Contingency Story Points 550 490 430 370 310 250 180 110 70 30 Adjusted team velocity to reflect loss of team member. Team velocity will no longer cover MVP.
  • 10. 1. First 3 sprints on plan, additional stories added to backlog, but backlog is less than MVP and Contingency planned. 2. Lose team member for 3 sprints reducing velocity and MVP cannot be met as originally planned. 3. Added additional velocity to later sprints to keep to current sprint plan.
  • 11. Sprint 1 2 3 4 5 6 7 8 9 10 Sprint End Date 2/15/19 3/1/2019 3/15/2019 3/29/2019 4/12/2019 4/26/2019 5/10/2019 5/24/2019 6/7/2019 6/21/2019 Plan Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600 Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500 Original Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600 600 Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40 Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600 Original Remaining Story Points (Incl Backlog) 450 390 330 260 190 120 50 Original Remaining MVP & Contingency Story Points 550 490 430 360 290 220 150 80 40 Actual/Forecast Actual Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600 Actual Total Story Points (Incl Backlog) 500 550 600 600 600 600 600 600 600 600 Actual Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600 Actual Team Velocity for Sprint 50 60 60 60 60 60 70 70 55 55 Actual Total Completed Story Points 50 110 170 230 290 350 420 490 545 600 Actual Remaining Story Points (Incl Backlog) 450 440 430 370 310 250 180 110 55 Actual Remaining MVP & Contingency Story Points 550 490 430 370 310 250 180 110 55 Decision taken to reduce number of team members planned to be released for sprint 9 and 10. Increased forecasted velocity to reflect additional team members for these sprints. MVP is now being met.
  • 12. 1. First 3 sprints on plan, additional stories added to backlog, but backlog is less than MVP and Contingency planned. 2. Lose team member for 3 sprints reducing velocity and MVP cannot be met as originally planned. 3. Added additional velocity to later sprints to keep to current sprint plan. 4. Product Owner adds additional stories to MVP.
  • 13. Sprint 1 2 3 4 5 6 7 8 9 10 Sprint End Date 2/15/19 3/1/2019 3/15/2019 3/29/2019 4/12/2019 4/26/2019 5/10/2019 5/24/2019 6/7/2019 6/21/2019 Plan Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600 Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500 Original Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600 600 Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40 Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600 Original Remaining Story Points (Incl Backlog) 450 390 330 260 190 120 50 Original Remaining MVP & Contingency Story Points 550 490 430 360 290 220 150 80 40 Actual/Forecast Actual Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600 Actual Total Story Points (Incl Backlog) 500 550 600 600 600 650 735 735 735 735 Actual Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 700 700 Actual Team Velocity for Sprint 50 60 60 60 60 60 70 70 55 55 Actual Total Completed Story Points 50 110 170 230 290 350 420 490 545 600 Actual Remaining Story Points (Incl Backlog) 450 440 430 370 310 300 315 245 190 135 Actual Remaining MVP & Contingency Story Points 550 490 430 370 310 250 180 110 155 100 Product Owner adds 100 story points to MVP. MVP now exceeds team capacity. MVP can no longer be delivered within current sprint plan.
  • 14. 1. First 3 sprints on plan, additional stories added to backlog, but backlog is less than MVP and Contingency planned. 2. Lose team member for 3 sprints reducing velocity and MVP cannot be met as originally planned. 3. Added additional velocity to later sprints to keep to current sprint plan. 4. Product Owner adds additional stories to MVP 5. Additional Sprint is added to complete MVP.
  • 15. Sprint 1 2 3 4 5 6 7 8 9 10 11 12 Sprint End Date 2/15/19 3/1/2019 3/15/2019 3/29/2019 4/12/2019 4/26/2019 5/10/2019 5/24/2019 6/7/2019 6/21/2019 7/5/2019 7/19/2019 Plan Original Team Capacity Story Points 600 600 600 600 600 600 600 600 600 600 600 600 600 Original Total Story Points (incl Backlog) 500 500 500 500 500 500 500 500 500 500 500 500 500 Original Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 600 600 600 630 700 Original Planned Team Velocity for Sprint 50 60 60 70 70 70 70 70 40 40 Original Total Completed Story Points 50 110 170 240 310 380 450 520 560 600 600 600 Original Remaining Story Points (Incl Backlog) 450 390 330 260 190 120 50 Original Remaining MVP & Contingency Story Points 550 490 430 360 290 220 150 80 40 Actual/Forecast Actual Team Capacity Story Points 700 700 700 700 700 700 700 700 700 700 700 700 700 Actual Total Story Points (Incl Backlog) 500 550 600 600 600 650 735 735 735 735 735 735 Actual Total MVP & Contingency Story Points 600 600 600 600 600 600 600 600 700 700 700 700 Actual Team Velocity for Sprint 50 60 60 60 60 60 70 70 70 70 70 Actual Total Completed Story Points 50 110 170 230 290 350 420 490 560 630 700 700 Actual Remaining Story Points (Incl Backlog) 450 440 430 370 310 300 315 245 175 105 35 35 Actual Remaining MVP & Contingency Story Points 550 490 430 370 310 250 180 110 140 70 Decision taken to keep team fully staffed and to add an additional sprint. Updated forecasted velocity based on decision. MVP is now being met. Some additional backlog items will not be delivered (35 story points).
  • 16.
  • 17.
  • 18. Jeffrey D. Mansfield Project Management/Program Management/Portfolio Management Professional Driving Business Strategy Implementation through Projects http://www.linkedin.com/in/jeffreydmansfield/ http://www.twitter.com/jeffmansfld Resume - http://www.slideshare.net/jeffreydmansfield/resume -mansfield-jeffrey-ppm-jan272014-31143481