+ All Categories
Home > Business > Agile Estimations in a Traditional World

Agile Estimations in a Traditional World

Date post: 14-Apr-2017
Category:
Upload: aca-it-solutions
View: 606 times
Download: 0 times
Share this document with a friend
15
Agile estimations in a traditional world Nico De Greef, PMP Independent Agile Coach BE
Transcript
Page 1: Agile Estimations in a Traditional World

Agile estimations in a traditional world

Nico De Greef, PMPIndependent Agile Coach

BE

Page 2: Agile Estimations in a Traditional World

Today’s Methodologies

Traditional Prince2 PMBoK

Agile Scrum

Page 3: Agile Estimations in a Traditional World

Difference in Approach

Prince2, PMBoK are PROJECT based Agile (Scrum) is a PRODUCT based

Page 4: Agile Estimations in a Traditional World

Difference in Terminology

Terminology Sprints, Story Points, Velocity

Agilians are not project managers PID, EVM, Gantt Chart, Matrix organization, Critical Path,

Business Case, Project Charter, …?

Governance Compliance Standardized PMO reporting, …

Page 5: Agile Estimations in a Traditional World

Giveaway

Interview question:How does a project start?

Page 6: Agile Estimations in a Traditional World

Traditional World

• Scope• Schedule• Cost• Quality

Agile World

• Scope• Schedule• Cost• Quality

Page 7: Agile Estimations in a Traditional World

Earned Value Management (EVM)

Planned BAC = Initial Budget at Completion PV = Planned Value

Measured AC = Actual Cost EV = Earned Value

Calculated ETC = Estimate to Complete EAC = Estimate at Completion

Page 8: Agile Estimations in a Traditional World

ProjectStart

ProjectEnd

BAC300.000 €

PlannedMeasured

Today3 months far

(50%)

PV150.000 €

EV(40%)

120.000 €

AC(60%)

180.000 €

EAC = AC + (BAC-EV) x AC / EV= 180.000 + (300.000-120.000) x 180.000 / 120.000= 450.000

EAC450.000 €

a 6 months project

ETC270.000 €

Calculated

NEWProject

End

Page 9: Agile Estimations in a Traditional World

Earned Value Management

Earned Value Management means MathEstimate to Complete

=(BAC-EV) x AC / EV

Some PMs take a shortcutEstimate to Complete

=BAC – AC

30% is done, 70% remaining

until 1 month before the deadline...

Page 10: Agile Estimations in a Traditional World

Agile EVM

Estimate to Complete is easy Built-in in Scrum

Page 11: Agile Estimations in a Traditional World

Before we continue Sprint

Fixed duration of work for the team

Story Functional specification of a task Estimated in story points

Story Point Relative Estimation of effort, risk and complexity Fibonacci compensated

Velocity Number of story points delivered during a sprint

Capacity Number of man-days consumed in a sprint

Page 12: Agile Estimations in a Traditional World

Agile EVM chart – day 0

For demo purposes:1 sprint = 50.000 €= 5 developers, 20 days, 500€/day

BAC

50% PV after 3 sprints

Page 13: Agile Estimations in a Traditional World

Agile EVM chart – after 3 months

For demo purposes:1 sprint = 50.000 euro= 5 developers, 20 days, 500€/day

40% (EV)

5+ sprints

ETC

EAC

But upstaffing first 3 months1 sprint = 60.000 euro

AC

Page 14: Agile Estimations in a Traditional World

Why so easy? Agile Forecasts are based on the story point relative estimation

It takes into account past performance, for future delivery

Example If you planned to spent 10 Story points a sprint 50 story points would be forecasted to 5 sprints

If you actually deliver 5 story points a sprint 50 story points would be forecasted to 10 sprints

No complex re-estimation needed!

Agile EVM Capacity, scope change (less or more story points) and past performance (velocity) impact

number of sprints Number of sprints indicate cost and schedule

Page 15: Agile Estimations in a Traditional World

Questions ?


Recommended