Introduction to Agile Estimate and planning

1. 1
2 0 1 3 – Ju n
By: Mohamed Saad

2.  The Problem and the Goal
 Why Planning Fails
 An Agile Approach
 References.
2

3. “Planning is everything. Plans are nothing.”
 Why Do Planning
› Reducing risk
› Reducing uncertainty
› Supporting better decision making
› Establishing trust
› Conveying information
3

4.  What Makes a Good Plan?
› Making tradeoff decisions
› Build Set of features with resources in specific Time
 What Makes Planning Agile?
› Is focused more on the planning than on the plan
› Encourages change
› Results in plans that are easily changed
› Is spread throughout the project
4

5. “No plan survives contact with the
enemy.”
 Planning Is by Activity Rather
Than Feature
› Activities don’t finish early.
› Lateness is passed down the schedule.
› Activities are not independent.
5

6.  Multitasking Causes Further Delays
6

7.  Features Are Not Developed by
Priority
 We Ignore Uncertainty (need
iterative planning)
 Estimates Become Commitments
› Estimates are probabilities
› Commitments are dates with (prob.
< 1)
7

8. “A good plan violently executed now is better
than a perfect plan executed next week.”
 Individuals and interactions over processes and
tools
 Working software over comprehensive
documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan
8

9.  An Agile Approach to Projects
› Work as one team (common goal)
› Work in short iterations (timeboxed)
› Deliver something each iteration
› Focus on business priorities (user stories)
› Inspect and adapt (change each
iteration)
9

10.  An Agile Approach to Planning
› Multiple Levels of Planning
 Release
 Iteration
 Day
 Product
 Portfolio
 Strategic
10

11.  An Agile Approach to Planning
› Conditions of Satisfaction
 Release level
 Scope
 Schedule
 Budget
 quality
 Iteration Level
11

12.  Agile Estimating and Planning by Mike
Cohn.
12