Scribd
Upload
33 views21 pages

PMC120 Systems Development Lifecycle (SDLC) Week 3

The project charter outlines a proposed project to build a distributed batch scheduler for a university research group. Key details include developing the scheduler to make use of available CPUs on the university network, with the goals of increasing efficiency and saving time and money. High-level deliverables, timelines, and stakeholders are identified. The project charter serves as authorization to begin the initiating phase.

Uploaded by

ian vannery
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
33 views21 pages

PMC120 Systems Development Lifecycle (SDLC) Week 3

The project charter outlines a proposed project to build a distributed batch scheduler for a university research group. Key details include developing the scheduler to make use of available CPUs on the university network, with the goals of increasing efficiency and saving time and money. High-level deliverables, timelines, and stakeholders are identified. The project charter serves as authorization to begin the initiating phase.

Uploaded by

ian vannery
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 21

PMC120 SDLC

Week 3 Initiation and Planning Phases


…Initiating Phase…

 Why do Projects Fail:

 https://www.youtube.com/watch?v=CTHHiBNXJ6w&t=76s
Initiating Phase…

 Involves aspect of Stakeholder and Risk Management


 Identifies the “need”
 Defines a potential new project or proposed new phase to an existing project
 Obtains formal approval which is part of the “Project Charter”
 Project Charter is a statement of the scope, objectives, and participants in a
project.
 Contain the essence of the project
 Provide a shared understanding of the project
 Act as a contract between the project sponsor, key stakeholders and the project
team
 More on the Project Charter later
…Initiating Phase…

 What do they want?


 What will we give them?
 What will it cost us to give it to them?
 What will we get in return from them?
 What is at Stake (make and brake)?
 The initiating phase is the last opportunity to terminate the project without
significant financial penalties and reputational damage
…Initiating Phase…

 Project sponsor is the person who is paying for the project


 Complete an initial stakeholder identification
 Determines those persons that are involved with the project and/or have an affect
on the project
 Identify the core stakeholders and determine what they want to achieve
 May require a Request for Proposal (RFP), Request for Tender (RFT), Request for
Quotation (RFQ), or Business Proposal
 If you cannot identify what the core stakeholders want – complete a top-down-
analysis
…Initiating Phase…

 Top-Down-Analysis
 Stakeholders know they need something but don’t know what it is
 Determine Business Objectives
 Business Activities
 Business Groups Applications/Services/System
 Each layer has “wants”, “needs”, “requirements” which drive the Desired
Outcomes and Perceived Benefits
…Initiating Phase…

 Business Objectives
 Sales, growth, market expansion, client retention
 Business Activities
 Sales, marketing, customer support, client training
 Business Groups
 Regional sales teams, online marketing, R&D, customer support
 Services
 Billing systems, databases, email, printers, internet, network file sharing
…Initiating Phase…

 Do not question Time – when do they need it by or Cost – how much are they
prepared to spend. Concentrate on the basics
 Misunderstandings and misinterpretations are project killers
…Initiating Phase…

 What will we give them?


 What will you (the PM), your office (PMO), and the core stakeholders give the
sponsor?
 Provide a general indication of how it is proposed that the project will be
implemented
 Do not include details unless asked to do so
 Keep it simple
…Initiating Phase…

 What will we give them?


 Overview of the Project
 Assumptions made about the project
 Project Constraints
 Scope Boundaries
 General list of high-level requirements
 A list of high level deliverables
 A list of high-level dates for milestones
…Initiating Phase…

 Intellectual Property Rights (IP)


 Who exactly own what?
 Depends on local, governmental laws
 Can be written into a contract under the Terms and Conditions
 Should include the sub-contractors
 Should cover existing and new IP
…Initiating Phase…

 What will it Cost us to Give it to them?


 Make a reasonable estimate of the projects approximate [Time], the approximate
[Cost] and the approximate [People] and [Resources]
 Rough Order of Magnitude (ROM)
 1 – 3 – 6 - 12 months
 2 – 5- 10 – 50 -100 thousand of dollars
…Initiating Phase…

 What will We Get in Return from Them


 Fees
 Contract Value
 Payment methods
 Payment milestones
 i.e. 5% at sign-off, 5% at completion of Detailed specification…
…Initiating Phase…

 What is at Stake?
 What is the Return on Investment (ROI)
 ROI – (Gain from Investment – Cost of Investment/Cost of Investment)
 What strategic value will this project provide?
 What are the tangible benefits?
 What are the benefits to other projects?
 What is the likelihood of success?
 What is the risks involved?
 What are the alternatives available?
 Is this a rational decision or an emotional one?
…Initiating Phase…

 What is at Stake?
 Is there a market demand?
 Is this project statutory, legal?
 What is the competitive advantage
 Is there a productivity or process improvement?
…Initiating Phase…

 Outputs - Documentation
 Customer Requirements
 Project Charter
 Stakeholder Management Plan
 Detailed Specifications
 Non-detailed Project Schedule
 Non-detailed Architectural Design
…Initiating Phase…

 Output – Customer Requirements


 You should at this point have a clear picture of the customer wants and needs
 It is common for the customer requirements to change and evolve over the
duration of the project
…Initiating Phase…

 Output: Project Charter


 Used to obtain official authorization to commence the project
 Signed off by sponsor and/or stakeholders
 Includes:
 Project Identification
 Project Authorization
 Project Managers name
 Key Stakeholders
 Project Overview
 Project Scope Boundaries
…Initiating Phase…

 Project Charter includes:  Project Charter includes:


 Project Assumptions  High-Level Project Milestones
 Project Constraints  Contract Master Schedule
 Project Priorities  Costs Estimates
 High-Level Risks  Payment Milestones/Payment Schedule
 High-Level Project Requirements  Tangible Measures
 High-Level Project Deliverables  Project Acceptance Criteria
 Intellectual Property Rights  Project Closure & Termination
 High-Level Property Rights  Additional Information
…Initiating Phase…

 Output: Risk and Issues Register


 Output: Detailed Specifications
 Output: Stakeholder Management Plan
In Class Assignment

 Project Charter example


 The project is to build a distributed batch scheduler to be used by a
University research group. A batch system allows users to submit the
programs they would like to run, and then schedules the jobs to run in the
background of various computers on the network. In this way, the use of
available CPUs can be increased, saving time and money.

You might also like