TPP 5 - Consolidated Project Management Plan (Group)

TTP-5 Consolidated Project Management Plan (Team project)

Please be sure to read the Team Contribution Assessment and Grading of Team Assignments and the Project Documentation Requirements sections of the ITP Master Document.

Assignment for the TTP-5 Project Deliverable

Review your previous deliverables assignments and the assignments from the other teams in the Shared Learning Environment Discussions.

Prepare a consolidated Project Management Plan / Proposal (PMP) that consolidates and summarizes each of the ITP deliverables.

The final deliverable assignment posting should include a project plan, a project schedule and a project presentation.

This assignment has three parts.

Part 1. Project Plan in Microsoft Word

Review your previous deliverables assignments and the assignments from the other teams in the Shared Learning Environment Discussions.

Prepare a consolidated Project Management Plan / Proposal (PMP) that consolidates and summarizes each of the ITP deliverables. This will be a complete, consolidated project plan document (in a format/structure from the textbook, from www.pmi.org, or from other valid research) including all relevant project information and all information from previous ITP deliverable documents.

All the ITP assignments from this semester should be updated and improved based on learning through the semester from instructor comments, sharing the projects of the other teams, additional text readings and additional research, and other lessons learned. You may use any number of features such as the updated assignments, appendices or embedded documents, but all appendices and embedded documents should reflect the changes you have experienced through the semester.

Please note that the full documents should not be part of the main body of the Project Plan. They are supporting documents only. For example, one embedded document or appendix should be an updated Risk Register in Excel for all major tasks and at least 2 sub-tasks. Another appendix should be an updated and expanded version of your project charter that summarizes the project, given what you know now. For instance, as but one example, any changes in project schedule, costs, and scope since the original draft of the charter should now be reflected in the updated charter.

The Consolidated Project Plan consolidates, discusses and summarizes each of the ITP deliverables plus additional information that would be included in a project management plan. The consolidated plan, with the exception of the Microsoft Project file, must summarize each of the ITP documents (schedule, major resources, major risks, cost, etc.) in the text of the document. The final consolidated plan should discuss what the project is, what is required to meet the needs of the bakery, how information was gathered and presented, and information that will help the company and the client or executive sponsor). Documents to support the SUMMARY should be added as Appendices - either in full or embedded (preferable). Do not use links to external files as this will fail to work as expected!

The Consolidated Project Plan must include at least a paragraph that describes which project documents/assignments were changed, updated and/or improved, how, and why. If, for example, the

team made changes to the Resources, the team might indicate that they saw another team that included a resource that had not been considered yet. This paragraph (or more) is mandatory!

The consolidated plan should include references used (with appropriate citations) to gather the information.

Some sections to consider for inclusion in the Consolidated Project Plan are:

• A title page

• The executive summary (with appropriate changes) of the project proposal and plan.

• The scope, cost and schedule (early in the document!)

• Business requirements for the project and system, and reason for undertaking the project (problem statement) should be included.

• Clear and complete scope statement should be included; what is IN scope and what is out of scope.

• Objectives, constraints, and assumptions should be included.

• Participants (project team AND stakeholders) along with their roles should be listed.

• Project background should be provided.

• Technical and PM approach/strategy should be described.

• Outsourcing/contracting should be addressed

• Benefits and value to the client (note: this does not mean costs or budget) should be detailed.

• Rough order of magnitude (ROM) estimate of costs and required project budget should be included based on your own cost estimate.

• ROM estimate of total time required to complete the project and project completion date should be included based on your Project schedule.

• A summary-level Gantt chart with a few major bars might be a useful, though optional, addition. However, do not include a copy of a full MS Project Gantt chart that is so detailed that it is unreadable.

• A conclusion paragraph should be included, briefly summarizing the project and requesting approval to proceed with the project.

As an example, PMI recommends the following sections in a project management plan:

• Purpose/background/approach

• Goals/objectives

• Scope

• Deliverables

• Constraints/assumptions

• Related projects/critical dependencies

• Schedule and milestones

• Budget/cost-benefit assessment

• Risk assessment

• WBS

• Quality management approach

• Tools and techniques to be used

• Resource estimates

• Standards

• Change and control procedures

• Roles/responsibilities

• Work plan

• Team contact directory

• Approval sign-off form

There are several other good templates and formats available. Please be sure to credit the source of your Project Plan structure or format.

Part 2. Project Schedule in Microsoft Project

This will be an updated Microsoft Project schedule with updated durations, dependencies, resources, and costs. The updates are a result from the weekly ITP assignments. The schedule should be updated based on lessons learned, instructor's comments, improvements resulting from sharing and looking at the work of other teams.

Part 3. Project Presentation in Microsoft PowerPoint

This will be a Microsoft PowerPoint presentation (no more than 10 slides) that provides a high-level executive-level summary of your project proposal for the major stakeholder(s). The slides should be prepared and formatted as though they will be presented face-to-face in a Conference room with a projector.

• The presentation should open with a discussion of scope, cost, and schedule.

• This presentation will be a decision presentation, not merely an information presentation. The PowerPoint slides should NOT be overly full of text.

• Length should be appropriate to purpose and audience (approx. 8-10 slides).

• The slides should not be too full of text or bullets, and should use large enough text for readability

• Note: Please do not use timed automatic slide transitions for this presentation.

• You may organize and format your presentation in any way that seems most effective and appropriate to the purpose.

• Graphics may be used but should be meaningful, useful, and not distracting or gratuitous.

The consolidated project plan document and project plan presentation should include:

• Enough detail should be provided to allow the stakeholder(s) to make a go/no-go decision on whether or not the proposal is acceptable to begin implementing the project plan, designing and installing the IT project.

• MAKE A RECOMMENDATION!

• A title page or cover sheet that includes the contributors. This should not be a stand-alone file but should simply be the first page of another Word document (e.g., the Charter) that you are submitting.

Make sure that all your documents are consistent and do not contradict each other. (For instance, the schedule and costs as presented in the Microsoft PowerPoint presentation, the Microsoft Project schedule, the charter and sections of the Consolidated Plan should agree; the narrative in the Plan and the Microsoft PowerPoint presentation should agree with each other; and so forth.)

Also make sure that any problems with previous ITP deliverables have been corrected before incorporating them in your TTP-5 work, and make sure that any comments from the instructor regarding previous ITP deliverables have been corrected and updated. PLEASE include a paragraph that discusses what has been changed and updated (previous assignments that are now part of the project plan), what changed and why. This may be the final paragraph or a discussion included as an appendix, but I would like to see what is different from when you did the original assignment during the semester.

Please post the THREE final ITP documents (.mpp, .ppt, .doc) in the Assignment Area and in the Shared Learning Environment Discussion Forum

To summarize:

The plan should be in the structure of a project management plan that you should find from a credible source through your research. PMI, for example, is a credible source. Your plan should include updated documents/assignments, as embedded files, appendices, or any other method that works well for you and your team. Please include a discussion of what has been updated and why, even thought is not a normal part of a Project Management Plan. This might include what you have learned through additional readings and sources, what you have learned from sharing and looking at the other teams' efforts, and what you have changed as a result of my feedback and comments. This helps me focus in on the improvements you have made over the semester. The final assignment includes a PowerPoint presentation that leads the client to a go-no go decision. It should be a high level presentation - much like an executive summary - that addresses the problem, the solution, the scope, schedule and cost and other information your team thinks is relevant to making the decision to proceed. And, please do not forget to update the MS Project (.mpp) file. You will post THREE documents only.

Grading approximate breakdown by areas include:

o General: Structure, Format, Mechanics, Style (~4%)

o Updated and Complete MS Project (.mpp) Schedule (~19%)

o Project Resources and Costs (~15%)

o Risk register (~20%)

o ITP-6 Proposal Plan Presentation PPT (~40%)

o Updated project charter (~3%)

Rubrics and Grading for the ITP-6 Project Deliverable

To earn 90-100% of the points available for this assignment -

Meet all requirements, including an updated MS Project WBS with schedule, durations, dependencies,

and resources; project resources and costs at the Summary Task and sub-task levels plus a project total

in either your MS Project (.mpp) and/or Excel; a Risk Register for all major tasks and at least 4 sub-tasks

in either Excel or Word; a Microsoft Word document or (at your instructor's option) PowerPoint

presentation of (9-10 slides) that provides an Executive Summary of your project proposal with sufficient

detail to allow the stakeholder to make a go/no-go decision on whether or not the proposal is

acceptable to begin work on the IT project, and that includes all the information specified above; and an

updated and expanded project charter. Approximate breakdown by areas is as specified above. Include

reference sources are used in the text and included in a Reference page.

The MS Project (.mpp) is complete (all tasks include durations, predecessors/successors, resources) and

the Network View flows from left to right with multiple paths culminating with the final task at the far

right. Most of the Network View is not critical path. Resources are not overallocated and the final task

clearly identifies the end of the project and is consistent with the project charter discussion. The

textbook and at least 5 academically credible reference sources are used in the text and included in a

Reference page. Documents are thorough, easy to understand, and provide consistency throughout. All

documents reflect improvements over the original submissions.

To earn 80-89% of the points available for this assignment -

Meet all requirements, including an updated MS Project WBS with schedule, durations, dependencies,

and resources; project resources and costs at the Summary Task and sub-task levels plus a project total

in either your MS Project (.mpp) or Excel; a Risk Register for all major tasks and at least 2 sub-tasks in

either Excel or Word; a Microsoft Word document or (at your instructor's option) PowerPoint

presentation of (7-8 slides) that provides an Executive Summary of your project proposal with sufficient

detail to allow the stakeholder to make a go/no-go decision on whether or not the proposal is

acceptable to begin work on the IT project; and an updated project charter.

The MS Project (.mpp) is complete (all tasks include durations, predecessors/successors, resources) and

the Network View flows from left to right with multiple paths culminating with the final task at the far

right. Most of the Network View is not critical path. Resources are not overallocated and the final task

clearly identifies the end of the project and is consistent with the project charter discussion. The

textbook and at least 5 academically credible reference sources are used in the text and included in a

Reference page. Documents are thorough, easy to understand, and provide consistency throughout. All

documents reflect improvements over the original submissions.

To earn 70-79% of the points available for this assignment -

Meet all requirements, including an updated MS Project WBS with schedule, durations, dependencies,

and resources; project resources and costs at the Summary Task and sub-task levels plus a project total

in either your MS Project (.mpp) or Excel; a Risk Register for all major tasks in either Excel or Word; a

Microsoft Word document or (at your instructor's option) PowerPoint presentation of (5-6 slides) that

provides an Executive Summary of your project proposal with sufficient detail to allow the stakeholder

to make a go/no-go decision on whether or not the proposal is acceptable to begin work on the IT

project.

To earn 60-69% of the points available for this assignment -

Address an updated MS Project WBS with schedule, durations, dependencies, and resources; project

resources and costs; project risks; a Microsoft Word document or (at your instructor's option)

PowerPoint presentation that provides an Executive Summary of your project proposal intended for the

stakeholder to make a go/no-go decision on whether or not the proposal is acceptable to begin work on

the IT project.

Less than 60% -

Team efforts that do not meet the requirements will earn a zero. Team efforts that are not original work

will earn a zero. Team efforts that do not have proper APA references and citations to any included or

quoted work will earn at most 50%.

Please notice that there is a STRONG incentive for ALL team members to carefully proofread team

documents before submitting. This incentive will continue through the semester.

Project Management Plan Template.docx

Project Management Plan Template

Group Name:
Project Name:
Project Manager
Document Revision #:

Project Management Plan Template | Project Name

Government of the Northwest Territories 2019 4

Table of Contents Table of Contents 1 1 Executive Summary 2 1.1 Purpose, Scope, and Objectives 2 1.2 Assumptions, Constraints and Risks 2 1.3 Project Deliverables 2 1.4 Schedule and Budget Summary 3 1.5 References 3 1.6 Definitions and Acronyms 3 2 Project Organization 3 2.1 Roles and Responsibilities 3 2.2 Stakeholder 3 3 Managerial Process Plans 3 3.1 Startup Plan 3 3.1.1 Estimates 3 3.1.2 Staffing 3 3.2 Work Plan 4 3.2.1 Work Breakdown Structure 4 3.2.2 Schedule Allocation 4 3.2.3 Budget Allocation 4 3.2.4 Quality Control 5 3.2.5 Reporting 5 3.2.6 Project Metrics 5 3.2.7 Risk Management Plan 5 3.2.8 Project Closeout Plan 5

Executive Summary

Purpose, Scope, and Objectives

Assumptions, Constraints and Risks

Project Deliverables

Schedule and Budget Summary

References

Definitions and Acronyms

Project Organization

Roles and Responsibilities

Stakeholder

Managerial Process Plans

Startup Plan

Estimates

Staffing

Work Plan

Work Breakdown Structure

Schedule Allocation

Budget Allocation

Quality Control

Reporting

Project Metrics

Risk Management Plan

Project Closeout Plan

· a process for capturing project metrics in the business projects database,