Project Management: Program and Portfolio Information Systems course (written essay)
PPMP 20012
Program & Portfolio Information Systems
Lecture 4 for Week 4
Prepared by:
Dr. Ronny Veljanovski, BSc, PhD, GradCertTEd, CertIVFMB, PMP
Discipline Leader for Project Management,
School of Engineering & Technology
Higher Education Division
CQUniversity Rockhampton
Topics
• Topic for the week is:
– “Describe how systems engineering concepts and
methodologies can help a project manager organise a
project.”
• Lecture
– Overview
– Tasks
– Week 4
– Portfolio
2
PPMP20012
Program & Portfolio Information Systems
THE 4TH WEEK’S READINGS
Week 4 - Topic: Describe how systems engineering concepts and methodologies can help
a project manager organise a project.
• Mandatory Readings
– SEBoK http://www.sebokwiki.org
• Part 2: Foundations of Systems Engineering - 'Knowledge Area: Systems Approach Applied to
Engineered Systems';
• Part 5: Enabling Systems Engineering;
– Kerzner (2013) Chapters 1.21; 2.16-2.18; 17.18;
– AS/NZS 15288:2015 Chapter 6.1-6.2;
– Al-Mamary Y.H., Shamsuddin A, & Aziati N., (2013) "The Impact of Management Information
Systems Adoption in Managerial Decision Making: A Review" Management Information
Systems Vol 8, No. 4: pp. 010-017;
• Optional Readings
– AS ISO 21504:2016 Project, programme and portfolio management—Guidance on portfolio
management;
– Visit the PMI web site for Portfolio Management - http://www.pmi.org/Learning/portfolio-
management.aspx;
• YouTube
– What is Enterprise Project Portfolio Management (EPPM) (By Oracle Primavera)
• Portfolio for Week 3
4
SEBoK – Part 2 – Systems Approach
Applied to Engineering Systems
• Applying systems approach to help:
– Identify and understand complex problems or opportunities
– Synthesize alternatives
– Analyse and select most appropriate alternatives
– Implement and approve a solution
– Deploying, using and sustaining engineering system solutions
• Involves active participation of stakeholders during all
the activities
• A holistic approach
Source: SEBoK Wiki
A systems approach - overview
• Terminology
– Situation System: is the problem or
opportunity
– Respondent System: is a system created to
respond to the situation
– System Assets: e.g. products, services,
facilities, instruments, knowledge, methods,
tools, etc…
Source: SEBoK Wiki
A Whole System
Control element
Source: SEBoK Wiki
A Whole Lifecycle
POSIWID = Purpose of System and What it Does
S = Stimulus
R = Response
PSS = Problem Solution System Source: SEBoK Wiki
The Whole Problem
Source: INCOSE UK Sillitto (2010)
Identifying and Understanding
Problems
• Introduction
• Problem Exploration
• Problem Identification
• Problem Context
Source: SEBoK Wiki
Identifying and Understanding
Problems
• Introduction
– System Complexity
– Problem or opportunity might be difficult to
fully understand
– Systems solutions may not solve the problem
the first time
– Systems solution is still useful in increasing
understanding of both the issues and what to
try next to solve a problem
Source: SEBoK Wiki
Identifying and Understanding
Problems
• Problem Exploration
– Forming system views help stakeholders
better understand each others viewpoints
– Provides a starting point
– Hard vs Soft systems approach
Source: SEBoK Wiki
Identifying and Understanding
Problems • Problem Identification
– Hard system thinking – a problem exists and can be stated by one or more stakeholders objectively
– How difficult or well understood is the problem?
– Is the problem tame, regular or wicked? • Tame – solution might be well defined
• Regular – solutions might not be obvious and problems are encountered on a regular basis.
• Wicked – cannot be fully solved, solutions might not be obvious, serious attention should be given to them
– Who is impacted?
– Does everyone think there is a problem?
Source: SEBoK Wiki
Wicked Problems
• Poorly defines
• Complex context
• Many stakeholders are involved
• Decisions require weighing value trade-
offs
• Solutions require design and analysis
• Long time horizons
Source: SEBoK Wiki
Identifying and Understanding
Problems • Problem Context – identify a way by which a complex
system situation cab be resolved around a system-of- interest (SoI) – What’s the aim of the SoI?
– What does the wide SoI look like?
– What are the objectives of the wider SoI?
– What are the objectives?
– What are the economic, informational and other conditions?
– Hard system context – a description of a logical or ideal solution may be included
– Soft System context – ensure wider stakeholder concerns are considered, includes conceptual models
• Does not include ideal solutions but provides alternatives
Synthesising Possible Solutions
• Synthesis is an activity used to describe one more system solutions based on the problem context – What are the options for a SoI based on required
properties and behaviour for the problem or opportunity
– What are the solutions options relevant to the SoI in its intended environment
• Time, cost and risk described
– Assess the properties and behaviour of each candidate solution in the wider system context
• Iterative
Source: SEBoK Wiki
Analysis and Selection –
Alternatives • System analysis
– Assessment criteria – accessing the properties and behaviour against it
– Comparing the assessments of each candidate solution
• Effectiveness analysis – Performance criteria associated with the systems
primary and enabling functions
• Trade-off studies – Comparing characteristics of each candidate system
element to each candidate system to determine solution that balances the criteria in the best way
Implementing and Proving a
Solution
• Verification
– Does each element of the system meet the
requirements?
• Validation
– Doe the entire system meet stakeholder
needs?
Source: SEBoK Wiki
Further….
• Deploying, using and sustaining systems to solve problems (http://sebokwiki.org/wiki/Deploying,_Using,_and_ Sustaining_Systems_to_Solve_Problems)
• Stakeholder responsibility (http://sebokwiki.org/wiki/Stakeholder_Responsibili ty)
• Applying the systems approach (http://sebokwiki.org/wiki/Applying_the_Systems_ Approach)
Enabling Systems Engineering
(read)
• Part 5 – SEBoK (http://sebokwiki.org/wiki/Enabling_Systems_Engineering)
• How an ‘enterprise’ prepares and positions
itself to effectively perform SE activities.
– Enabling businesses and enterprises
– Enabling teams
– Enabling individuals
Kerzner (2013): 1.21; 2.16-2.18;
17.18;
• Concurrent Engineering
– Attempt to accomplish work in parallel (rather
than in series)
– Potential to accelerate development of
products/services
– Overlapping activities can lead to schedule
compression and lower cost
Source: Kerzner 2013
Kerzner (2013): 1.21; 2.16-2.18;
17.18;
• Risks with Concurrent Engineering?
– Too much overlap unanticipated problems,
re-work, can generate schedule slippages and
cost overruns.
Source: Kerzner 2013
AS/NZS 15288:2015
• Chapter 6.1 Agreement Processes – Acquisition Process 6.1.1
– Supply Process 6.1.2
– Chapter 6.2 Organisational Project-Enabling Processes
• Life cycle model management process 6.2.1
• Infrastructure management process 6.2.2
• Portfolio management process 6.2.3
• HR management process 6.2.4
• Quality management process 6.2.5
• Knowledge management process 6.2.6
Snippet of 15288:2015 - 6.2.3
Al-Mamary Y.H., Shamsuddin A,
& Aziati N., (2013) • "The Impact of Management Information Systems Adoption in Managerial
Decision Making: A Review" Management Information Systems Vol 8, No. 4:
pp. 010-017
• http://www.ef.uns.ac.rs/mis/archive-pdf/2013%20-%20No4/MIS2013-4-2.pdf
PMI (2013) The Standard for Program
Management -- Third Edition Chapter 2
S o
u rc
e : P
M I S
ta n
d a
rd fo
r P ro
g ra
m M
a n
a g
e m
e n
t 2 0
1 3
PMI (2013) The Standard for Program
Management -- Third Edition Chapter 2
Source: PMI Standard for Program Management 2013
PMI (2013) The Standard for Portfolio
Management -- Third Edition Chapter 2
Source: PMI Standard for Portfolio Management 2013
PMI (2013) The Standard for Portfolio
Management -- Third Edition Chapter 2 S
o u
rc e
: P M
I S ta
n d
a rd
fo r P
o rtfo
lio M
a n
a g
e m
e n
t 2 0
1 3
PMI (2013) The Standard for Portfolio
Management -- Third Edition Chapter 3
Source: PMI Standard for Portfolio Management 2013
P M
I (2
0 1
3 )
T h e S
ta n
d a
rd f o
r P
o rt
fo li o
M a
n a
g e
m e
n t
-- T
h ir d
E d
it io
n C
h a
p te
r 3
S o
u rc
e : P
M I S
ta n
d a
rd f o
r P
o rt
fo li o
M a
n a
g e
m e
n t 2
0 1
3
Week 4 - Topic: Describe how systems engineering concepts and
methodologies can help a project manager organise a
project
• Reflection: – How could you apply a systems approach to a
project?
– How can a systems approach help a PM to identify problems or opportunities
– How can a systems approach help a PM to solve problems or exploit opportunities?
– How can PM’s or other people across an organisation make better decisions?
• How will you write these reflections in the Portfolio for Week 4?
32
Summary
• Topic for the week is:
– “Describe how systems engineering concepts and
methodologies can help a project manager organise a
project.”
• Lecture
– Overview
– Tasks
– Week 4
– Reflection
33