Project Management
Integration Management»
Powered by Hackadelic Sliding Notes 1.6.5
Definition: Initiating, planning, executing, controlling, and closing of all key project, IT, and change management plans, processes, and outputs required to achieve project success.
Process: Prepare the feasibility study and business case
The process of developing a document based on research and quantification created to guide management decisions on whether or not to proceed with a project based on an assessment of its viability, costs and benefits.
The process of developing a document based on research and quantification created to guide management decisions on whether or not to proceed with a project based on an assessment of its viability, costs and benefits.
Output: Feasibility study and business case
A document based on research and quantification created to guide management decisions on whether or not to proceed with a project based on an assessment of its viability, costs and benefits.
A document based on research and quantification created to guide management decisions on whether or not to proceed with a project based on an assessment of its viability, costs and benefits.
Process: Prepare project charter
The process of developing a document that includes a project scope statement, formal project objectives, and list of key stakeholders and their roles and responsibilities.
The process of developing a document that includes a project scope statement, formal project objectives, and list of key stakeholders and their roles and responsibilities.
Output: Project charter
A document that includes a project scope statement, formal project objectives, and list of key stakeholders and their roles and responsibilities.
A document that includes a project scope statement, formal project objectives, and list of key stakeholders and their roles and responsibilities.
Powered by Hackadelic Sliding Notes 1.6.5
IT Management
User Requirements Management»
Infrastructure Management»
Powered by Hackadelic Sliding Notes 1.6.5
Powered by Hackadelic Sliding Notes 1.6.5
Definition: Initiating, planning and executing the identification and organization of stakeholder needs to evaluate options and acquire a solution that achieves the project objectives.
Process: Prepare high-level user requirements
The process of creating a general description of features and functions that a system must perform to meet user needs.
The process of creating a general description of features and functions that a system must perform to meet user needs.
Output: High-level user requirements
A general description of the features and functions that a system must perform to meet user needs.
A general description of the features and functions that a system must perform to meet user needs.

Powered by Hackadelic Sliding Notes 1.6.5
Definition: Initiating, planning, executing and controlling requirements for the location and configuration of the physical components of a new system.
Process: Prepare high-level technology requirements
The process of creating a general description of capacity and performance standards required of hardware used to support a proposed system.
The process of creating a general description of capacity and performance standards required of hardware used to support a proposed system.
Output: High-level technology requirements
A general description of technology constraints, and capacity and performance information required to support a proposed system.
A general description of technology constraints, and capacity and performance information required to support a proposed system.

Process: Define existing technology architecture
The process of creating an overview of the systems, software and other technical components currently supporting users that are critical to understanding the current environment
The process of creating an overview of the systems, software and other technical components currently supporting users that are critical to understanding the current environment
Output: Existing technology architecture diagram
A graphic overview of the systems, software and other technical components currently supporting users that are critical to understanding the current environment.
A graphic overview of the systems, software and other technical components currently supporting users that are critical to understanding the current environment.
Powered by Hackadelic Sliding Notes 1.6.5
Change Management
Realization Management»
Sponsorship Management»
Powered by Hackadelic Sliding Notes 1.6.5
Powered by Hackadelic Sliding Notes 1.6.5
Definition: Initiating, planning, controlling and closing what a stakeholder does to achieve the fundamental objectives of the project.
Process: Define objectives
The process of describing what a project plans to achieve.
The process of describing what a project plans to achieve.
Powered by Hackadelic Sliding Notes 1.6.5
Definition: Initiating, planning and controlling the selection, assessment and mentoring of a project’s most senior leader.
Process: Select the executive sponsor
The process of choosing the individual with ultimate responsibility for project success.
The process of choosing the individual with ultimate responsibility for project success.
Output: Executive sponsor
The individual with primary responsibility for achieving the project’s objectives and enabling project participants through his or her leadership.
The individual with primary responsibility for achieving the project’s objectives and enabling project participants through his or her leadership.
Powered by Hackadelic Sliding Notes 1.6.5
Excerpted from Project Management for Healthcare Information Technology (HIT) by Scott Coplan and David Masuda,
Copyright © 2011 by McGraw-Hill and Companies, Inc. All rights reserved.
A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Fourth Edition, Project Management Institute, Inc., 2008
