Презентация подготовлена по материалам выступления Анатолия Таразевича на витебском Miniq #27, который был проведен 30 июля 2020: https://community-z.com/events/miniq-vitebsk-27 Про доклад: Оценки, как правило, являются необходимым злом в разработке программного обеспечения. К сожалению, люди склонны считать, что написание нового программного обеспечения - это все равно что строить дом или ремонтировать автомобиль, и что подрядчик или участвующий в нем механик должны быть в состоянии обеспечить надежную и точную оценку обьема работы и сроков её выполнения. Но это не всегда так и для того чтобы этого достичь понимания в этом вопросе - важно чтобы все люди участвующие в процессе разработки, будь то разработчик или бизнесс-аналитик, понимали главные особенности и законы эстимаций об этом мы и поговорим.

1. The 5 Laws of
Software
Estimates

2. Немного о себе
2
Анатолий Таразевич
Место работы: EPAM Systems
Должность: Software Engineer

3. Estimations
3

4. Estimation in scrum
4

5. Why story points
•Standardization
•Time Tracking
•Measuring team performance
•Comparing teams
5

6. 5 Laws of estimations
•1st : Estimates are Waste
6

7. Estimates are Waste
7

8. Estimates are Waste
8

9. 5 Laws of estimations
•1st : Estimates are Waste
•2nd: Estimates are Non-Transferable
9

10. Estimates are Non-Transferable
10

11. Estimates are Non-Transferable
11

12. 5 Laws of estimations
•1st : Estimates are Waste
•2nd: Estimates are Non-Transferable
•3rd : Estimates are Wrong
12

13. Estimates are Wrong
13

14. 5 Laws of estimations
•1st : Estimates are Waste
•2nd: Estimates are Non-Transferable
•3rd : Estimates are Wrong
•4th : Estimates are Temporary
14

15. Estimates are Temporary
15

16. 5 Laws of estimations
•1st : Estimates are Waste
•2nd: Estimates are Non-Transferable
•3rd : Estimates are Wrong
•4th : Estimates are Temporary
•5th : Estimates are Necessary
16

17. Estimates are Necessary
17

18. Estimation by analogy
18
Pros:
• Easy to collect data for evaluation
• Good accurate estimation, accuracy within 50%
• Can be used in the early stages of development
• No need to have business area knowledge
Cons:
• Need to have estimated projects base
• Quality of estimation depends on quality of the base
• Inaccurate estimates of previous projects, would affect
current estimation

19. Expert judgment
19
Pros:
• Easy to organize and make
• Might be very accurate
Cons:
• Quality of estimation depends on expert
experience
• Hard to reproduce, two experts will have
different estimations

20. Work Breakdown Structure (WBS)
20

21. Work Breakdown Structure (WBS)
21
Pros:
• Detailed and understand relationships
between deliverables and steps
• Transparency and monitoring
• Best for allocating cost and time estimates
Cons:
• Full and detailed requirements
• Scope of the project should be defined
• Poorly constructed WBS may result a
negative project outcomes

22. Planning poker
22
Pros:
• Very accurate
Cons:
• Very slow
• All team need to be involved
• All team members need to have the same
vision of the scope of 1 SP

23. The Bucket System
23

24. The Bucket System
24
Pros:
•Very fast
•Collaborative
Cons:
•Experienced team
•Roughly estimates
•Relative results

25. Three-Points estimating
25

26. Three-Points estimating
26
Pros:
• it is considered to be one of the most
accurate estimation techniques in project
management;
• it reduces the scenario with too optimistic
and too inflated estimates.
Cons:
• it requires more time to provide three
estimates for each task.

27. Thank you
27

28. THANK YOU

29. Useful links
• https://ardalis.com/5-laws-of-software-estimates
• https://technology.amis.nl/2016/03/23/8-agile-estimation-techniques-beyond-planning-poker/
• https://www.pmi.org/learning/library/agile-project-estimation-techniques-6110
• https://blog.ganttpro.com/en/project-estimation-techniques-for-greater-management/
• https://bohutskyi.com/Estimation_Techniques.html
• https://medium.com/serious-scrum/scrum-management-tells-us-to-use-story-points-9c47e7727d09