Planning PRE APPROVAL pt-1
Main steps
- Identify and initiate project
- Perform a feasibility analysis
- Planning (or Inception) phase outcome: A system request based on a business need or opportunity
- Plan possible results: whether it is accepted or denied
Project Idenification
What are project ideas driven by?
- Business needs ether by the businesspeople or IT team or both
- Some kind of pain for example low stock price ect...
- When a company realises a way to have a competitive edge
Project Sponsor
What is a project sponsor
This is a person that wants to see the project succeed, and has the ability to move it farward
Who might it be
- Usually, this is a member of IT or a business person
Business Values
Tangible Values
- Something that can be measured
- 2% increase in revenue
Intangible Values
- Something has changed however you cannot put a exact value on it
- Better customer service, happier staff, a new products impact
System Request
This is a document that details the advantages of creating a new system
This document should contain a feasibility check and risk assessment
As well as:
Example
Feasibility and Risk Analysis
- What are the risks?
- How can said risks be overcome, or minimise them?
Technical Feasibility
(Can we build it?)
Are the analysts familiar with the topic?
Are you familiar with the technology?
How large is the project?
How hard is it to inter-grate?
Economic Feasibility
(Should we build it money wise?)
What are the expenses?
What will bring in the money?
How much is it worth?
Costs and Benefits table
Organisational Feasibility
(Will the user use it?)
Is the project beneficial to the companies goal?
Will the user like it?
Do a stakeholder analysis:
- Key people
- Organisational management
- System users
- Others
Feasibility and Risk Assessment
Risk assessment example
Feasibility report example
This report such describe:
- Current business process
- Suggested improvement
- How this improvement will improve things
- This should be as much tangible data as possible
Planning