Definition (What & Why)

Total Page:16

File Type:pdf, Size:1020Kb

Definition (What & Why)

Project Request

Requester: Date Requested:

Tracking Number:

1 PROJECT INITITATION STAGE:

1.1 Problem Definition (What) What is the problem that you want resolved? Describe the Situation.

1.2 Goals and objectives (Why) Business & Technical reasons. Why does it need to be addressed? Name the Critical Success Factors.

1.3 Timeframe required (When) When do you need the problem resolved by?

1.4 Specific Location(s) (Where) Where is this problem occurring. What are the locations that are involved in solving this problem?

1.5 Known Stakeholders (Who) Who do you think it effects, who would be interested in the project (as an recipient or politically or for personal reasons?)

1.6 Potential Solutions (How) How do you think the problem would be solved?

1.7 Sign Off: Who and What will be the approval process for this project? Is this project budgeted?

______

Date:

______Signature

Approval / Disapproval for investigation proposal:

If Disapproved, reason for decision:

Created by Staale Swift Page 1 of 3 1/9/2018 OAR File: 06c30d744845273934aef892eacb701a.doc 2 PROJECT PLANNING STAGE

2.1 Preliminary Feasibility 2.1.1 Determine if legitimate work exists before engaging other resources

2.2 Concept Briefing 2.2.1 Engagement Letter – Formal Engagement document to be used during the Planning Stage 2.2.2 Global Overview – Project Kick Off, Establish a Mission, Vision and Values Statement 2.2.3 Resource Analysis Chart – Resource commitments from both parties

2.3 Project Meeting 2.3.1 Project Charter Established –Project Organization, Meetings, Schedules, Reporting 2.3.2 Project personnel assigned and organized 2.3.3 Data Control worksheets established

2.4 Data Collection 2.4.1 Information Gathering 2.4.1.1 ID Administrators 2.4.1.2 ID Current Organization involvement 2.4.1.3 Develop Workgroups, Roles and Responsibilities 2.4.1.4 Develop Work place for project 2.4.1.5 Identify Politics 2.4.1.6 Be able to Address a strategy, structure, systems, skills, staffing, style, shared values 2.4.1.7 Develop Communication Plan 2.4.2 Business Information – Current / Future State. Conduct Recon 2.4.2.1 ID Current and Future information flows 2.4.2.2 ID Issues regarding Training, Determine experience level of Users, Support and Training 2.4.2.3 Penetrate Various Layers of management to solicit feedback 2.4.2.4 Conduct Concerns workshops at Various Layers 2.4.2.5 Conduct Business Process Re Engineering where necessary 2.4.3 Technical Information – Current / Future State. Conduct Recon 2.4.3.1 Physical Layer – LAN, Cabling and Wiring conditions for the project 2.4.3.2 Logical Layer – Electronics, WAN, Data Flow and bottleneck issues 2.4.3.3 NOS Layer – Server, Hardware, Software, Backups 2.4.3.4 Data Layer – End User Data, Client Server Situation 2.4.3.5 Application Layer –Application Current and Future State 2.4.3.6 Desktop Layer – Hardware, software, Unit Testing, Integration Testing, Roll Out, Migration 2.4.3.7 Desktop Management Layer – Asset tracking, Recon, Reporting, Software Distribution, Problems 2.4.4 Financial and Risk Issues 2.4.4.1 Review Budget Issues 2.4.4.2 Review Procurement Issues 2.4.4.3 Review Risk Management Plan 2.4.4.4 Review Expected Cost Justification Issues 2.4.4.5 Review Capital Expenditure Process to set expectations 2.4.5 Data Review 2.4.5.1 Internal review to determine if enough information is available to develop a Scope Statement. 2.4.5.2 Development of a Scope Statement ( a document that describes the situation and outlines “What” is to be done.) 2.4.5.3 Obtain Approvals for Scope Statement

Page 2 of 3 1/9/2018 2.5 Analysis, Design and Recommendations 2.5.1 A Statement of Work (SOW) is Developed. A SOW takes the scope document and tells What, When, Where, Why, Who and How. The SOW should incorporate : 2.5.1.1 Work Breakdown Structure 2.5.1.2 Analysis and Design Phase. 2.5.1.3 Plan of action and workplan 2.5.1.4 Resources Required 2.5.1.5 Bottom up estimate: cost to complete 2.5.1.6 Assumptions defined 2.5.1.7 Roles and Responsibilities 2.5.1.8 Estimated completion date 2.5.1.9 Deliverable Matrix 2.5.1.10 Milestones 2.5.1.11 Completion criteria defined 2.5.2 Analysis Documents are created 2.5.3 Design Documents are created 2.5.4 Develop a Quality plan in support of the project 2.5.5 Develop a Communications Plan in support of the project 2.5.6 Develop a Marketing Plan in support of the project 2.5.7 Develop a Course of Action 2.5.8 Develop a Project Plan using the WBS, Resources, Costs, dependencies, constraints, outside business issues impacting the project. 2.6 Recommendation Meeting 2.6.1 Schedule meetings to conduct Presentation of Analysis 2.6.2 Schedule meetings to conduct Design Reviews and approvals 2.6.3 Schedule meetings to Conduct Project Management Reviews All meetings are to inform, obtain feedback, and obtain agreement to move on to project implementation.

3 PROJECT EXECUTION

3.1 Installation and Implementation 3.1.1 Schedule meetings for Technical and Project Change Management where necessary 3.1.2 Formally Document post – installation support and service plans 3.1.3 Identify tasks and accountability in the implementation phase of the project 3.1.4 Identify tasks and accountability in the operational phase of the project 3.1.5 Coordinate Course of Action for Strategy, Skills, Staffing, Style, Systems, Structure, and Shared Values through out implementation phase of project 3.1.6 Execute project procurement and implementation activities 3.1.7 Work the Risk Plan to mitigate and reduce risks 3.1.8 Execute the Communication plan through out the project 3.1.9 Execute the Quality Plan

4 Complete and Close out

4.1 Complete 4.1.1 Close out all Risk Issues from the Risk Log 4.1.2 System Completion Checklists filled out and signed off 4.1.3 Unit Completion Checklists filled out and signed off 4.1.4 Function Completion Checklists filled out and signed off 4.1.5 Hand Off and acceptance documents are given to operational group supporting operations 4.1.6 Deliverable Acceptance documents signed 4.1.7 Project is invoiced 4.1.8 Project is paid for

4.2 30 – 90 Day Review Meeting 4.2.1 Assure Client Satisfaction and Address Outstanding Issues

Page 3 of 3 1/9/2018

Recommended publications