art of estimation. vlad savitsky
DESCRIPTION
* 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.TRANSCRIPT
Art of EstimationArt of Estimation
Speaker: Vlad SavitskySpeaker: Vlad Savitsky
Working at
Skype: vlad_savitsky
+38096 530 27 12
AgendaAgenda
● Client's risks● Low quality problem● Low estimates strategy● Best Practices● Deadline! Why again?
Client's risksClient's risks
Clients vs DevelopersClients vs Developers
Client:● Wants to control the
project budget.● Wants to get project
finished in time.● Wants highest
possible quality.
Developer:● Hates estimates.● Always needs more
time.● Requirements is not
clear enough.
How clients How clients uses estimates?uses estimates?
● Planning.● Budget.● Credibility (Trust).● Control project flow.
Recap: Estimates isn't whatRecap: Estimates isn't whatclients really need.clients really need.
Agile:● Simple and clear workflow.● Release often to get feedback (Sprints).● Work on important tasks first.
Low quality problemLow quality problem
Weak Market Position
Low estimate
Low quality
1
2
3
Estimation ExperimentEstimation Experiment
Task: Cut 54 trees.
Estimate this task.
How many hours it takes 1 men to accomplish this task?
Recap: Low quality Recap: Low quality makes everyone unhappy!makes everyone unhappy!
Agile: Do your best!
Best PracticesBest Practices
Best Practices (1)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.
Best Practices (2)Best Practices (2)
● Let whole Team estimate.● Use planningpoker.com.● Estimation also takes time.● Definition of Done.● Real overdraft is ~3 (up to 4).
Recap: Estimates will never be Recap: Estimates will never be exactexact
Agile:● Estimate using abstract Story Points.● Story Points show difficulty of task (not time).● Each Sprint has a velocity.
Deadline! Why again?Deadline! Why again?
ReasonsReasons
● Estimates are never accurate.● Force Majeure.● “Bottle necks” in Development Process.● Release at the end of project.● There is no typical tasks.● Bad planning.
Recap: Release oftenRecap: 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.
Agile DevelopmentAgile Development
Agile ManifestoAgile 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/
KanbanKanban
● Visualize the workflow● Limit work-in-progress (WIP)● Manage Flow
ScrumScrum
Time, Cost, and Scope Time, Cost, and Scope ConstraintsConstraints
Recap: Agile could help avoid Recap: Agile could help avoid stress and make all happier.stress and make all happier.
● Read about Kanban, Scrum, and Lean.● Go to trainings.● Sell Scrum (Agile) to your clients and Team.
Useful linksUseful links
Scrum:● http://scrumalliance.com/● http://agilemanifesto.org/● http://www.scrum.com.ua/
Useful linksUseful 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
Useful linksUseful links
Online Kanban boards:● kanbanery.com● trello.com
Do you have any questions?
Speaker: Vlad SavitskySpeaker: Vlad Savitsky
Working at
Skype: vlad_savitsky
+38096 530 27 12