Professional Documents
Culture Documents
---x---
Plans are nothing; planning is everything
Eisenhower
Agile projects successful 3X more than non-
agile projects.
Benefit of (good) Estimates
• Reduce risk
• Reduce uncertainty
• Establishes trust
• Transmit information/knowledge
Planning
Agile Waterfall
Empirical Predictive
MoSCoW Must have, Should have, Could have, Would not have
Should haves Important, but absence of it would not make the product
useless
Would not haves Out of scope, defines the boundary of the product
ideal
Release every sprint
Expanding scope of MVP
Kano Analysis
Survey
Q#2 Rate your satisfaction if the product does not have “this” feature?
Answers:
A) Like it,
B) Neutral,
C) Dislike it
How much extra would you pay for “this” or more of “this” feature?
Kano Analysis
Q#1 (Presence of a feature)
Like Neutral Dislike
Like
- ?
Q#2 (Absence of a feature)
L
Neutral
E I ?
Dislike
L T -
High Medium 2
High High 3?
Medium Low 4?
Low Low 5?
Medium Medium 6?
Medium High 7
Low Medium 8
Low High 9
12
Sprint Planning
13
Sprint 0
14
Integration / Stabilization Sprint
15
Rules of thumb
• A team size of 7-9
• 1 and half medium stories per developer
• 1 Tester for every two developers
• Do not change sprint length
• Prefer 100% allocation over partial allocation of people
Estimation
Relative Absolute
Challenges?
Definition of “Done”
MS Project
50% done
Waterfall
Vs. ScrumPad
Metrics Velocity,
Bug find rate per sprint,
Bug fix rate per sprint,
Test coverage
Tracking progress
Sprint Review Team meets with the product owner and stakeholders to show
the work done in the current sprint and solicit feedback.
Track done
Tracking
release
Let’s test our understanding
Difference between relative vs. absolute estimation?
How to do resource allocation?
How to handle shared resources?
How to plan for production support work?
Do you still need a Gantt chart?
How to plan for fixed bid contract?
Who does planning?
What is velocity?
How to improve estimation?
How do you ensure team delivers what they plan to deliver in a sprint?
Recap
• Prioritize product backlog on an on-going basis
• Staff the team in the beginning and keep the team in place through out the life of the
project
Recap contd.
• The team should be cross-functional- include testers, Sys admins, DBA,
SMEs
32