Confidential and Proprietary Information

Total Page:16

File Type:pdf, Size:1020Kb

Confidential and Proprietary Information

Fundamentals of Technology Project Management Project Plan Template Project Name Project Plan

PROJECT NAME

Confidential and Proprietary Information This document contains information that is proprietary to . Transmittal, receipt, or possession of this document does not express license, or imply rights to use, sell, design, manufacture, or to have manufactured, any product, concept, or service from this information. No reproduction, publication, or disclosure of this information, in whole or in part, electronic or otherwise, shall be made without prior written authorization of an officer of Authorized transfer of this document from the custody and control of constitutes a loan for limited purpose(s), and this document must be returned to upon request, and in all events, upon completion of the purpose(s) of the loan.

Page 1 of 9 Created by "Author" Fundamentals of Technology Project Management Project Plan Template Project Name

Document Change Log

Prepared By Title Date Version

Revisions

Modified By Reason Date Version

Page 2 of 9 Created by "Author" Fundamentals of Technology Project Management Project Plan Template Project Name Table of Contents

1. Introduction...... 4 2. Project Definition Overview...... 4 3. Changes Since Project Definition Was Approved...... 4 4. Staffing Plan...... 4 5. Development Environment...... 4 6. High-Level Schedule...... 4 7. Deliverables and Milestones...... 4 8. Functional Requirements...... 5 9. Technical Requirements...... 5 10. Decision Support System (DSS) Plan...... 5 11. Quality Assurance (QA) Plan...... 5 12. Communications Plan...... 5 13. Deployment Plan...... 5 14. Operations Plan...... 5 15. Training Plan...... 5 16. Risk Management Plan...... 5 17. Measurement Plan...... 5 18. Client Acceptance Criteria...... 6 19. Project Plan Approval...... 6

Page 3 of 9 Created by "Author" Fundamentals of Technology Project Management Project Plan Template Project Name

1. Introduction The project name is Café IT–Build IT and Café IT is the name of the coffee internet shop located in the heart of LA City in CA State. Our group name is Café IT –Build IT, in this project we care about all the IT and technical staff in this coffee internet shop.

2. Project Definition Overview ~$oject_DefinitionHINDZ_draft_3.doc

3. Changes Since Project Definition Was Approved

3.1. The Problem: -Technical service café IT contains certain conditions in addition to customer requests. -area 1: Need always to have a new set of games. -area 2: Computer needs to be a variety of programmers and specific for this purpose. -Internet speed must be to serve the high end. -our client looks to be the "No. 1" in coffee shop in the Los Angeles downtown. -Technical should serve this goal by watch quality and price of competing for others all the time. -Provision of high quality and at the same time maintains the low price. -Harness the technology in Café IT to Sell the largest number of the membership of the café IT and Sell the largest number of hours online.

3.2. The Solution -Providing technical allow competition, through the provision of appropriate high speed internet to play. -The Games also provide modern developed that will attract the public, which may not be available in their homes. -Building official page for the project shows the services provided by the most potential. -Connecting the site to Google and yahoo because search engines that cause an increase in customers. -Lower prices for this technical reason to attract customers.

Page 4 of 9 Created by "Author" Fundamentals of Technology Project Management Project Plan Template Project Name

3.3. Time and Costs:

Work on this project will start in 01- 14-08 and end in 03-16-08. As well as the initial budget and schedule estimated and described in this project in schedule document and budget document.

4. Staffing Plan See it in Staffing Plan Document

5. Development Environment http://home.comcast.net/~todd_lara_smith/Marathon03.html#

6. High-Level Schedule Assignment Starting Finishing Name Roles Position Date Date Floor 01/14/08 01/18/08 Kevin Project Working Duffy leader representative Wall 01/14/08 01/20/08 Archie Project Project River Assistant Consultant Painting 01/21/08 01/23/08 Cooler Project Project Knight Assistant Consultant Windows 01/21/08 01/22/08 Jack Project Project Chen Manager specialist Tables 01/23/08 01/23/08 Jessie Advisor Client Miller representative Chairs 01/23/08 01/23/08 Page Bell Advisor Client Representative Coffee 01/24/08 01/25/08 Monica Quality QA consulting Machine Phuong Assurance Manager Electricity 01/26/08 01/31/08 Cindy Technical Electricity Dodge Manager representative department Computers 02/01/08 02/22/08 Scott Computer Computer Wood Sponsor CEO TVs 02/23/08/ 03/15/08 Edwin Business Business Drood Manager Representative

7. Deliverables and Milestones Milestone Date Status Responsible Issue/Comments Initiating

Page 5 of 9 Created by "Author" Fundamentals of Technology Project Management Project Plan Template Project Name

Project Manager 01/14/08 Completed Joe determined/assigned Business case 01/18/08 Completed Erica created Project charter 01/22/08 Completed Edwin signed Planning Project kickoff 01/12/08 Completed Tiger Went well meeting held Project contract 01/12/08 Completed Erica signed Scope statement 01/15/08 Completed Haley completed List of risks 01/17/08 Completed Norris Reviewed with completed sponsor and team Schedule and cost 01/21/08 Completed Todd baseline completed Executing Coffee shop 01/25/08 Completed Hind blueprint completed TV area completed 01/26/08 Completed Todd Internet area 01/27/08 Completed Todd completed Print area completed 01/28/08 Completed Hind User inputs collected 01/31/08 Completed Jessie User requests 02/05/08 Completed Michael completed Internet testing 02/10/08 Completed Scott completed TV testing 02/18/08 Completed Edwin completed Electricity testing 02/26/08 Completed Cindy completed Monitoring and Controlling Status reports Every Friday All Closing Final project 03/06/08 Edison presentation Sponsor sign-off on 03/07/08 Archie project completion Final project report 03/12/08 Page completed Project hand off 03/14/08 All

Page 6 of 9 Created by "Author" Fundamentals of Technology Project Management Project Plan Template Project Name

8. Functional Requirements See it in Functional Requirements Document

9. Technical Requirements See it in Technical Requirements Document

10. Decision Support System (DSS) Plan

11. Quality Assurance (QA) Plan See it in Quality Assurance Plan Document

12. Communications Plan 017 Communication Plan.doc

13. Deployment Plan See it in Deployment Plan Document

14. Operations Plan See it in Operations Plan Document

15. Training Plan Training Name Role Position Contact Information Coffee Edison Human HR president [email protected] Makers Chen Resource Leader Computer Tiger Technical IT [email protected] Developer Woods Manager representative Coding Woody QA advisor IT Manager [email protected] Testers Allen Shop Yale Sponsor Business CEO [email protected] manager Fonda

16. Risk Management Plan

Risk Categories Budget and Roles and Methodology Schedule Responsibilities Errors in Time Due date: Manager: Joe Add more estimating time 03/16/08 Fleming workers or

Page 7 of 9 Created by "Author" Fundamentals of Technology Project Management Project Plan Template Project Name or resource Cost: 40,000$ more resource availability to finish it Absence of Human 2,000$ HR leader: Find a person leadership Resource Michael Chen who are able to handle his job Lack of Communication 1,000$ Group leader: Build up a good consultation Erica Bell relationship by with key communicating stakeholders them with good manners and good conversation skills Poor attitude Quality 5,000$ QA leader: Rang up toward quality Kevin Faue employee’s paycheck

17. Measurement Plan

18. Client Acceptance Criteria Our goal is to product a project, which must be acceptable as "complete" by the client. This project is to complete with 2 months for no more then $40,000. The Client representatives has responsibilities to supervise the project, and check out its design, inputs, financial status, benefits, development, investment, test and deployment. If the project does not meet their requirement, like takes a little longer to complete or costs a little more than planned, the client will still accept it as a success if it has a good quality, a good potential in investment and helps the client’s benefits on rise.

19. Project Plan Approval

Client Sponsor: Signature: Print Name: Title: Date: Signature: Print Name: Sponsor: Title: Date:

Signature:

Page 8 of 9 Created by "Author" Fundamentals of Technology Project Management Project Plan Template Project Name

Print Name:

Project Manager: Title: Date:

Page 9 of 9 Created by "Author"

Recommended publications