Art of Estimation. Vlad Savitsky

726 views
640 views

Published on

* How to finish project in time?
* How to make clients happy and don't lose your mind?
* Why estimates not so perfect?
* What is Agile (Scrum and Kanban)?
* and many more.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
726
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
25
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Art of Estimation. Vlad Savitsky

  1. 1. Art of Estimation
  2. 2. Speaker: Vlad Savitsky Working at Skype: vlad_savitsky vlad.savitsky@gmail.com +38096 530 27 12
  3. 3. Agenda● Clients risks● Low quality problem● Low estimates strategy● Best Practices● Deadline! Why again?
  4. 4. Clients risks
  5. 5. Clients vs DevelopersClient: 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.
  6. 6. How clients uses estimates?● Planning.● Budget.● Credibility (Trust).● Control project flow.
  7. 7. Recap: Estimates isnt what clients really need.Agile:● Simple and clear workflow.● Release often to get feedback (Sprints).● Work on important tasks first.
  8. 8. Low quality problem Weak Market Position1 Low estimate 3 2 Low quality
  9. 9. Estimation ExperimentTask: Cut 54 trees.Estimate this task.How many hours ittakes 1 men toaccomplish this task?
  10. 10. Recap: Low qualitymakes everyone unhappy! Agile: Do your best!
  11. 11. Best Practices
  12. 12. 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.
  13. 13. Best Practices (2)● Let whole Team estimate.● Use planningpoker.com.● Estimation also takes time.● Definition of Done.● Real overdraft is ~3 (up to 4).
  14. 14. Recap: Estimates will never be exactAgile:● Estimate using abstract Story Points.● Story Points show difficulty of task (not time).● Each Sprint has a velocity.
  15. 15. Deadline! Why again?
  16. 16. 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.
  17. 17. Recap: Release oftenAgile:● Use Sprints (1-4 weeks)● Demonstrate working features to client.● Release at the end of Sprint.● Each Sprint Product gets working increment.
  18. 18. Agile Development
  19. 19. 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/
  20. 20. Kanban● Visualize the workflow● Limit work-in-progress (WIP)● Manage Flow
  21. 21. Scrum
  22. 22. Time, Cost, and Scope Constraints
  23. 23. 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.
  24. 24. Useful linksScrum:● http://scrumalliance.com/● http://agilemanifesto.org/● http://www.scrum.com.ua/
  25. 25. Useful linksFree 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
  26. 26. Useful linksOnline Kanban boards:● kanbanery.com● trello.com
  27. 27. Do you have any questions?
  28. 28. Speaker: Vlad Savitsky Working at Skype: vlad_savitsky vlad.savitsky@gmail.com +38096 530 27 12

×