How are planning and monitoring In Agile project are quite different from traditional? Let's check it out!

1. 1
Agile Planning and Monitoring
By Nhan Nguyen

2. 2
Contents
 Planning
 Estimation methods
 Adaptive planning
 Monitoring
 Self-organizing team
 Monitoring tools

3. 3
Planning Poker
 A consensus-based technique for estimating
 Used to estimate Size (Story Point) of an User
Story -or- Effort (ideal hours) of a Task
 May use Fibonacci sequence such as 0, 1, 2, 3, 5,
8, 13, 20, 40, 100 cards

4. 4
Planning Poker Steps
1. The moderator (usually the product owner) reads out the story
2. Team discuses and each estimator selects a card that represents
his/her estimation
3. Team reveals all cards at once
4. High and low estimates are reconciled / clarified
5. Goto step 2. Future rounds show convergence, otherwise choose:
 Majority estimate -or-
 High estimate(s) -or-
 Average of the estimates -or-
 Adopt three points (PERT) averaging

5. 5
Determining User Story’s Size
1 2 3
 Select a basis size for a
user story (Basis Story)
 Estimate for the
remaining stories based
on relative size with the
basis story
2 4 6
3 6 9

6. 6
Example: Size Estimate
Size = 1
Size = ?
Size = ?

7. 7
Why does Planning Poker work?
 Sizing user stories
=> Performance is measured and get chance to improve
 It brings multiple expert opinions together
=> High and low estimates are reconciled / clarified
 Estimators improve overall understanding
=> accuracy of estimates
 Group discussions
=> averaging of the individual estimates

8. 8
Affinity Estimating
1. Silent Relative Sizing
2. Wikipedia-like Editing of Wall
3. Place Items into Relative Sizing
Buckets
4. Product Owner “Challenge”
5. Get it into Electronic tool

9. 9
Affinity Estimating

10. 10
Adaptive Planning
 5 levels of Agile Planning
 Product Vision
 Product Roadmap
 Release Planning
 Iteration Planning
 Daily Plan

11. 11
5 levels of Agile Planning

12. 12
Product Vision

13. 13
Product Roadmap

14. 14
Product Roadmap

15. 15
Release Planning
Example of Deriving estimates
• 4 Sprints
• 3 weeks long per Sprint
• 12 weeks total duration
Average of #SPs completed in a
sprint = 45 Points
Example of Definition of Done (DoD)
• Deployment testing passed
• Release notes delivered
• Build requirements met
• Integrated stress testing passed

16. 16
Iteration Planning
Example of Sprint’s DoD
• Bugs committed in sprint
resolved
• Product Owner demo
• No compile warning in code
• Code repository is tagged
Example of Story’s DoD
• Unit test passed
• Functional test passed
• Acceptance test passed
• Task’s status is updated
• Code is reviewed
• Build system compiles

17. 17
Daily Planning
Tips for daily meeting
• Focus on getting updates from
the team
• Always Be On Time
• 15 Minute Time-Box
• Avoid Lose Focus
• Make it visual
• Identify Blockers
• The Team Is Most Important
• Don’t Blog or Email or … during
Daily Meetings
Symbol Description
Good start To help start the day well
Improvement To support improvement
Focus
To reinforce focus on the
right things
Team
To reinforce the sense of
team
Status
To communicate what is
going on

18. 18
Summary of Agile Planning
Yearly
Bi-Yearly
Quarterly
Bi-Weekly
Daily

19. 19
 Self-Organizing team
 Monitoring tools
 Burn-down chart
 Burn-up chart
 Cumulative Flow Diagram
 Velocity chart
 Parking Lot Chart
 Acceptance Test Chart
 Test Coverage metrics
Monitoring

20. 20
 Define: A group of motivated individuals, who work together toward a
goal, have the ability and authority to take decisions and readily adapt to
changing demands
Self-Organizing Team
 Important ingredients:
 Pull work for themselves
 Commit on their work
 Manage their work as a group
 Still require mentoring, coaching
 Communicate more with each other
 Understand requirements and aren’t
afraid to ask questions to get their
doubts clarified
 Continuously enhance their own
skills and recommend innovative
ideas and improvements.

21. 21
Burn-Down Chart

22. 22
Burn-Up Chart

23. 23
Cumulative Flow Diagram
NewTasks
Backlog
Cycle Time
Lead Time
WIP
ToBeDone

24. 24
Velocity Chart

25. 25
Parking Lot Chart

26. 26
Acceptance Test Chart

27. 27
Test Coverage Metrics
 Function coverage
 Path coverage
 Statement coverage

28. 28
Summary
 Agile Planning
 Re-planning occurs frequently
 Estimates of size and duration are separated
 Plans are made at different levels
 Plans are based on features, not tasks
 Work-in-Progress is eliminated in every iteration
 Uncertainty is acknowledged and planned for
 Monitoring
 Tracking is at the team level
 Using visible graphs in working place

29. 29
Agile Project Room

30. 30
Agile Project Room

31. 31
Agile Project Room

32. 32
Q&A