Project Management Information System (PMIS) Process Comparison Report

This report provides a comparative analysis of two Project Management Information Systems (PMIS): MS Project and Sciforma. The comparison is structured around the 49 project management processes outlined by the Project Management Institute (PMI), evaluating the presence or absence of each process within the two systems. The analysis covers a wide range of processes, including those related to project charter, scope management, schedule management, cost management, quality management, resource management, communication management, risk management, procurement management, and stakeholder engagement. The report identifies which processes are supported by each system, highlighting their strengths and weaknesses in terms of functionality and features. Key references, such as Kerzner's 'Project Management: a systems approach' and works by Lima, Fernandes, and Machado, and Rosenberger and Tick, are utilized to provide a comprehensive understanding of the PMIS capabilities. The findings offer valuable insights for project managers and organizations seeking to select or optimize their PMIS for effective project execution.

Running head: PROJECT MANAGEMENT INFORMATION SYSTEM
Project Management Information System
Name of the Student:
Name of the University:

1PROJECT MANAGEMENT INFORMATION SYSTEM
Project Management Information System
Process MS Project Sciforma
Process 1: Develop project
charter process
Yes Yes
Process 2: Develop project
management plan process
Yes Yes
Process 3: Direct and
manage project work
process
Yes Yes
Process 4: Manage project
knowledge process
Yes Yes
Process 5: Monitor and
control project work process
Yes No, it does have way to
monitor and control over
project phases.
Process 6: Perform
integrated change control
process
Yes No, it does have change
control information or
change requests raised
(Lima, Fernandes and
Machado 2018).
Process 7: Close project or
phase process
Yes Yes
Process 8: Plan scope
management process
No, it does not have scope
management planning
abilities (Kerzner 2017).
No, it does not have any
scope plan information for
scope planning.
Process 9: Collect Yes Yes

2PROJECT MANAGEMENT INFORMATION SYSTEM
requirements phase
Process 10: Define scope
process
No, it requires scope
statement to define project
scope.
No, this process does not
have scope plan information.
Process 11: Create WBS
process
Yes Yes
Process 12: Validate scope
process
No, as it does not have
scope information, therefore
unable to validate the project
scope.
No, this process requires
scope plan to validate scope
changes (Kerzner 2017).
Process 13: Control scope
process
No, it does not way to
control scope as there is no
scope process information
(Rosenberger and Tick
2019).
No, this process requires
scope plan to control scope.
Process 14: Plan schedule
management
Yes Yes
Process 15: Define activities Yes Yes
Process 16: Sequence
activities
Yes Yes
Process 17: Estimate activity
durations
Yes Yes
Process 18: Develop
schedule
Yes Yes
Process 19: Control Yes Yes

3PROJECT MANAGEMENT INFORMATION SYSTEM
schedule
Process 20: Plan cost
management process
Yes Yes
Process 21: Estimate costs
process
Yes Yes
Process 22: Determine
budget process
Yes Yes
Process 23: Control costs
process
Yes Yes
Process 24: Plan quality
management
No, this process does not
have way to include quality
standards (Kerzner 2017).
No, this process does not
determine quality policies
and procedures related to
project deliverables.
Process 25: Manage quality
process
No, as this process does not
include quality process,
therefore it is not require to
manage.
No, it does not have quality
procedures for project
processes (Meredith, Mantel
Jr and Shafer 2017).
Process 26: Control quality
process
No, it does not have way to
capture quality related
information (Rosenberger
and Tick 2019).
No, this process does not
have information of quality
planning.
Process 27: Plan resource
management process
Yes Yes
Process 28: Estimate activity
resources process
Yes Yes

4PROJECT MANAGEMENT INFORMATION SYSTEM
Process 29: Acquire
resource process
Yes Yes
Process 30: Develop team
process
Yes Yes
Process 31: Manage team
process
Yes Yes
Process 32: Control
resources process
Yes Yes
Process 33: Plan
communication management
process
No, it does not have
collaboration support like
online chat and others
features (Kerzner 2017).
Yes
Process 34: Manage
communications process
No, this process does not
ensure that the project
information is recorded.
Yes
Process 35: Monitor
communications process
No, this process does not
have stakeholder’s
information to
communicate.
Yes
Process 36: Plan risk
management process
Yes Yes
Process 37: Identify risks
process
Yes Yes
Process 38: Perform
qualitative risk analysis
No, this process does not
have way to assess risk
No, this process does have
risk parameters to set risk

5PROJECT MANAGEMENT INFORMATION SYSTEM
probability and impact
factors.
priorities.
Process 39: Perform
quantitative risk analysis
No, it does not have way to
set numerical value for
identified risks (Kerzner
2017).
No, this process does not
have information on risk
prioritization.
Process 40: Plan risk
responses process
Yes Yes
Process 41: Implement risk
responses process
Yes Yes
Process 42: Monitor risks
process
Yes Yes
Process 43: Plan
procurement management
process
No, this process does not
have way to capture
procurement information.
No, this process does not
have way to document seller
data (Rosenberger and Tick
2019).
Process 44: Conduct
procurement process
No, this process does not
have way to evaluate the
procurement options (Lima,
Fernandes and Machado
2018).
No, this process does not
have way to select proper
sellers for procurement
approaches.
Process 45: Control
procurement process
No, this process requires to
manage procurement
relationships to control it.
No, this process does not
have way to monitor the
contract performance.
Process 46: Identify Yes Yes

6PROJECT MANAGEMENT INFORMATION SYSTEM
stakeholder process
Process 47: Plan stakeholder
engagement process
No, this process does not
have way to plan how to
approach the stakeholders
(Lima, Fernandes and
Machado 2018).
No, this process does not
have way to manage
stakeholder’s expectations
(Rosenberger and Tick
2019).
Process 48: Manage
stakeholder engagement
process
No, this process does not
have way to manage
stakeholder’s expectations,
and interest (Meredith,
Mantel Jr and Shafer 2017).
No, this process does not
have way to manage
stakeholder’s expectations,
and impact on project.
Process 49: Monitor
stakeholder engagement
process
No, this process requires
information to monitor the
relationships between
stakeholders.
No, this process does not
have way to customize the
stakeholder engagement.

7PROJECT MANAGEMENT INFORMATION SYSTEM
References
Kerzner, H., 2017. Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Lima, A., Fernandes, G. and Machado, R.J., 2018, September. Mapping between PMI and
OGC artefacts for project portfolio management. In 2018 International Conference on
Intelligent Systems (IS) (pp. 754-762). IEEE.
Meredith, J.R., Mantel Jr, S.J. and Shafer, S.M., 2017. Project management: a managerial
approach. John Wiley & Sons.
Rosenberger, P. and Tick, J., 2019. Adaption of selected PMBOK processes to fit SCRUM
developments1, 2.