PowerPoint Presentation
Digital Campus
Project
Project
management
Stakeholder
management
Project internal
communication
Analysis &
Planning
Requirement
Budget
Period
Monitoring &
Controlling
Design
Website
UI
Front-end
Back-end
Platform
feature APIs
Development
Website
UI
Front-end
Back-end
Platform
feature APIs
Support
document
Test
Internal test
Canary test and
dark launch
Optimize
HR
Recruitment
Finances
Acceptable WBS – use WBS numbering to distinguish between the
WPs – be more specific to your project (seems a bit too close to a
template for IT project)!
WBS (Top 3 Level)
Digital Campus (ZIPPY) Release 1.0v
Requirements
& Tasks
Market Research
Test & Integration Publication
Software
Developments
Test & Integration
Plan, Scenario
API Connection
Test Demo Workshop
User Training
Project
Management
Analysis of
requirement
Software
Development Plan
Development
(sprint1)
Analysis of
Satisfaction
WBS
Management of
Schedule & Budget
Release Integrated
System
Management of
Goal & Scope
Management of
Organization
Management of
Project Plan
User Interface
Training
Development
(sprint2)
Management of
Communication
User Interface
Interview
Management of
Risks
Agreement
Low Fidelity
UI Prototype
High Fidelity
UI Prototype
Use Case
Development
(sprint3)
Software
Architecture
Software
Training
User Interface
Test
Integrated
Training
Integration
Functional Test
Integrated Test
Code Review &
Optimization
Survey
System Operator
Training
Context Scenario
Usability Test
(Low Fidelity)
Usability Test
(High Fidelity)
good WBS, but remember to use deliverables/outcomes in the
WBS not the activities: it does make sense, but would have
been better to put outputs of sprint 1, 2 etc in the WBS than
the sprint itself – otherwise how would you know the
deliverable has been achieved?
WBS
3
WBS is too limited and needs further development before it can
be used as a basis for project planning. You should organise the
top level by major project deliverable and not by project
lifecycle phase. The WBS is not used as a scheduling tool. Don’t
put activities in the WBS (test equipment), rather put the
outcomes of activities in the WBS.
WBS
WBS seems to be missing deliverables related to the product, there is
Design and Testing but nothing in between?
Good effort on WBS, looks like you have given project some thought but
you have to tidy up the WBS before it can be used for project planning.
Not clear what the connectors are doing, also has mix of activities and
deliverables (should be deliverables only), branches seem to be
timelines which is incorrect
Biomedical
Makerspace
1.1 Concept
Validation
1.1.1 Project
Background
1.1.2 Academics
Needs Analysis
1.1.3 Student
Needs Analysis
1.1.5 Makerspace
Vision Alignment
1.1.6
Sponsorship
1.1.4 UNSW
2025 Strategy
Alignment
1.2 Design &
Planning
1.2.1 Project
Scope
1.2.2 Risk Analysis
and Risk
Management
1.2.3 Cost and
Time Schedule
Management
1.2.5
Communications
Management
1.2.6 Stakeholder
Engagement
1.2.4 Human
Resource
Management
1.3 Pre-
Construction
1.3.1 Invitation to
Tender for
Construction Work
1.3.2 Site
Assessment,
Approval and Permits
1.3.3 Contact
UNSW Suppliers
1.3.5 Vendor and
Bidding of
Makerspace
Equipment
1.3.4 Licensing &
Authorisation for
Makerspace
Equipment
1.4
Procurement
1.4.1 Personal
Protective
Equipment (PPE)
1.4.2 Makerspace
Equipment
Procurement
1.4.3 Technician
Manuals (Medical
Devices)
1.5
Construction
1.5.1 Facility
Construction
1.5.2 Quality Control
1.5.3 Emergency
and Safety
Systems
1.5.5 Sustainable
Recycling Systems
1.5.4 Air Ventilation
Control Systems
1.6 Testing
1.6.1 Project
Delivery
1.6.2 Review of
Risk Analysis &
Risk Management
1.6.3 Review of
Project Cost and
Time Schedule
1.7 Closing &
Handover
1.7.1 Strengths &
Weaknesses of
Project
1.7.2 Measure
Stakeholder
Satisfaction
1.7.3 Final Cost
and Training
Budget
1.7.5 Final Project
Report
1.7.6 Project
Close-out
Meeting
1.7.4
Achievements
1.8 Training &
Support
1.8.1 Online
Safety Modules
1.8.2 Instruction
Manuals for
Makerspace
Equipment
1.8.3 Online
Badge-based
Workshop
Modules
1.8.5 Other
Supporting
Resources
1.8.4 Workshop
Supplies
Work Breakdown
Structure
1.1.7 Benefits
Management
Plan
WBS has too much emphasis on the PM work, missing much of
the product scope. Planning and design is a good deliverable,
but on inspection it is a list of PM outcomes and not actually
related to the design of the product, which is missing. 100%
rule?
ChemEngg Makerspace
Determine needs &
requirements
Develop project charter Quality Checkpoint Data Analysis
Gather data
Document current
Makerspace facilities
Gain Sign off/high level
requirements
Analyse training needs
Planning
Develop project plan
Gain Plan Approval
Prepare WBS
Assign tasks
Design & Execution
Identifying the space
Design of the layout
Procurring new
equipement
Refurblishment
contracting
Room refurblishment Install and configure
equipment
Formulating a WHS
manual
Desiging and
implementing a web
portal for stakeholders
ongoing support
Developing a remope
operation and training
system
Acceptance testing
Evaluation test 1
Add, modify, rectify
Evaluation test 2
Closure
Lesson learnt
Handover to
Stakeholder ongoing
support
InitiationSchedule Kick off meeting
Missed the point about WBS. Need to talk to your
demonstrator. Should have deliverables and outcomes in the
WBS, not activities. Odd structure.
WBS
Slide Number 2
WBS
Slide Number 4
Slide Number 5
Slide Number 6
Slide Number 7