SlideShare a Scribd company logo
A short white paper of self-learning about how
to interpret the classic Agile burn-down chart as
a tool of earned value management
An Exercise in
Earned Value
Management
in AGILE
Presented by Square Peg
Consulting, LLC
John Goodpasture, PMP
Copyright 2014, All rights reserved
Square Peg Consulting, LLC
An exercise in earned value management in Agile methods
1 Set-up and background
A project applying agile methods has developed a backlog of three objects.
 Backlog is a prioritized list of objects to be delivered in a scheduled time frame
 An object can be anything that is countable and measureable, with a beginning
effort and a clear definition of complete.
A common tool in Agile methods for assessing earned value is the burn-down chart.
 A burn-down chart is a plot of COUNT of backlog objects vs SCHEDULE
(planned wall time)
 There can be surrogates for COUNT of objects: count of stories; count of story
points; count of cases; and, number of remaining hours to deplete the backlog, or
number of remaining hours to complete the backlog
 There is no information on the burn-down about sequence, since that would
require planning the work for a specific object.
 There is no information on the burn-down about actual hours or resources
consumed
 In this project the backlog count is 3; but the count could go up or down during
the course of the project due to abandoned objects or new objects or technical
debt that modifies the backlog. Technical debt is treated as objects.
 An object has a burn-down status of COMPLETE or NOT COMPLETE.
It’s common to link the burn-down chart with a Work in Process (WIP) chart (a.k.a
Kanban chart) to track object status in finer detail than the NOT COMPLETE status. WIP
status could include, but not limited to: Not Started, Design, Develop, Test, Verify,
Validate, and Hold for inventory, etc.
2 Planning the project
Assume the following backlog plan for the backlog with COUNT = 3:
Backlog plan
Object identification Planned resource Wall time
Object A 40 hours 2 days
Object B 45 hours 3 days
Object C 35 hours 2 days
Copyright 2014, All rights reserved
Square Peg Consulting, LLC
Total Backlog 120 hours 13 days
Planned resource is the estimated effort; wall time includes consideration for the
availability or conflicts or constraints regarding resources. Thus, a resource rate, like
hours/day, is not always the case.
Wall time may or may not be the calendar schedule, since there could be overlap of wall
time if there are enough resources to go around.
The planner should have access to a team benchmark for productivity. Productivity is not
usually measured over a day; rather it is measured over a duration of a sprint or iteration,
typically 2-4 weeks. A productivity measure for this project might be:
6 objects per sprint (4 weeks)
3 Setting up the baseline burn-down charts
At the outset, the PLANNED VALUE of the baseline is:
 REMAINING COUNT = 3;
 REMAINING HOURS = 120;
And, the PLANNED SCHEDULE is 12 days (1 day of overlap assumed)
Since there is no information about sequence on the burn-down chart, the planner does
not know if Object A will be started or completed before the other two objects, and the
same for the others. Thus, simple linearity is assumed for the initial planning plots.
Typically, X-Y scatter plots are applied because each axis is independent and can have its
own data set. Also, the major and minor axis are independently set to integers because
there is no partial credit.
And, it’s typical to keep the object count and the remaining hours on different charts.
Burn-down plots
The following are the baseline burn-down plots.
Copyright 2014, All rights reserved
Square Peg Consulting, LLC
Baseline burn-down chart:
Of course, you can use row-column data in a spreadsheet chart without the plots.
Copyright 2014, All rights reserved
Square Peg Consulting, LLC
4 Running the project (exercises)
For all exercise answers, apply this template:
Remaining count:
Remaining hours:
Earned value:
 objects earned
 planned hours earned
 hours actually used
 Efficiency: planned hours/actual hours
Exercise 1
Let’s assume the team starts with Object B.
 At the end of Day 2, the team reports Object B is complete
 Team reports 40 hours actually consumed
At the end of Day 2, what is the burn-down status; what is the earned value?
Copyright 2014, All rights reserved
Square Peg Consulting, LLC
Exercise 2
Now, at the beginning of Day 3, the team is informed that Object A is already developed
and in a library. Five hours are required on Day 3 to move Object A from the library into
the project configuration system, at which point Object A is complete.
What is the burn-down status at the end of Day 3?
Exercise 3
The team goes on to Object C on Day 4, completing it at the end of Day 7, four days total
for Object C. 50 hours are consumed. However, at the end of Day 6, an additional
requirement is discovered. Object D, valued at 40 hours.
For Object D, 3 days are required, beginning on Day 7 and ending on Day 9.
What is the burn-down status on Day 7?
Exercise 4
On Day 9, Object D is completed. 45 hours were consumed. No additional objects have
been added since the discovery of Object D. What is the burn-down status at the end of
Day 9?
Exercise 5
What is the final tabulation for the project, as measured from the baseline?
Copyright 2014, All rights reserved
Square Peg Consulting, LLC
5 Appendix of Answers
Exercise 1 Answer
Answer:
Remaining count: 2
Remaining hours (for Object A and C, from the resource plan): 75 hours
Earned value:
 1 object earned
 45 planned hours earned for Object B
 40 hours actually used
 Efficiency: 45/40 = 112.5%
The spread of “remaining hours” is an estimate made at the end of each object delivery;
this estimate would be made like other “estimates to complete”. The charts herein are
examples of estimates of hour remaining. Your estimates might be different.
Exercise 2 Answer
Answer
Remaining count: 1
Remaining hours (for Object C): 35 hours
Earned value:
 1 object earned
 40 planned hours earned for Object A
 5 hours actually used
 Efficiency: 50/5 = 1000%
Exercise 3 Answer
Answer
Remaining count: 1 (for Object D)
Remaining hours: 40 hours
Earned value:
 1 object earned (Object C)
 35 planned hours earned for Object C
 50 hours actually used
 Efficiency: 35/50 = 70%
Exercise 4 Answer
Answer
Remaining count: 0
Remaining hours: 0 hours
Earned value:
Copyright 2014, All rights reserved
Square Peg Consulting, LLC
 1 object earned (Object D)
 40 planned hours earned for Object D
 45 hours actually used
 Efficiency: 40/45 = 89%
Exercise 5 Answer
 Objects planned: 3
 Objects earned: 4
 Objects Remaining: 0
 Planned value (hours): 120
 Earned value (hours): 160
 Hours remaining: 0
 Hours consumed: 140
 Efficiency: 160/140 = 114%
Final tabulation burn-down charts
Copyright 2014, All rights reserved
Square Peg Consulting, LLC

More Related Content

Viewers also liked (20)

PPTX
Burn down chart | Coepd
COEPD HR
 
PDF
Agile in action | Our process for optimising conversions
Randall Snare
 
PDF
Measure what matters for your agile project
Munish Malik
 
PPT
Agile in Action - Agile Overview for Developers
Matt Cowell
 
PPTX
Agile in Action - Keynote: Becoming and Being Agile - What Does This Mean?
Spiffy
 
PPTX
Better pm-with-jira-20141121-v4
Biser Simeonov
 
PPTX
Breaking bad BA habits - BA Development Day 2015
David Morris, MBA
 
PDF
My path as an entrepreneur - or how I turned into the person I am
iO
 
PPTX
Successful Agile Adoption as a Foundation to Transformation Enable2016
David Morris, MBA
 
PPTX
Enterprise analysis
COEPD HR
 
PPTX
Building Your Agile Coaching Practice
Salesforce Engineering
 
PDF
“Mental Models for Agile Adoption” from ALE2011
Barry O'Reilly
 
PPTX
An Agile Practice Framework for Scaling Agile Adoption in an Enterprise
Brad Appleton
 
PDF
Project Management: Burn-Down Chart / OrangeHRM Project MOD (eng)
Anatoliy Okhotnikov
 
PPTX
Agile Methods Adoption on Software Development @ Agile 2014
Caio Cestari
 
PPTX
Agile in Action - Act 2: Development
Spiffy
 
PPT
Top Metrics for Agile @Agile NCR2011
Priyank Pathak
 
PPTX
Agile 101 Basic Measurement
Dhaval Panchal
 
PDF
Agile and the nature of decision making
Dennis Stevens
 
PDF
Agile.2013.effecting.a.dev ops.transformation.at.salesforce
Dave Mangot
 
Burn down chart | Coepd
COEPD HR
 
Agile in action | Our process for optimising conversions
Randall Snare
 
Measure what matters for your agile project
Munish Malik
 
Agile in Action - Agile Overview for Developers
Matt Cowell
 
Agile in Action - Keynote: Becoming and Being Agile - What Does This Mean?
Spiffy
 
Better pm-with-jira-20141121-v4
Biser Simeonov
 
Breaking bad BA habits - BA Development Day 2015
David Morris, MBA
 
My path as an entrepreneur - or how I turned into the person I am
iO
 
Successful Agile Adoption as a Foundation to Transformation Enable2016
David Morris, MBA
 
Enterprise analysis
COEPD HR
 
Building Your Agile Coaching Practice
Salesforce Engineering
 
“Mental Models for Agile Adoption” from ALE2011
Barry O'Reilly
 
An Agile Practice Framework for Scaling Agile Adoption in an Enterprise
Brad Appleton
 
Project Management: Burn-Down Chart / OrangeHRM Project MOD (eng)
Anatoliy Okhotnikov
 
Agile Methods Adoption on Software Development @ Agile 2014
Caio Cestari
 
Agile in Action - Act 2: Development
Spiffy
 
Top Metrics for Agile @Agile NCR2011
Priyank Pathak
 
Agile 101 Basic Measurement
Dhaval Panchal
 
Agile and the nature of decision making
Dennis Stevens
 
Agile.2013.effecting.a.dev ops.transformation.at.salesforce
Dave Mangot
 

Similar to Agile earned value exercise (20)

PPTX
09 Fine-tuning Assignment Details
Soe Naing Win
 
DOCX
PMGT 510Principles of Project ManagementGroup Assign.docx
stilliegeorgiana
 
PPTX
MARKS IN YOUR POCKET PMP for PMP Preparation
ssusera09841
 
DOCX
6Allocating Resources to the ProjectSolution to Project C.docx
troutmanboris
 
DOC
3. Creation Quiz for studying PMI SP exam
Wilber Tuttleman
 
DOCX
Critical Path MethodIntroductionOnce you have the network diag.docx
annettsparrow
 
PPT
project_management and its adoption_10.ppt
MuhammadIrfan561681
 
PPTX
DOC-20230811-WA0054..pptx busnises plangood
ssuser4f8f65
 
PPTX
12 Tracking Progress on Tasks and Assignments
Soe Naing Win
 
DOCX
Week 3 Homework AIB ProblemsBefore starting this homewo.docx
melbruce90096
 
PDF
Estimating-Durations-Activities-EDGE.pdf
ssuser8674da
 
PPT
Resource-Allocation.ppt
TecnicoItca
 
PDF
06 pmp time management exam
Jamil Faraj , PMP
 
DOCX
PrintNetwork Diagrams and Resource UtilizationIntroduction B.docx
ChantellPantoja184
 
PPTX
PROJECT-ANALYSIS-TOOL-PPT.pptx
PHOEBEANNEARTECHE1
 
PDF
Estimate activity duration
Niaz Ali
 
DOCX
Project NameCommunication PlanOverviewEffective and .docx
wkyra78
 
PPT
Case Dragonfly
mukul joshi
 
PDF
Derak project plan overview
Eric Gero
 
09 Fine-tuning Assignment Details
Soe Naing Win
 
PMGT 510Principles of Project ManagementGroup Assign.docx
stilliegeorgiana
 
MARKS IN YOUR POCKET PMP for PMP Preparation
ssusera09841
 
6Allocating Resources to the ProjectSolution to Project C.docx
troutmanboris
 
3. Creation Quiz for studying PMI SP exam
Wilber Tuttleman
 
Critical Path MethodIntroductionOnce you have the network diag.docx
annettsparrow
 
project_management and its adoption_10.ppt
MuhammadIrfan561681
 
DOC-20230811-WA0054..pptx busnises plangood
ssuser4f8f65
 
12 Tracking Progress on Tasks and Assignments
Soe Naing Win
 
Week 3 Homework AIB ProblemsBefore starting this homewo.docx
melbruce90096
 
Estimating-Durations-Activities-EDGE.pdf
ssuser8674da
 
Resource-Allocation.ppt
TecnicoItca
 
06 pmp time management exam
Jamil Faraj , PMP
 
PrintNetwork Diagrams and Resource UtilizationIntroduction B.docx
ChantellPantoja184
 
PROJECT-ANALYSIS-TOOL-PPT.pptx
PHOEBEANNEARTECHE1
 
Estimate activity duration
Niaz Ali
 
Project NameCommunication PlanOverviewEffective and .docx
wkyra78
 
Case Dragonfly
mukul joshi
 
Derak project plan overview
Eric Gero
 
Ad

More from John Goodpasture (20)

PDF
Five tools for managing projects
John Goodpasture
 
PPTX
Risk management short course
John Goodpasture
 
PDF
Agile in the waterfall
John Goodpasture
 
PDF
RFP template
John Goodpasture
 
PDF
Agile 103 - the three big questions
John Goodpasture
 
PDF
Agile for project managers - a sailing analogy-UPDATE
John Goodpasture
 
PDF
Feature driven design FDD
John Goodpasture
 
PDF
Dynamic Systems Development, DSDM
John Goodpasture
 
PDF
Agile for project managers - A presentation for PMI
John Goodpasture
 
PDF
Five risk management rules for the project manager
John Goodpasture
 
PDF
Building Your Personal Brand
John Goodpasture
 
PDF
Portfolio management and agile: a look at risk and value
John Goodpasture
 
PDF
Project examples for sampling and the law of large numbers
John Goodpasture
 
PDF
Agile for project managers - a sailing analogy
John Goodpasture
 
PDF
Risk management with virtual teams
John Goodpasture
 
PDF
Bayes Theorem and Inference Reasoning for Project Managers
John Goodpasture
 
PDF
Adding quantitative risk analysis your Swiss Army Knife
John Goodpasture
 
PDF
Business value and kano chart
John Goodpasture
 
PDF
Agile for Business Analysts
John Goodpasture
 
PDF
Time centric Earned Value
John Goodpasture
 
Five tools for managing projects
John Goodpasture
 
Risk management short course
John Goodpasture
 
Agile in the waterfall
John Goodpasture
 
RFP template
John Goodpasture
 
Agile 103 - the three big questions
John Goodpasture
 
Agile for project managers - a sailing analogy-UPDATE
John Goodpasture
 
Feature driven design FDD
John Goodpasture
 
Dynamic Systems Development, DSDM
John Goodpasture
 
Agile for project managers - A presentation for PMI
John Goodpasture
 
Five risk management rules for the project manager
John Goodpasture
 
Building Your Personal Brand
John Goodpasture
 
Portfolio management and agile: a look at risk and value
John Goodpasture
 
Project examples for sampling and the law of large numbers
John Goodpasture
 
Agile for project managers - a sailing analogy
John Goodpasture
 
Risk management with virtual teams
John Goodpasture
 
Bayes Theorem and Inference Reasoning for Project Managers
John Goodpasture
 
Adding quantitative risk analysis your Swiss Army Knife
John Goodpasture
 
Business value and kano chart
John Goodpasture
 
Agile for Business Analysts
John Goodpasture
 
Time centric Earned Value
John Goodpasture
 
Ad

Recently uploaded (20)

PPTX
Explanation about Structures in C language.pptx
Veeral Rathod
 
PPTX
Presentation about Database and Database Administrator
abhishekchauhan86963
 
PDF
On Software Engineers' Productivity - Beyond Misleading Metrics
Romén Rodríguez-Gil
 
PPTX
GALILEO CRS SYSTEM | GALILEO TRAVEL SOFTWARE
philipnathen82
 
PDF
Salesforce Pricing Update 2025: Impact, Strategy & Smart Cost Optimization wi...
GetOnCRM Solutions
 
PDF
Applitools Platform Pulse: What's New and What's Coming - July 2025
Applitools
 
PDF
Enhancing Healthcare RPM Platforms with Contextual AI Integration
Cadabra Studio
 
PPTX
Farrell__10e_ch04_PowerPoint.pptx Programming Logic and Design slides
bashnahara11
 
PDF
10 posting ideas for community engagement with AI prompts
Pankaj Taneja
 
PDF
Supabase Meetup: Build in a weekend, scale to millions
Carlo Gilmar Padilla Santana
 
PDF
Adobe Illustrator Crack Full Download (Latest Version 2025) Pre-Activated
imang66g
 
PDF
How Agentic AI Networks are Revolutionizing Collaborative AI Ecosystems in 2025
ronakdubey419
 
PPTX
TRAVEL APIs | WHITE LABEL TRAVEL API | TOP TRAVEL APIs
philipnathen82
 
PDF
Enhancing Security in VAST: Towards Static Vulnerability Scanning
ESUG
 
PDF
WatchTraderHub - Watch Dealer software with inventory management and multi-ch...
WatchDealer Pavel
 
PPTX
Role Of Python In Programing Language.pptx
jaykoshti048
 
PPT
Activate_Methodology_Summary presentatio
annapureddyn
 
PPT
Why Reliable Server Maintenance Service in New York is Crucial for Your Business
Sam Vohra
 
PPTX
ASSIGNMENT_1[1][1][1][1][1] (1) variables.pptx
kr2589474
 
PDF
System Center 2025 vs. 2022; What’s new, what’s next_PDF.pdf
Q-Advise
 
Explanation about Structures in C language.pptx
Veeral Rathod
 
Presentation about Database and Database Administrator
abhishekchauhan86963
 
On Software Engineers' Productivity - Beyond Misleading Metrics
Romén Rodríguez-Gil
 
GALILEO CRS SYSTEM | GALILEO TRAVEL SOFTWARE
philipnathen82
 
Salesforce Pricing Update 2025: Impact, Strategy & Smart Cost Optimization wi...
GetOnCRM Solutions
 
Applitools Platform Pulse: What's New and What's Coming - July 2025
Applitools
 
Enhancing Healthcare RPM Platforms with Contextual AI Integration
Cadabra Studio
 
Farrell__10e_ch04_PowerPoint.pptx Programming Logic and Design slides
bashnahara11
 
10 posting ideas for community engagement with AI prompts
Pankaj Taneja
 
Supabase Meetup: Build in a weekend, scale to millions
Carlo Gilmar Padilla Santana
 
Adobe Illustrator Crack Full Download (Latest Version 2025) Pre-Activated
imang66g
 
How Agentic AI Networks are Revolutionizing Collaborative AI Ecosystems in 2025
ronakdubey419
 
TRAVEL APIs | WHITE LABEL TRAVEL API | TOP TRAVEL APIs
philipnathen82
 
Enhancing Security in VAST: Towards Static Vulnerability Scanning
ESUG
 
WatchTraderHub - Watch Dealer software with inventory management and multi-ch...
WatchDealer Pavel
 
Role Of Python In Programing Language.pptx
jaykoshti048
 
Activate_Methodology_Summary presentatio
annapureddyn
 
Why Reliable Server Maintenance Service in New York is Crucial for Your Business
Sam Vohra
 
ASSIGNMENT_1[1][1][1][1][1] (1) variables.pptx
kr2589474
 
System Center 2025 vs. 2022; What’s new, what’s next_PDF.pdf
Q-Advise
 

Agile earned value exercise

  • 1. A short white paper of self-learning about how to interpret the classic Agile burn-down chart as a tool of earned value management An Exercise in Earned Value Management in AGILE Presented by Square Peg Consulting, LLC John Goodpasture, PMP
  • 2. Copyright 2014, All rights reserved Square Peg Consulting, LLC An exercise in earned value management in Agile methods 1 Set-up and background A project applying agile methods has developed a backlog of three objects.  Backlog is a prioritized list of objects to be delivered in a scheduled time frame  An object can be anything that is countable and measureable, with a beginning effort and a clear definition of complete. A common tool in Agile methods for assessing earned value is the burn-down chart.  A burn-down chart is a plot of COUNT of backlog objects vs SCHEDULE (planned wall time)  There can be surrogates for COUNT of objects: count of stories; count of story points; count of cases; and, number of remaining hours to deplete the backlog, or number of remaining hours to complete the backlog  There is no information on the burn-down about sequence, since that would require planning the work for a specific object.  There is no information on the burn-down about actual hours or resources consumed  In this project the backlog count is 3; but the count could go up or down during the course of the project due to abandoned objects or new objects or technical debt that modifies the backlog. Technical debt is treated as objects.  An object has a burn-down status of COMPLETE or NOT COMPLETE. It’s common to link the burn-down chart with a Work in Process (WIP) chart (a.k.a Kanban chart) to track object status in finer detail than the NOT COMPLETE status. WIP status could include, but not limited to: Not Started, Design, Develop, Test, Verify, Validate, and Hold for inventory, etc. 2 Planning the project Assume the following backlog plan for the backlog with COUNT = 3: Backlog plan Object identification Planned resource Wall time Object A 40 hours 2 days Object B 45 hours 3 days Object C 35 hours 2 days
  • 3. Copyright 2014, All rights reserved Square Peg Consulting, LLC Total Backlog 120 hours 13 days Planned resource is the estimated effort; wall time includes consideration for the availability or conflicts or constraints regarding resources. Thus, a resource rate, like hours/day, is not always the case. Wall time may or may not be the calendar schedule, since there could be overlap of wall time if there are enough resources to go around. The planner should have access to a team benchmark for productivity. Productivity is not usually measured over a day; rather it is measured over a duration of a sprint or iteration, typically 2-4 weeks. A productivity measure for this project might be: 6 objects per sprint (4 weeks) 3 Setting up the baseline burn-down charts At the outset, the PLANNED VALUE of the baseline is:  REMAINING COUNT = 3;  REMAINING HOURS = 120; And, the PLANNED SCHEDULE is 12 days (1 day of overlap assumed) Since there is no information about sequence on the burn-down chart, the planner does not know if Object A will be started or completed before the other two objects, and the same for the others. Thus, simple linearity is assumed for the initial planning plots. Typically, X-Y scatter plots are applied because each axis is independent and can have its own data set. Also, the major and minor axis are independently set to integers because there is no partial credit. And, it’s typical to keep the object count and the remaining hours on different charts. Burn-down plots The following are the baseline burn-down plots.
  • 4. Copyright 2014, All rights reserved Square Peg Consulting, LLC Baseline burn-down chart: Of course, you can use row-column data in a spreadsheet chart without the plots.
  • 5. Copyright 2014, All rights reserved Square Peg Consulting, LLC 4 Running the project (exercises) For all exercise answers, apply this template: Remaining count: Remaining hours: Earned value:  objects earned  planned hours earned  hours actually used  Efficiency: planned hours/actual hours Exercise 1 Let’s assume the team starts with Object B.  At the end of Day 2, the team reports Object B is complete  Team reports 40 hours actually consumed At the end of Day 2, what is the burn-down status; what is the earned value?
  • 6. Copyright 2014, All rights reserved Square Peg Consulting, LLC Exercise 2 Now, at the beginning of Day 3, the team is informed that Object A is already developed and in a library. Five hours are required on Day 3 to move Object A from the library into the project configuration system, at which point Object A is complete. What is the burn-down status at the end of Day 3? Exercise 3 The team goes on to Object C on Day 4, completing it at the end of Day 7, four days total for Object C. 50 hours are consumed. However, at the end of Day 6, an additional requirement is discovered. Object D, valued at 40 hours. For Object D, 3 days are required, beginning on Day 7 and ending on Day 9. What is the burn-down status on Day 7? Exercise 4 On Day 9, Object D is completed. 45 hours were consumed. No additional objects have been added since the discovery of Object D. What is the burn-down status at the end of Day 9? Exercise 5 What is the final tabulation for the project, as measured from the baseline?
  • 7. Copyright 2014, All rights reserved Square Peg Consulting, LLC 5 Appendix of Answers Exercise 1 Answer Answer: Remaining count: 2 Remaining hours (for Object A and C, from the resource plan): 75 hours Earned value:  1 object earned  45 planned hours earned for Object B  40 hours actually used  Efficiency: 45/40 = 112.5% The spread of “remaining hours” is an estimate made at the end of each object delivery; this estimate would be made like other “estimates to complete”. The charts herein are examples of estimates of hour remaining. Your estimates might be different. Exercise 2 Answer Answer Remaining count: 1 Remaining hours (for Object C): 35 hours Earned value:  1 object earned  40 planned hours earned for Object A  5 hours actually used  Efficiency: 50/5 = 1000% Exercise 3 Answer Answer Remaining count: 1 (for Object D) Remaining hours: 40 hours Earned value:  1 object earned (Object C)  35 planned hours earned for Object C  50 hours actually used  Efficiency: 35/50 = 70% Exercise 4 Answer Answer Remaining count: 0 Remaining hours: 0 hours Earned value:
  • 8. Copyright 2014, All rights reserved Square Peg Consulting, LLC  1 object earned (Object D)  40 planned hours earned for Object D  45 hours actually used  Efficiency: 40/45 = 89% Exercise 5 Answer  Objects planned: 3  Objects earned: 4  Objects Remaining: 0  Planned value (hours): 120  Earned value (hours): 160  Hours remaining: 0  Hours consumed: 140  Efficiency: 160/140 = 114% Final tabulation burn-down charts
  • 9. Copyright 2014, All rights reserved Square Peg Consulting, LLC