Nick Small, Shawn Boughey, Karolina Latkoska Project Briefing 1

Nick Small, Shawn Boughey, Karolina Latkoska Agenda 1.Business Case 2.Stakeholder Engagement 3.Scope 4.Schedule 5.Status 2 6.Managing Risks 7.Controlling Changes 8.Ensuring Quality 9.Summary 10.Questions

Nick Small, Shawn Boughey, Karolina Latkoska 1. Business Case New system for managing GAZCars conversions Fully specified in 15 weeks Cost of inaction is much higher than action Existing system is unreliable Instil customer confidence (conversion choices) Contact with existing customers simplified 3

Nick Small, Shawn Boughey, Karolina Latkoska 2. Stakeholder Engagement Stakeholders identified via GAZCars Industry Briefing Paper and liaising with client representatives Online forums Stakeholders documented in Project Management Plan Stakeholder engagement outlined in Communications Plan 4

Nick Small, Shawn Boughey, Karolina Latkoska 5

3a. Scope IN SCOPE Database design Decision support system OUT OF SCOPE Online booking system 6

Nick Small, Shawn Boughey, Karolina Latkoska 3b. Scope (deliverables) IN SCOPE Complete project document suite –Project planning documentation –Requirements analysis documentation –Design documentation OUT OF SCOPE Working prototype 7

Nick Small, Shawn Boughey, Karolina Latkoska 4a. Schedule 8 Four phases –Project Planning –Requirements Analysis –Design –Project Closure

Nick Small, Shawn Boughey, Karolina Latkoska 4b. Schedule (link)(link) 9

Nick Small, Shawn Boughey, Karolina Latkoska 5. Status Project Planning Project Charter Project Management Plan Risk Mgt Plan Change Mgt Plan Project Quality Plan Communication Plan Configuration Plan Project Closure Document Requirements Analysis Use Case Diagram Use Case Narratives Sequence Diagrams Data Flow Diagrams Domain Diagram Design Functional Specifications System Architecture Database Design Specification Data Migration Strategy GUI Specification 10 Complete In Progress Overdue

Nick Small, Shawn Boughey, Karolina Latkoska 6a. Managing Risks Risk identification Risk assessment Risk controls Risk triggers Risk monitoring 11

Nick Small, Shawn Boughey, Karolina Latkoska 6b. Key Project Risks Team members with limited time and availability Loss of team members Unclear requirements Uncertainty over responsibilities 12

Nick Small, Shawn Boughey, Karolina Latkoska 6c. Risk Register (link)(link) DescriptionLikelihoodConsequence Risk Rating Risk Triggers Risk Controls C=consequence control L=likelihood control Residual Risk Team members with limited time Almost certain MajorExtremeNot meeting deliverables milestones Lack of feedback on documents requiring review Inactivity on Wikispaces Clear action items each week (C) Review progress weekly: identify delays, formulate action to address (C) Communicate requests for help through Wikispaces (C) High Loss of team members Unlikely MajorHighTeam member advises dropping out Team member not contactable Negotiate reduced scope with client (C) Medium

Nick Small, Shawn Boughey, Karolina Latkoska 7a. Controlling changes What is the change? What is the benefit? What will it take? What if we don’t? Quality and risk?

Nick Small, Shawn Boughey, Karolina Latkoska 7b. Controlling changes What is the change? What is the benefit? What will it take? What if we don’t? Quality and risk? Adapt to Lost Team Member Complete Promised Deliverables On-Time Reduction in Project Scope Possible Project Failure Risk Mitigation Measure

Nick Small, Shawn Boughey, Karolina Latkoska 8. Ensuring Quality Product Descriptions Deliverable Quality Assurance Checklists Agreed with client Quality Reviews Product Descriptions Deliverable Quality Assurance Checklists Final team review Sign-off by client

Nick Small, Shawn Boughey, Karolina Latkoska 9. Summary Issues: Existing database is a mess GAZCars’ business is expanding Require increased functionality and reliability Solution : PG Project Maniacs GAZCars EMS

Nick Small, Shawn Boughey, Karolina Latkoska References Duncan, WR 1996, A Guide to the Project Management Body of Knowledge, Project Management Institute, Sylva, North Carolina Object Management Group 2009, Unified Modelling Language Infrastructure Version 2.2 Standards Australia 2004, AS/NZS 4360:2004 Risk Management Stumpf, R and Teague, L 2005, Object-Oriented Systems Analysis and Design with UML, Pearson, New Jersey 18

Nick Small, Shawn Boughey, Karolina Latkoska 10. Questions...