Lecture 2: Conceptualizing and Initializing The IT Project

1
Lecture 2 Conceptualizing and Initializing The
IT Project
2
Key areas of Project Management

• Scope Management
• Issue Management
• Cost Management
• Quality Management
• Communications Management
• Risk Management
• Change Control Management

3
Scope Management

• Project Scope Management is the process to ensure
  that the project is inclusive of all the work
  required, and only the work require, for
  successful completion.
• Primarily it is the definition and control of
  what IS and IS NOT included in the project
• This component is used to communicate
• How the scope was defined
• How the project scope will be managed
• Who will manage the scope (e.g., PM, QA)
• Change Control

4
Issue Management

• Issues are restraints to accomplishing the
  deliverables of the project.
• Issues are typically identified throughout the
  project and logged and tracked through
  resolution.
• Issues not easily resolved are escalated for
  resolution.
• In this section of the plan the following
  processes are depicted
• Where issues will be maintained and tracked
• The process for updating issues regularly
• The escalation process
• The vehicle by which team members can access
  documented issues

5
Cost Management

• The processes required to ensure the project is
  completed within the approved budget and
  includes
• Resource Planning - The physical resources
  required (people, equipment, materials) and what
  quantities are necessary for the project
• Full Time Employees, Professional Services, Cost,
  and Contingency.
• Budget
• Budget estimates
• Baseline estimates
• Project Actuals

6
Quality Management

• Quality Management is the processes that insure
  the project will meet the needs via
• Quality Planning, Quality Assurance, and Quality
  Control
• Clearly Defined Quality Performance Standards
• How those Quality and Performance Standards are
  measured and satisfied
• How Testing and Quality Assurance Processes will
  ensure standards are satisfied
• Continuous ongoing quality control

7
Communications Management

• The processes necessary to ensure timely and
  appropriate generation, collection,
  dissemination, and storage of project information
  using
• Communications planning Determining the needs
  (who needs what information, when they need it,
  and how it will be delivered)
• Information Distribution Defining who and how
  information will flow to the project stakeholders
  and the frequency
• Performance Reporting Providing project
  performance updates via status reporting.
• Define the schedule for the Project Meetings
  (Team, OSC, ESC), Status Meetings and Issues
  Meetings to be implemented

8
Risk Management

• Risk identification and mitigation strategy
• When\if new risks arise
• Risk update and tracking

9
Change Control Management

• Define how changes to the projects scope will be
  executed
• Formal change control is required for all of the
  following
• Scope Change
• Schedule changes
• Technical Specification Changes
• Training Changes
• All changes require collaboration and buy in via
  the project sponsors signature prior to
  implementation of the changes

10
Methodology

• A strategic level plan for managing and
  controlling IT projects
• A template for initiating, planning, developing
  an information system
• Recommends in support of an IT project
• phases
• deliverables
• processes
• tools
• knowledge areas
• Must be flexible and include best practices
  learned from experiences over time

11
An IT Project Methodology
12
Why Have Project Phases?

• A project should successfully pass through each
  of the project phases in order to continue on to
  the next
• Management reviews (also called phase exits or
  kill points) should occur after each phase to
  evaluate the projects progress, likely success,
  and continued compatibility with organizational
  goals

13
Phases

• Phase 1 Conceptualize and Initialize
• Phase 2 Develop the Project Charter and Detailed
  Project Plan defined in terms of projects
• scope
• schedule
• budget
• quality objectives

14
Phases continued

• Phase 3 Execute and Control the Project using
  approach such as the SDLC .
• Phase 4 Close Project
• Phase 5 Evaluate Project Success
• Post mortem by project manager and team of entire
  project
• Evaluation of team members by project manager
• Outside evaluation of project, project leader,
  and team members
• Evaluate projects organizational value

15
IT Project Management Foundation

• Project Management Processes
• Initiating processes
• Planning processes
• Executing processes
• Controlling processes
• Closing processes

• Project Objectives

16
Project Process Groups

• Initiation
• Definition and Planning
• Executing
• Controlling
• Closing

17
Initiation

• Define the need
• Return on Investment Analysis
• Make or Buy Decision
• Budget Development

18
Definition and Planning

• Define Project Scope
• Define functional requirements
• Requirements to be prioritized into business
  critical and non-business critical need
• Define technical requirements
• Risk Management Planning

19
Definition and Planning

• Resource Planning
• Work Breakdown Structure
• Project Schedule Development
• Configuration Management Plan
• Quality Assurance Plan
• Production Support Plan
• Service Level Agreement
• System Design

20
Implementation

• Training Plan
• System Build
• Quality Assurance

21
Implementation

• User Training
• Production Review
• Go Live

22
Closing

• Contractual Closeout
• Post Production Transition
• Lessons Learned

23
Application in Project Execution and Controlling

• A project schedule empowers a Project Manager to
  
• Manage the time, cost, and resources of the
  project
• Assess the progress of the project against the
  baseline
• Assess and communicate the impact of issues and
  change management
• Forecast and what-If scenarios
• Issue Management

24
(No Transcript)
25
(No Transcript)
26
(No Transcript)
27
IT Project Management Foundation

• Tools - e.g. CASE
• Infrastructure
• Organizational Infrastructure
• Project Infrastructure
• Project Environment
• Roles and Responsibilities of team members
• Processes and Controls
• Technical Infrastructure
• Project Management Knowledge Areas

28
Project Goal ?

• Install new hardware and software to improve our
  customer service to world class levels
• Respond to 95 of our customers inquiries within
  90 seconds with less than 5 callbacks about the
  same problem.

versus
29
A Really Good Goal

• Our goal is to land a man on the moon and return
  him safely by the end of the decade.
  
  

John F. Kennedy
30
Project Selection and Approval

• The IT Project Selection Process
• The Project Selection Decision
• IT project must map to organization goals
• Selection should be based on diverse measures
  such as
• tangible and intangible costs and benefits
• various levels throughout the organization