Answered: PMs Most Common Agile Questions
Mark Kilby Agile Coach, Rally Software mkilby@rallydev.com 407.687.3350 (cell) Led Fortune 50 agile transitions in - Government - Technology - Healthcare - Insurance/Fina ncial
Bring us your toughest Agile Questions
AGENDA Top Questions How do traditional roles change? How do I work with distributed teams? How do I work with waterfall teams? How do I fund agile projects? Other questions?
How do roles change?
Contribution over Role Role over Title
Small (5-9) Dedicated Persistent Cross-Functional Collaborative Empowered No Egos Delivery Team
Product Owner Represents users/customers One voice for team Prioritizes ALL work Calls for releases Owns ROI
Scrum Master Servant Leader Facilitates Team Enforces principles Removes impediments Not a decision maker
RACI is Dead
Other Roles
I Manage Projects!
Exception
How to work with Distributed Teams?
Mandatory Co-Located Teams is a Myth!
Agile Principles Business people and developers must work together daily through the project The most efficient and effective method of conveying information to and within a development team is face-to-face conversation http://agilemanifesto.org
Communicate Effectively
Co-located Part-time Co-located Distributed, High Overlap Distributed, Low Overlap Distributed, Low Overlap + Culture Distributed, Low Overlap + Culture & Organization Easier Harder
Jeff Sutherland Fully Distributed Scrum: Replicating Local Productivity and Quality with Offshore Teams - 2009 Fully Distributed Scrum: The Secret Sauce for Hyperproductive Offshore Development Teams - 2009 Distributed Scrum: Agile Project Management with Outsourced Development Teams - 2007 HYPER-PRODUCTIVITY = 4X IMPROVEMENT
The off-shore code/test Factory (CAUTION)
Off-shore Automated Testing Factory
How do I work with Waterfall Teams?
Collaboration
PMBOK Project Phase 2008 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide) 4 th Edition
PMBOK 3 Phase Project
5 Levels of Agile Planning Vision Roadmap Release /Phase Iteration Dail y
5 Levels of Agile Planning Vision Roadmap Release /Phase Iteration Dail y
Roadmap Planning Phase / Release 1 Phase / Release 2 Phase / Release 3 THEME 1 THEME 2 THEME 3 1. Feature A 2. Feature B 3. Feature C 1. Feature A 2. Feature B 3. Feature C 1. Feature A 2. Feature B 3. Feature C
Release/Phase 1 Iteration 0 Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration X
Iteration Zero Backlog Story writing Estimating Splitting Prioritizing Architecture High-level Spikes Release Planning Team(s) Iter. Length Velocity Dependencies Risks Scheduling Coordination
Planning Workshop
Release/Phase Planning Iteration 1 Iteration 2 Iteration 3 Iteration X 1. Story A 2. Story B 3. Story C 1. Story D 2. Story E 3. Story F 1. Story G 2. Story H 3. Story I 1. Hardening Analysis Design Code Test
Considerations Business Value Risk Mitigation Learning Dependencies Constraints
Reporting Progress % Complete Burn-downs Earned Value Parking Lot Diagrams Risk Lists Etc
How do we fund agile projects?
How do we Plan Agile Projects?
Could I have some money? I don t have a plan, but I m agile
Budget
THE TEAM
Backlog
$??? COST
Release/Phase 1 COST? Iteration 0 Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration X
Iteration Cost DATA Team size: Team Velocity: assume 7 people (can range 4-10) $90/hr/person Avg: 40hr/week $25,200 / week Iter. Length: 2 weeks (can be 1-4 weeks for different projects, but iteration is fixed for a project) Cost per Iteration: $52,400
Velocity
VELOCITY = DISTANCE TIME
Units Completed EMPIRICAL EVIDENCE 25 20 15 10 5 0 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Worst = 10 Average = 15 Best = 20
ESTIMATESIZ DERIVEDURATIO E N SIZE CALCULATION DURATION 120 UNITS VELOCITY = 15 8 ITERATIONS
WHEN will we finish? (Fixed scope) Total Units 120 Low Velocity 10 Average Velocity 15 High Velocity 20 120 20 = 120 15 = 120 10 = Adapted from Mike Cohn
WHAT will we finish? (Fixed schedule) Will Have 80 units Line of hope 120 units Might Have 150 units Line of despair Won t Have
PROJECT PLAN DATA Backlog size: Team Velocity: Team Cost: Iter. Length: 274 units Low: 18 units / iter. Avg: 22 units / iter. High: 25 units / iter. $52,400 / iter. 2 weeks Projections Best Case: Schedule: 22 wks Cost: $576,400 Most Likely: Schedule: 26 wks Cost: $681,200 Worst Case: Schedule: 32 wks Cost: $838,400
FUNDING MODELS
Traditional Build the Backlog Select the Team Known cost Known velocity Size the Backlog Fixed Scope Predict Schedule & Cost Fixed Schedule Predict Scope & Cost
Incremental Scope - Schedule Cost Whole project Remainder of project Next iteration Pay for only next iteration We ll deliver something valuable We ll update our projections You Decide if you want another
Fixed Price They re Paying to avoid Risk Data mitigates yours Incremental Delivery Mitigates Risk Builds Trust Eases Change Mgmt
Price / Point Risk avoidance of Fixed Price Flexibility of Incremental Adaptability of Time & Material
More Questions?
THANK YOU! Mark.Kilby@rallydev.com