1. COPYRIGHT TOM SULZER © 2015 IS 455 Oct 1, 2015 Agenda House Cleaning Quick Review Initiate Second Life Project Teams for Second Life Project are the teams you are in … Initiate SL Role Training …

2. House Cleaning … Most of you have accepted my invitation in Second Life. One of you have NOT! COPYRIGHT TOM SULZER © 2015 Alex R. Fissure Simulation registration: Four of you have NOT! Mark H., Alex R., Ben A., Tony K.

3. Iterative/Adaptive PM with SCRUM Scope Plan Launch (Vague) Idea Product owner develops prioritized function list (Product backlog) Sprint Planning Meeting Sprint Backlog Sprint 4-hr: client presents prioritized functionality to be added to backlog 4 hr: high-level sprint plan COPYRIGHT TOM SULZER © 2015 Quick Review

4. Iterative / Adaptive PM with SCRUM Monitor and Control Close Sprint Backlog Sprint Demo Sprint Functionality SCRUM has 30 day sprints COPYRIGHT TOM SULZER © 2015

5. Final Questions  Was the business outcome realized?  Was anything learned to improve the version?  What was learned to improve the PM process?  Yes? Great!  No? Kill the project.  We’ll do better next time. COPYRIGHT TOM SULZER © 2015

6. Different Methodologies – Same Activities © 2014 TOM SULZER Traditional (Waterfall) Adaptive (SCRUM) Phases:Defining Version Scope PlanningCycle Plan ExecutingCycle Build ControllingClient Check Point ClosingPost-Version Review

7. Version Scope  Same as Defining Phase (Traditional )  Outputs:  Conditions Of Satisfaction (COS),  Project Overview Statement (POS)  Also  Best guess at prioritized list of functions (requirements) in realization that it will change COPYRIGHT TOM SULZER © 2015

8. Version Scope  Output:  Work Breakdown Structure taken to mid-level  Prioritize scope triangle parameters (time, cost, resources, scope, quality) COPYRIGHT TOM SULZER © 2015

9. Cycle Plan  Same as Planning Phase (Traditional)  Inputs (first cycle)  POS  Prioritized scope triangle  Functionality to be built  Mid level WBS  Add for subsequent cycles  Scope Bank (new ideas or thoughts on functionality – discovery) COPYRIGHT TOM SULZER © 2015

10. Cycle Plan  Process 1. Prioritize functionality into cycles for development (cycle length 2-6 weeks) Get functionality to be built this cycle 2. Decompose extracted WBS to task level 3. Note dependencies among tasks 4. Group tasks in meaningful way and assign task groups to teams 5. Team develops own schedule and resource allocation subject to cycle time and budget. COPYRIGHT TOM SULZER © 2015

11. Cycle Build  Same as Executing Phase (Traditional )  Finish cycle build schedule and resource allocation  Team members have daily task list, post status of tasks daily  PM does daily review and acts on any variances COPYRIGHT TOM SULZER © 2015

12. Cycle Build  Issue Log  Records all issues that arise and how they are addressed and resolved’  Scope Bank  Records all ideas, learning, “discovery” by teams in process of work COPYRIGHT TOM SULZER © 2015

13. Client Checkpoint  Same as Controlling Phase (Traditional )  Critical Review  Criteria:  Quality  Business Value  Consider:  Scope bank – what has been learned, how does it affect the functionality in the scope?  Revise priorities on functionality for next cycle COPYRIGHT TOM SULZER © 2015

14. Post-Version Review  Same as Closing Phase (Traditional )  Version is complete or incomplete  Allocated Budget/Time spent  Compare to success criteria  Document learning  Initial ideas for next version COPYRIGHT TOM SULZER © 2015

15. Different Methodologies – Same Activities © 2014 TOM SULZER Traditional (Waterfall) Adaptive (SCRUM) Phases:Defining Version Scope PlanningCycle Plan ExecutingCycle Build ControllingClient Check Point ClosingPost-Version Review

16. Different Methodologies – Same Activities © 2014 TOM SULZER Traditional (Waterfall) Adaptive (SCRUM) Extreme (Inspire) Phases:Defining Version ScopeVisionate PlanningCycle Plan Speculate ExecutingCycle Build Innovate ControllingClient Check PointReevaluate ClosingPost-Version ReviewDisseminate

17. Extreme PM with Flexible Model Scope Plan Launch Monitor and Control Close Visionate Speculate Innovate Reevaluate Disseminate Yes No INSPIREINSPIRE COPYRIGHT TOM SULZER © 2015

18. Mapping Extreme to Traditional Extreme (Inspire)  Visionate  Speculate  Innovate  Reevaluate  Disseminate COPYRIGHT TOM SULZER © 2015 Traditional  Scope  Planning project infrastructure  Design, Build, Test  Customer to evaluation progress  Deployment, implementation

19. Different Methodologies – Same Activities © 2014 TOM SULZER Traditional (Waterfall) Adaptive (SCRUM) Extreme (Inspire) Phases:Defining Version ScopeVisionate PlanningCycle Plan Speculate ExecutingCycle Build Innovate ControllingClient Check PointReevaluate ClosingPost-Version ReviewDisseminate

20. Second Life … Roles SL Project Role Training

21. Next time Project Scope…