Write a project management plan. we have a template and project description. we need to edit the

Fantastic news! We've Found the answer you've been seeking!

Question:

Write a project management plan. we have a template and project description. we need to edit the template(table of contents) with our own ideas.

CPSC 8820-01 Project Management Plan

Your Unique Company Name

Street Address

City, State, Zip Code

Instruction for Completing the Project Plan

This template is used to create a project plan. The template is found on the following pages. The following instructions are to be followed:

At a minimum, all sections must be addressed. Additional information may be added as needed. If something is not applicable, just state “not applicable”. If the information requested is located in another document, just add a pointer to that document.

When creating the project plan, important information that needs to be included may not yet be available at the time the plan is submitted. If certain information is not available at the time of submittal, indicate the planned availability date if known.

The project plan for projects should be updated when there is a need to document changes and/or additions in information and communicate it to the project team. It is left to the discretion of the project manager based on the importance of the change as to when the project plan is updated.

Once starting working on the project, this instruction and all annotations should be removed and replaced with your own plan.

Always update the “Table of Contents” after each document edit is completed

To avoid any plagiarism confusion, it is required that you change all these descriptions to your unique specifications i.e., what you did for your project, not just text description.

Table of Contents

1. Executive Summary. 2

2. Project Management Approach. 2

3. Project Scope. 2

4. Milestone List 2

5. Schedule Baseline and Work Breakdown Structure. 3

6. Change Management Plan. 3

7. Communications Management Plan. 3

8. Cost Management Plan. 5

9. Procurement Management Plan. 6

10. Project Scope Management Plan. 6

11. Schedule Management Plan. 6

12. Quality Management Plan. 6

13. Risk Management Plan. 7

13.1 Risk Register 7

14. Staffing Management Plan. 7

14.1 Resource Calendar 7

15. Cost Baseline. 7

16. Quality Baseline. 8

17. Sponsor Acceptance. 8

1.Executive Summary

The Introduction provides a high level overview of the project and what is included in this Project Management Plan. This should include a high level description of the project and describe the projects deliverables and benefits. Excessive detail is not necessary in this section as the other sections of the project plan will include this information. This section should provide a summarized framework of the project and its purpose.

This section should do the following:

Describe the problem.

Describe the solution.

State objectives, i.e., why we are doing/want to do it.

Summary the economics for the company and customer.

Identify any key assumption, e.g., about project, competition.

Identify any key constrains, e.g., applicable standards, market window.

Identify risks and probable impacts.

Make the support request absolute clear.

Make a recommendation/request.

It is assumed that the rest of document clearly supports the statement made here. Remember that executive summary speak the language of business, i.e., customers and money.

2.Project Management Approach

This section is where you outline the overall management approach for the project. This section should describe, in general terms, the roles and authority of project team members. It should also include which organizations will provide resources for the project and any resource constraints or limitations. If there are any decisions which must be made by specific individuals—for example authorizing additional funding by the project sponsor—this should also be stated here. It should be written as an Executive Summary for the Project Management Plan.

3.Project Scope

State the scope of the project in this section. The scope statement from the project charter should be used as a starting point; however, the project plan needs to include a much more detailed scope than the charter. This detail should include what the project does and does not include. The more detail included in this section, the better the product. This will help to clarify what is included in the project and help to avoid any confusion from project team members and stakeholders.

4.Milestone List

Provide a summary list of milestones including dates for each milestone. Include an introductory paragraph in this section which provides some insight to the major milestones. This section should also mention or discuss actions taken if any changes to the milestones or delivery dates are required.

The below chart lists the major milestones for the XYZ Project.

Milestone	Description	Date
Complete Requirements Gathering	All requirements for XYZ must be determined to base design upon	2/28/xx
Complete XYZ Design	This is the theoretical design for the software and its functionality	5/31/xx
Complete XYZ Coding	All coding completed resulting in software prototype	7/31/xx
Complete XYZ Testing and Debugging	All functionality tested and all identified errors corrected	8/31/xx
Complete Transition of XYZ to TSI Production	Completed software and documentation transitioned to operations group to begin production	11/30/xx

5.Schedule Baseline and Work Breakdown Structure

This section should discuss the WBS, WBS Dictionary, and Schedule baseline and how they will be used in managing the project’s scope. The WBS provides the work packages to be performed for the completion of the project. The WBS Dictionary defines the work packages. The schedule baseline provides a reference point for managing project progress as it pertains to schedule and timeline. The schedule baseline and work breakdown structure (WBS) should be created in Microsoft Project. The WBS can be exported from the MS Project file.

6.Change Management Plan

This section should describe your change control process. Ideally, this process will be some type of organizational standard which is repeatable and done on most or all projects when a change is necessary. Changes to any project must be carefully considered and the impact of the change must be clear in order to make any type of approval decisions. Many organizations have change control boards (CCBs) which review proposed changes and either approve or deny them. This is an effective way to provide oversight and ensure adequate feedback and review of the change is obtained. This section should also identify who has approval authority for changes to the project, who submits the changes, how they are tracked and monitored.

For complex or large projects the Change Management Plan may be included as an appendix to the Project Management Plan or as a separate, stand-alone document. We have a detailed Change Management Plan template available on our website.

7.Communications Management Plan

The purpose of the Communications Management Plan is to define the communication requirements for the project and how information will be distributed to ensure project success. You should give considerable thought to how you want to manage communications on every project. By having a solid communications management approach you’ll find that many project management problems can be avoided. In this section you should provide an overview of your communications management approach. Generally, the Communications Management Plan defines the following:

Communication requirements based on roles

What information will be communicated

How the information will be communicated

When will information be distributed

Who does the communication

Who receives the communication

Communications conduct

For larger and more complex projects, the Communications Management Plan may be included as an appendix or separate document apart from the Project Management Plan. We have a detailed Communications Management Plan template available on our website.

The Communications sample Matrix can be used as the guide for what information to communicate, who is to do the communicating, when to communicate it, and to whom to communicate.

Communication Type	Description	Frequency	Format	Participants/ Distribution	Deliverable	Owner
Weekly Status Report	Email summary of project status	Weekly	Email	Project Sponsor, Team and Stakeholders	Status Report	Project Manager
Weekly Project Team Meeting	Meeting to review action register and status	Weekly	In Person	Project Team	Updated Action Register	Project Manager
Project Monthly Review (PMR)	Present metrics and status to team and sponsor	Monthly	In Person	Project Sponsor, Team, and Stakeholders	Status and Metric Presentation	Project Manager
Project Gate Reviews	Present closeout of project phases and kickoff next phase	As Needed	In Person	Project Sponsor, Team and Stakeholders	Phase completion report and phase kickoff	Project Manager
Technical Design Review	Review of any technical designs or work associated with the project	As Needed	In Person	Project Team	Technical Design Package	Project Manager

8.Cost Management Plan

The Cost Management Plan clearly defines how the costs on a project will be managed throughout the project’s lifecycle. It sets the format and standards by which the project costs are measured, reported, and controlled. Working within the cost management guidelines is imperative for all project team members to ensure successful completion of the project. These guidelines may include which level of the WBS cost accounts will be created in and the establishment of acceptable variances. The Cost Management Plan:

Identifies who is responsible for managing costs

Identifies who has the authority to approve changes to the project or its budget

How cost performance is quantitatively measured and reported upon

Report formats, frequency and to whom they are presented

For complex or large projects the Cost Management Plan may be included as an appendix to the Project Management Plan or as a separate, stand-alone document. We have a detailed Cost Management Plan template available on our website.

9.Procurement Management Plan

The Procurement Management Plan should be defined enough to clearly identify the necessary steps and responsibilities for procurement from the beginning to the end of a project. The project manager must ensure that the plan facilitates the successful completion of the project and does not become an overwhelming task in itself to manage. The project manager will work with the project team, contracts/purchasing department, and other key players to manage the procurement activities.

For larger projects or projects with more complicated procurement management requirements, you can include the Procurement Management Plan as a separate document apart from the Project Management Plan. We have a detailed Procurement Management Plan available on our website.

10.Project Scope Management Plan

It is important that the approach to managing the projects’ scope be clearly defined and documented in detail. Failure to clearly establish and communicate project scope can result in delays, unnecessary work, failure to achieve deliverables, cost overruns, or other unintended consequences. This section provides a summary of the Scope Management Plan in which it addresses the following:

Who has authority and responsibility for scope management

How the scope is defined (i.e. Scope Statement, WBS, WBS Dictionary, Statement of Work, etc.)

How the scope is measured and verified (i.e. Quality Checklists, Scope Baseline, Work Performance Measurements, etc.)

The scope change process (who initiates, who authorizes, etc.)

Who is responsible for accepting the final project deliverable and approves acceptance of project scope

We have a detailed Scope Management Plan available on our website which can be included as an appendix to the Project Management Plan for larger or more complex projects. Be sure to review it and determine if it's necessary for managing your project.

11.Schedule Management Plan

This section provides a general framework for the approach which will be taken to create the project schedule. Effective schedule management is necessary for ensuring tasks are completed on time, resources are allocated appropriately, and to help measure project performance. This section should include discussion of the scheduling tool/format, schedule milestones, and schedule development roles and responsibilities.

Be sure to check out the detailed Schedule Management Plan available on our website. The separate Schedule Management Plan is suitable for larger projects or projects where the schedule management is more formalized.

12.Quality Management Plan

This section discusses how quality management will be used to ensure that the deliverables for the project meet a formally established standard of acceptance. All project deliverables should be defined in order to provide a foundation and understanding of the tasks at hand and what work must be planned. Quality management is the process by which the organization not only completes the work, but completes the work to an acceptable standard. Without a thorough Quality Management Plan, work may be completed in a substandard or unacceptable manner. This section should include quality roles and responsibilities, quality control, quality assurance, and quality monitoring.

For larger or more complex projects, the Quality Management Plan may be included as an appendix or separate document. A detailed Quality Management Plan is available for use on our website.

13.Risk Management Plan

This section provides a general description for the approach taken to identify and manage the risks associated with the project. It should be a short paragraph or two summarizing the approach to risk management on this project.

Since risk management is a science in itself, we have many risk management templates available on our website. Look for the detailed Risk Management Plan, Risk Register along with templates for performing a risk assessment meeting.

13.1 Risk Register

The Risk Register for this project is provided in Appendix x, Risk Register.

14.Staffing Management Plan

Discuss how you plan to staff the project. This section should include discussion on matrixed or projectized organizational structure depending on which is being used for this project. This section should also include how resources will be procured and managed as well as the key resources needed for the project.

14.1Resource Calendar

Include a Resource Calendar as part of your project plan. The resource calendar identifies key resources needed for the project and the times/durations they'll be needed. Some resources may be needed for the entire length of the project while others may only be required for a portion of the project. This information must be agreed to by the Project Sponsor and Functional Managers prior to beginning the project.

15.Cost Baseline

This section contains the cost baseline for the project upon which cost management will be based. The project will use earned value metrics to track and manage costs and the cost baseline provides the basis for the tracking, reporting, and management of costs.

The sample cost baseline for the XYZ project includes all budgeted costs for the successful completion of the project.

16.Quality Baseline

This section should include the quality baseline for the project. The purpose of this baseline is to provide a basis for ensuring that quality can be measured to determine if acceptable quality levels have been achieved. It is important for all projects to clearly define and communicate quality standards and the quality baseline serves this purpose.

The XYZ Project must meet the sample quality standards established in the quality baseline. The quality baseline is the baseline which provides the acceptable quality levels of the XYZ Project. The software must meet or exceed the quality baseline values in order to achieve success.

project Description:

Aiming at the lucrative luxury automobile market, and of course, superb financial benefit from continue increasing sales of luxury cars in the United State, an international company is planning to create a new Lexus dealership that is very similar to an existing Lexus dealer in Schaumburg, Illinois, and plan to expand few more in next few months. As part of required support function, Our company is in a short list to compete and hope to win a final database contract that will be used to support this effort. Since this is a major but short notice project, the monetary award is well above market price, and this opportunity provide a critical entry point to doing business with this international company, our company need to demonstrate the quality of your products and get this account to survive. The customer is requesting that we provide detailed relational DB requirements documentation to be reviewed by their team as soon as possible.

Using Woodfield Lexus (http://www.woodfieldlexus.com/) as their role model in the region, the website will give your team a summary of all functions/services provided by the Woodfield Lexus. And based on these info, their initial operation needs are as follows:

To be able to help support the adventure, this new car dealership, minimally, need to provide exactly what Woodfield Lexus has offer to their targeted customers.

To promote this new organization and associated dealership sales programs, continue public promotion to solicit future customers from public and private sectors will also need to be planned and tracked.

A small army of employees (marketing, sales, mechanical, etc) will be recruited, hired and trained, thus need to be planned and tracked as well.

Special financial arrangement (i.e., 5-15% discounts for selected models) can be made to all buying customers, but credit check will be required.

Your team will be responsible to provide this DB requirements and design document in the time frame we have. The template should be used and requirement and design review will be scheduled accordingly (see section 3). You will have TBD minutes slot for your presentation. The document and presentation materials must be emailed to their representative one week before scheduled review meeting as well.

Customer info and Inputs

After requirement review and discussion with customers, we will need to follow up to further clarify our requirement specification if any and customer will likely want us to combine it with a more detailed design section within our requirement documentation.

The following info are provided by customer.

Depend on your proposal, a single or multiple database can be used for entire organization (i.e. DB will be used to plan and track ALL inventory, sales events/schedule, employees/salary, customers/services, and ALL associated activities.

The initial offering (targeted 6/2017) will cover Chicago city in Illinois (note: plan to expand to Madison-Wisconsin and Indianapolis-Indiana soon too). The promotion campaign has already started in this city and states.

It is expected to have 3,500 customers to visit the web site per week for the next 3 months, so performance/database availability (24/7) is very important to the company. Online selection/purchase is highly expected when the website is visited.

Each employee and buyer will have a login to check their personal account/activities.

The accuracy and integrity of DB must be maintained, the access of the DB must be secured as well.

To insure the integrity of the database, the company plan to have a weekly routine maintenance run to fix and correct any DB issues. This is scheduled for every Sunday 10PM to 6AM central time. Daily DB maintenance and backup, can only be performed between 1AM to 3AM central times.

To insure 24/7 donation/service view and access, the customer want to have a duplex system (i.e. mirror systems and can be switched in less then 15 seconds, so all data must be updated in real time and in-sync all the time. To handle fail over case, the system must support at least 60 seconds worth of data in temporary memory space. This is estimated as 200 visitors/users and their transient state info.

The Web portal and frond-end Web user interface will be provided by xyz MultiMedia Company, but all the data will be provided to them by interface with our database. They will be using Java for web application, real time DB access will be written using C and C++. Network and internet bandwidth will also be provided by xyz, and shall not be a problem for Database access needs.

As a project manager, working with your end user, management, development and test teams, based on the project management principles, study and start up a project plan that your will be used to present and manage this feature/project. Mid-term reviews and Final Project Review will be scheduled per syllabus.

8845 Class Team Action items:

As a Database Feature System Engineer and Development Team, working with your end users, Project Manager and Feature Test teams, study and start up a project development plan that your will be used to present and manage this feature/project.

Write requirement and design doc to reflect above info, the customer would like to review a more detailed database requirement and design specification. The database must provide capabilities to support application such as retrieving/adding/deleting/updating inventory, employee, visitors/Users, Customers, and different kind of service data. System security, data integrity audit, routine backup, fault recovery, system update and other associated business and maintenance activities must also be considered to support customer’s day-to-day database applications.

Please focus on the following section in requirement document:

For section 1 – For our exercise, give high level view of what feature is about.

For section 2 – focus on data model, data information flow, user interface can be used as starting point, but what are those data and what happen to those data as your users move from one state to another state and where are the data come from and go. It will be easier to fill in other subsection once this is done. Example: Need to look at how "customer data" "service data" ...... in the database will be used by web application. e.g., when customer visit the web site and click the different service icon: a query is send and retrieve associated part of the database and pass the info to web application for display ... e.t. c. Need to consider all different kind of usage, thus different combination of customer data query, security check/blocking, data update, data delete , insert new service data , remove service, .............etc.

For section 3 - This is supposedly the "heart" of the requirement document (e.g., why we call this a "requirement" document. As example shown in the template, requirement should have the following format, or something like it. As you can also see in the following examples, you should be able to convert your write-up into many, many requirements (must have at least 25 of them :-).

For each requirement, please use the following SMART criteria as guidelines (https://en.wikipedia.org/wiki/SMART_criteria):

Specific – target a specific area for improvement.

Measurable – quantify or at least suggest an indicator of progress.

Achievable – specify what will be accomplished

Realistic – state what results can realistically be achieved, given available resources.

Time-related – specify when the result(s) can be achieved

Also in general, the users should be able to add, update, or delete any field(s), record(s) or table(s) as needed.

Sample Requirements:

Note: these are samples, to avoid any plagiarism confusion from others, please update them to your unique specification as needed, i.e., please specify what information are needed to support your requirement.

(Your Name)

Add, update or delete car model (e.g., ES300H, ES 350, GS 350, RX350,… etc) and associated info (please specify what info should be tracked e.g., vendor, invoice number/price/lot/date, sales, special promotion, clearance).

Implementation: Mandatory or Optional depend on the needs.

(Your Name)

Add, update or delete car Maker (e.g., Lexus, Acura, Audi, BMW …etc) and associated info (please specify what info should be tracked e.g., invoice number/price/lot/date, sales, and special promotion).

Implementation: Mandatory

(Your Name)

Add, update or delete new service/promotion and associated info (e.g., free lift time car wash with new car purchase, special discount for 20,000 miles service …)

Implementation: Mandatory

< Company Name-Maint-000700 v1.0> (Your Name)

The feature must support an automated, customer schedulable weekly

full DB backup capabilities.

Implementation: Mandatory

Example: Full DB backup every Monday at 1 AM.

For design section in the document, it is up to you how you want to organize this section. It could be one design unit that covers every requirement, or you could have one design unit to cover customer database requirements, one for feature, and one for employee …….. Etc. In this section, please

apply/incorporate as many theories, ER/EER model(s), schema, normal forms, hashing, transaction, concurrency, design process ……etc. as you can and explain why you choose each for your design. Prototype each of your design unit as well. Please note that the prototype could be pseudo or actual coding as needed. The database constraints, if any, should also be specified in the design.

Please note that section 1 should lead to section 2, section 2 should lead to section 3, and section 3 should lead to section 4.

The requirement (sections 1, 2, 3, 7, 8, 9, 10) document and presentation materials must be emailed to their representatives one week before the requirement review/presentation date.

The Design (sections 4, 5, 6) document and presentation materials must be emailed to their representatives one week before the design review/presentation date.

The final Product Demo (using MYSQL workbench) will be scheduled on the last day of the class.