The document discusses estimation strategies for software development projects. It begins by outlining the risks clients face when relying on estimates, such as wanting to control costs and meet deadlines. Low estimates can lead to low quality work. The document recommends using agile methods like sprints and continuous delivery to manage risks. It provides best practices for estimation, such as splitting tasks, tracking time spent, and involving the whole team. Deadlines are often missed because of inaccurate estimates and other unpredictable factors. Adopting agile methods like Scrum and Kanban can help set realistic expectations and deliver value incrementally.

1. Art of Estimation

2. Speaker: Vlad Savitsky
Working at
Skype: vlad_savitsky
vlad.savitsky@gmail.com
+38096 530 27 12

4. Agenda
● Client's risks
● Low quality problem
● Low estimates strategy
● Best Practices
● Deadline! Why again?

5. Client's risks

6. Clients vs Developers
Client: Developer:
● Wants to control the ● Hates estimates.
project budget. ● Always needs more
● Wants to get project time.
finished in time. ● Requirements is not
● Wants highest clear enough.
possible quality.

8. How clients
uses estimates?
● Planning.
● Budget.
● Credibility (Trust).
● Control project flow.

9. Recap: Estimates isn't what
clients really need.
Agile:
● Simple and clear workflow.
● Release often to get feedback (Sprints).
● Work on important tasks first.

10. Low quality problem
Weak Market Position
1
Low estimate 3
2
Low quality

13. Estimation Experiment
Task: Cut 54 trees.
Estimate this task.
How many hours it
takes 1 men to
accomplish this task?

15. Recap: Low quality
makes everyone unhappy!
Agile: Do your best!

16. Best Practices

17. Best Practices (1)
● Split tasks into smaller.
● Track your working time.
● Use pomodoro.me
● Keep in mind each stage
(testing, code review, and etc).
● Each Team has own velocity.

18. Best Practices (2)
● Let whole Team estimate.
● Use planningpoker.com.
● Estimation also takes time.
● Definition of Done.
● Real overdraft is ~3 (up to 4).

19. Recap: Estimates will never be
exact
Agile:
● Estimate using abstract Story Points.
● Story Points show difficulty of task (not time).
● Each Sprint has a velocity.

20. Deadline! Why again?

21. Reasons
● Estimates are never accurate.
● Force Majeure.
● “Bottle necks” in Development Process.
● Release at the end of project.
● There is no typical tasks.
● Bad planning.

22. Recap: Release often
Agile:
● Use Sprints (1-4 weeks)
● Demonstrate working features to client.
● Release at the end of Sprint.
● Each Sprint Product gets working increment.

23. Agile Development

24. Agile Manifesto
● Individuals and interactions
over processes and tools
● Working software
over comprehensive documentation
● Customer collaboration
over contract negotiation
● Responding to change
over following a plan
http://agilemanifesto.org/

25. Kanban
● Visualize the workflow
● Limit work-in-progress (WIP)
● Manage Flow

26. Scrum

27. Time, Cost, and Scope
Constraints

28. Recap: Agile could help avoid
stress and make all happier.
● Read about Kanban, Scrum, and Lean.
● Go to trainings.
● Sell Scrum (Agile) to your clients and Team.

29. Useful links
Scrum:
● http://scrumalliance.com/
● http://agilemanifesto.org/
● http://www.scrum.com.ua/

30. Useful links
Free Books:
● Kanban и Scrum: выжимаем максимум
– http://scrum.org.ua/wp-
content/uploads/ScrumAndKanbanRuFinal.pdf
● Scrum и XP: заметки с передовой
– http://scrum.org.ua/wp-content/uploads/2008/12/scrum_xp-
from-the-trenches-rus-final.pdf
● Scrum Handbook
– http://jeffsutherland.com/scrumhandbook.pdf

31. Useful links
Online Kanban boards:
● kanbanery.com
● trello.com

32. Do you have any questions?

33. Speaker: Vlad Savitsky
Working at
Skype: vlad_savitsky
vlad.savitsky@gmail.com
+38096 530 27 12