Tatiana Gaidamaka: Plan ahead like James Bond does or precise project estimate without all the project details Website - https://pmday.org/online Fb Page - https://www.facebook.com/pmdayconference PMDay Videos -https://www.youtube.com/user/StartupLviv/featured

1. YALANTIS

2. ● Head of Project Management Office
in Yalantis
● 8 years in Project Management
● Project Manager Professional (PMI PMP
● Agile Certified Practitioner (PMIACP

6. Rough estimate needs to be precise!
ROM
PARAMETRIC ESTIMATE
ANALOGOUS ESTIMATE

8. A Rough Order of Magnitude Estimate (ROM estimate) is an estimation of a
project's level of effort and cost to complete. A ROM estimate takes place very
early in a project's life cycle — during the project selection and approval period
and prior to project initiation in most cases.
PMBoK

9. ● Scope being estimated three
times (SRS, UX and UI
estimates)
● For each round of estimate, a
certain level of uncertainty
applies (50%, 25%, 10%)
● Schedule being updated during
the discovery stage

12. Essentially, a parametric estimate is determined by identifying the unit cost or
duration and the number of units required for the project or activity.
PMBoK

13. ● % of estimated US
● Communications
● 10% of uncertainty
● PM Support
● BA Support
● Design support (entire UI
● QA/QC activities
● DevOps activities

14. Round 1  4th week of Planning
● Parametric estimate based
on 25% of described US
● 5409 hours
Round 2  5th week of Planning
● Parametric estimate based
on 75% of described US
● 4856 hours
Final estimate - 30 weeks
● Based on ACTUAL team’s
work
● 4870 hours

16. Analogous estimating is the process of comparing past projects with current
projects in order to estimate time and cost. Analogous estimating is done when
there is limited data on the current project. The more data that is collected from
past projects, the better the comparison will be.
PMBoK

17. 1. Actual spent hours were taken into account (not planned hours)
2. We make an assumption, that new Role is similar to one of the existing role
3. Backend and web frontend development efforts were reviewed due to expected code reuse
4. Depending on the complexity of the feature and its level of uncertainty, the analogous estimate varies
from 25% to 100% of the original effort.
For example:
- F1 30%
- F2 50%
- F4 25%
5. Wherever we do not have comprehensive historical data for Android and iOS efforts, we assume it takes
same time (100%) as for initial web frontend development. This dependency is tracked down based on the
historical data
6. Estimate does not include BA, UI/UX, PM and QA efforts. These efforts do not have impact on the
critical path and were turned down due to irrelevance of the given estimate
7. 15% risk buffer due to uncertainties is added to the estimate

18. Step 1: Estimate effort to develop sign in/sign up and profile page in new project

19. Step 2: Estimate effort to develop sign in/sign up and profile page for new role in current project. Past
development efforts may be reviewed due to expected code reuse

20. Any questions? Feel free to contact me
tatiana.gaidamaka@yalantis.net
Linkedin
© Copyright 2020 Yalantis – Full-stack mobile (iOS, Android) and web app design
and development company. All Rights Reserved