1. Agile Project Inception He Mian 2010-11-09

4. Challenge of Status Quo

5. Status-Quo On time On budget Within Scope Struggling with Quality and always almost get it done

6. But ... Unhappy Customer Unhappy Developer Unhappy Boss Suffered Project Manager

7. Understand Reason of the Dilemma 1. Waterfall model and phase-based earned value management 2. Contract Game 3. Metrics organization, Functional teams 4. Go to the solution domain too soon 5. Defined process over Motivated People 6. Separate these who doing the work and who improving the work 7. No Gold plating Plan this Speech in Agile tour Qingdao. 7 sins of traditional Project Management & SW Engineering and Agile Way Out

8. Lean Thinking System Thinking Theory of constraint Scrum XP Kanban LSD Mary Bas Daniel Lv Yi TWers Light in the Dark

9. Let's start Compose Cross Functional team Feed them with Two Pizzas Bring the Business people in

10. But, what's next … How to start

11. Target of Project Inception

13. Expectation from Inception Project Goal Project Plan Feasibility ， Critical Decision , Risk, Dependencies

14. Project Goal

15. Project Goal For (target customer) Who (statement of the need or opportunity) The (product name) is a (product category) That (statement of key benefit, that is, compelling reason to buy) Unlike (primary competitive alternative) Our product (statement of primary differentiation) Originated from the book “Cross the chasm”

16. Project Planning

17. Project Planning Cost Scope Time Scope Time Cost fixed variable

18. Scope Time Cost Start from Product Backlog Creation Time and cost as constraint

19. Split in Problem Domain Solution Domain Problem Domain Traditional Way Agile Way Splitting at Solution Domain Splitting at Problem Domain

21. If I had 20 days to solve a problem , I would take 19 days to define it

22. Techniques for Splitting Data Boundaries Operation Boundaries Scenario based Non-Functional

23. Techniques for Splitting Nonfunctional Based Performance, Scalability … Make it work, make it better Scenario Based Meaningful Subset of steps Sunny day path, rainy day path Operation Boundaries Based C/R/U/D Connecting, Send the traffic, … Data Boundaries Based Subset of data Subset of supported protocol

25. Detailed Appropriately Fine grained Coarse grained Place holder Priority Done

27. Estimated 5 3 13 8 In Relative Size With Planning Poke

29. Now We have Or

30. And … What else yet to be planned?

31. Planning Onion and Rolling wave Plan Product Vision Product Roadmap Release Planning Sprint Planning Daily Planning @ start of each release by PO and Team @ First day of each sprint by team @ Daily scrum meeting by team members

33. Risk Planning Possibility Impact Risk Item xxxxxxxx xxxxxx Mitigation Action ： xxx Owner: xxx Low Mid High Low High Mid

34. Tips on Architecture and Non-Functional requirement Concerns

41. Try it all together

42. Risk Spike Critical arch Decision User stories Biz needs, Vision, ROI Collaboration Inception (Sprint 0) Velocity Sprint Plan Burn Down Daily Run Burn UP Iteration Del. Update Sprint 1~n Estimation Priority Release Plan Release Planning

43. Now, We are on the way!

44. Inspect and Adapt

45. Thank You!