Project Briefing
1
Nick Small, Shawn Boughey, Karolina Latkoska
Agenda
1.
2.
3.
4.
5.
Business Case
Stakeholder Engagement
Scope
Schedule
Status
6. Managing Risks
7. Controlling Changes
8. Ensuring Quality
9. Summary
10.Questions
2
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
Nick Small, Shawn Boughey, Karolina Latkoska
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
• Four phases
–
–
–
–
Project Planning
Requirements Analysis
Design
Project Closure
8
Nick Small, Shawn Boughey, Karolina Latkoska
4b. Schedule (link)
9
Nick Small, Shawn Boughey, Karolina Latkoska
Complete
In Progress
5. Status
Overdue
Project Planning
Requirements Analysis
• Project Charter
• Use Case Diagram
• Project Management
Plan
• Use Case Narratives
• Risk Mgt Plan
• Change Mgt Plan
• Project Quality Plan
• Communication Plan
• Sequence Diagrams
• Data Flow Diagrams
• Domain Diagram
Design
• Functional
Specifications
• System Architecture
• Database Design
Specification
• Data Migration
Strategy
• GUI Specification
• Configuration Plan
• Project Closure
Document
10
Nick Small, Shawn Boughey, Karolina Latkoska
6a. Managing Risks
Risk
identification
Risk
monitoring
Risk triggers
Risk
assessment
Risk
controls
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)
Description
Likelihood
Consequence
Risk
Rating
Risk Controls
Risk Triggers
C=consequence control
Residual Risk
L=likelihood control
Team members
with limited time
Almost
certain
Major
Extreme
Not meeting
deliverables
milestones
Lack of feedback
on documents
requiring review
Inactivity on
Wikispaces
Loss of team
members
Unlikely
Major
High
Team member
advises dropping
out
Clear action items each
week (C)
High
Review progress weekly:
identify delays, formulate
action to address (C)
Communicate requests for
help through Wikispaces
(C)
Negotiate reduced scope
with client (C)
Team member
not contactable
Nick Small, Shawn Boughey, Karolina Latkoska
Medium
7a. Controlling changes
What is the
change?
What is the
benefit?
What will it
take?
What if we
don’t?
Nick Small, Shawn Boughey, Karolina Latkoska
Quality and
risk?
7b. 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
8. Ensuring Quality
Quality Reviews
Product Descriptions
Product Descriptions
Deliverable Quality Assurance
Checklists
Deliverable Quality Assurance
Checklists
Agreed with client
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 2.0
17
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...
Nick Small, Shawn Boughey, Karolina Latkoska