Answered: PMs Most Common Agile Questions

Transcription

1 Answered: PMs Most Common Agile Questions

2 Mark Kilby Agile Coach, Rally Software (cell) Led Fortune 50 agile transitions in - Government - Technology - Healthcare - Insurance/Fina ncial

3 Bring us your toughest Agile Questions

4 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?

5 How do roles change?

6 Contribution over Role Role over Title

7 Small (5-9) Dedicated Persistent Cross-Functional Collaborative Empowered No Egos Delivery Team

8 Product Owner Represents users/customers One voice for team Prioritizes ALL work Calls for releases Owns ROI

9 Scrum Master Servant Leader Facilitates Team Enforces principles Removes impediments Not a decision maker

10 RACI is Dead

11 Other Roles

12 I Manage Projects!

13 Exception

14

15 How to work with Distributed Teams?

16 Mandatory Co-Located Teams is a Myth!

17 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

18 Communicate Effectively

19 Co-located Part-time Co-located Distributed, High Overlap Distributed, Low Overlap Distributed, Low Overlap + Culture Distributed, Low Overlap + Culture & Organization Easier Harder

20 Jeff Sutherland Fully Distributed Scrum: Replicating Local Productivity and Quality with Offshore Teams Fully Distributed Scrum: The Secret Sauce for Hyperproductive Offshore Development Teams Distributed Scrum: Agile Project Management with Outsourced Development Teams HYPER-PRODUCTIVITY = 4X IMPROVEMENT

21

22 The off-shore code/test Factory (CAUTION)

23 Off-shore Automated Testing Factory

24

25 How do I work with Waterfall Teams?

26 Collaboration

27 PMBOK Project Phase 2008 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide) 4 th Edition

28 PMBOK 3 Phase Project

29 5 Levels of Agile Planning Vision Roadmap Release /Phase Iteration Dail y

30 5 Levels of Agile Planning Vision Roadmap Release /Phase Iteration Dail y

31 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

32 Release/Phase 1 Iteration 0 Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration X

33 Iteration Zero Backlog Story writing Estimating Splitting Prioritizing Architecture High-level Spikes Release Planning Team(s) Iter. Length Velocity Dependencies Risks Scheduling Coordination

34 Planning Workshop

35 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

36 Considerations Business Value Risk Mitigation Learning Dependencies Constraints

37 Reporting Progress % Complete Burn-downs Earned Value Parking Lot Diagrams Risk Lists Etc

38

39 How do we fund agile projects?

40 How do we Plan Agile Projects?

41 Could I have some money? I don t have a plan, but I m agile

42 Budget

43 THE TEAM

44 Backlog

45 $??? COST

46 Release/Phase 1 COST? Iteration 0 Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration X

47 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

48 Velocity

49 VELOCITY = DISTANCE TIME

50 Units Completed EMPIRICAL EVIDENCE Sprint 1 Sprint 2 Sprint 3 Sprint 4 Worst = 10 Average = 15 Best = 20

51 ESTIMATESIZ DERIVEDURATIO E N SIZE CALCULATION DURATION 120 UNITS VELOCITY = 15 8 ITERATIONS

52 WHEN will we finish? (Fixed scope) Total Units 120 Low Velocity 10 Average Velocity 15 High Velocity = = = Adapted from Mike Cohn

53 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

54 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

55 FUNDING MODELS

56 Traditional Build the Backlog Select the Team Known cost Known velocity Size the Backlog Fixed Scope Predict Schedule & Cost Fixed Schedule Predict Scope & Cost

57 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

58 Fixed Price They re Paying to avoid Risk Data mitigates yours Incremental Delivery Mitigates Risk Builds Trust Eases Change Mgmt

59 Price / Point Risk avoidance of Fixed Price Flexibility of Incremental Adaptability of Time & Material

60 More Questions?

61 THANK YOU!