Daniil Michailovas - Agile estimating and planning
-
Upload
agile-lietuva -
Category
Software
-
view
279 -
download
2
Transcript of Daniil Michailovas - Agile estimating and planning
AGILE ESTIMATING & PLANNINGDanil Michailovas - May 31 2016
OVERVIEW
Agile is …EstimatingPlanningTo learn …Final thoughts
AGILE IS …
… A PROPERTY
Agile != FastAgile != Cheap
… Fast + Cheap != Agile
… A MANIFESTO
“We are uncovering better ways of developingsoftware by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and toolsWorking software over comprehensive documentation
Customer collaboration over contract negotiationResponding to change over following a plan
That is, while there is value in the items onthe right, we value the items on the left more.”
http://www.agilemanifesto.org/
… A PATH
There are many paths to reach the same goalSelecting the right path is an art... or simply a choice!
AGILE ESTIMATING
NOT DEFINED
Not in ManifestoNot in ScrumNot in KanbanNot in XP
IS MORE ABOUT WHAT THAN HOW
Definition of Done (DoD)Working Software Minimum Viable Product (MvP)Business Value vs Technical Task
You can get a feedback from client on it
COMMON TOOLS
MoSCoWToyota, Lexus, Bentley … LadaStory Points#noestimates
STORY POINTS …
Team work2*2=4 ... For Me and For YouFast while being a team activityCan be really preciseSamples …
#NOESTIMATES
No need to have same size storiesTeam work is neededCase study …
AGILE PLANNING
IS JUST A PLANNING
The reliability is just as good as much time you spend on itThe outcome is a planThe plan will fail or not just as any other planSelling a castle for a price of a house is just as insane with Agile as with any other method
SO WHERE IS THE TRICK!?
60% of all delivered features are rarely or not used at allAt the end of the day, being able to avoid this is a huge part of being Agile
FEEDBACK IS THE KEY
Regular communication with the one who will accept the result is a part of a planIt makes no sense to get feedback if you do not react to itAgile, as I understand it, makes no sense if you don’t react to feedback
OTHER IMPORTANT THINGS
Most important business features are developed firstPlan is highly visible and easy to understand and changeQuality builds trustClient must understand the plan and the progress, usually to a grater detailsContract does define who takes the risk for not delivering
SOME TOOLS
Big physical planning boardsBurndown chartPersonasAgreement on delivery are focused more on challenge than on solutionRelative estimatesClear re-estimation strategy
SOME SAMPLES
Photos
TO LEARN …
READ THE BOOK
Agile Estimating and Planning
PLAY GAMES
Board gamesScotland YardGet Kanban
SimulationsMarshmallow ChallengeVarious Scrum games
Computer strategy gamesHeroes of Might and MagicJagged Alliance
USE IN LIFE
Plan an eventRide an Off-road Bicycle
FIND A COACH
In Agile LithuaniaIn Agile Alliance
FINAL THOUGHTS
WHAT PLAN DO YOU NEED?
How far in future do you really need to see?Does a plan and a progress help you making decisions?Do you have a place for mistakes?