TPP 5 - Consolidated Project Management Plan (Group)

This section of the Project Management Plan provides an overview of the purpose, scope and objectives of the project for which the Plan has been written, the project assumptions and constraints, a list of project deliverables, a summary of the project schedule and budget, and the plan for evolving the Project Management Plan.

Define the purpose and scope of the project.

Describe any considerations of scope or objectives to be excluded from the project or the deliverables.

Provide a concise summary of:

· the project objectives,

· the deliverables required to satisfy the project objectives, and

· the methods by which satisfaction of the objectives will be determined.

Describe the assumptions on which the project is based.

Describe the imposed constraints and risks on the project such as:

· schedule,

· budget,

· resources,

· quality,

· software to be reused,

· existing software to be incorporated,

· technology to be used, and

· external interfaces.

Identify and list the following, as required to satisfy the terms of the project charter or contract:

· project deliverables (either directly in this Plan, or by reference to an external document),

· delivery dates,

· delivery location, ands

· quantities required.

Specify the delivery media.

Provide a summary of the schedule and budget for the project.

Identify and state the roles and responsibilities of the project team.

Identify the stakeholders.

This section of the Project Management Plan specifies the project management processes for the project. This section defines the plans for project startup, risk management, project work, project tracking and project closeout.

Specify the estimated cost, schedule and resource requirements for conducting the project, and specify the associated confidence levels for each estimate.

Specify the methods, tools and techniques used to estimate project cost, schedule and resource requirements;

Specify the sources of estimate data and the basis of the estimation such as: analogy, rule of thumb, standard unit of size, cost model, historical database, etc.

Specify the methods, tools, techniques to be used to reestimate the project cost, schedule and required resources.

Specify the schedule for reestimation, which might be regular, a periodic or eventdriven (e.g.: on project milestones).

Specify the number of required staff, providing the following details:

· number of personnel by skill level,

· numbers and skill levels in each project phase, and

· duration of personnel requirement.

Specify the sources of staff personnel (e.g.: internal transfer, new hire, contracted, etc.)

Consider using resource Gantt charts, resource histograms, spreadsheets and tables to depth staffing plan by skill level, by project phase, and by aggregations of skill levels and project phases.

The Work Breakdown Structure (WBS), listed in Appendix C – Team Business Task Sheet, specifies the various work activities and work packages that will be performed within the Mamma’s Sandwich Shoppe & Bakery project plan. The WBS serves as the foundation of the project plan’s processes by organizing and defining the total scope of the project (Brotherton, Fried, & Norman, 2008), allowing the project team to identify the sequencing and dependencies of work activities quickly.

The activities listed within the WBS have broken down into ten (10) different level two (2) tasks, each representing a deliverable-oriented hierarchical decomposition of the work that needs to be executed by the project team. The following hierarchical diagram demonstrates the work activities broken down into three task levels:

The decomposition of these activities was based on each activity’s dependency on its previous stage or parallel activities that form the critical path to execution and completion (nutcache.com, 2019). Within each level three (3) work package, risks were identified and exposed, allowing Team Business’ project team to accurately identify the necessary resource requirements, schedule duration, and cost estimates.

Once the project work activities were defined and sequenced within the WBS, the activities were then transferred into a Gantt chart using the Microsoft Project productivity tool allowing the project schedule to be easily read and understood by all key stakeholders. The project activity durations were allocated by implementing a bottom-up approach where each work task is estimated based on the subtasks and estimated activity duration within each work package and aggregated. The associated Gantt chart within the Microsoft Project Plan, see Appendix A – Team Business Project Plan, demonstrates all of the critical stages within the project, listed on the y-axis, and their durations as bar charts with the time scale on the x-axis.

There were a few opportunities for concurrent work activities, such as within the Project Management phase, where activities were defined and sequenced to comprise the WBS; additionally, within these activities, costs were planned and estimated concurrently with systems acquisitions and contracting processes. The consolidation of these activities allowed the project planning phase to be executed in a more desirable timeline allowing for a more rapid delivery timeframe and formed the critical path. The critical path, or series of interrelated task dependencies that enable the project to be completed in the shortest amount of time, within the schedule is depicted in the following diagram:

Milestones serve as the exit gates or critical checkpoints that signify the successful completion of a project phase or project goal (Anderson, 2006). There are nine (9) milestones listed within Mamma’s Sandwich Shoppe & Bakery project plan:

The budget that supports Mamma’s Sandwich Shoppe & Bakery project was derived by using the WBS alongside investigating resource information from various sources such as the United States Bureau of Labor and Statistics and vendor websites that provided licensing quotes for their hardware, networking, or system licensing and components. This budget was incorporated into Team Business’ project plan within the Resource Cost Sheet, see Appendix B – Team Business Resource Sheet.

The estimated costs for resources allocated to this project include the costs for the personnel (internal and external), IT system hardware, Software-as-a-Service licenses, Internet Service Provider services, Service and License activation fees, and system training. The Project Plan listed in Appendix C – Team Business Task Sheet lists out each of these activities in greater detail with its associated costs.

The overall anticipated budget to support the project and project team is $60,194.99, which includes the $52,141.99 estimated project cost with an additional 15% overhead, or $8,052.90 projected for risk responses. These projected costs are 40% below the anticipated budget providing additional funding for unanticipated risks while allowing Mamma Mia to integrate other IT initiatives for her business.

To provide customer satisfaction and ensure that the project plan meets Mamma Mia’s business needs, total quality management is implemented to accurately asses, validate, and verify the needs and requirements of the organization to drive the project plan and align its resources appropriately.

The initial steps within the quality assurance and quality control process are first to gather the technical requirements based on Mamma’s Sandwich Shoppe & Bakery’s use-case. These steps were identified within the task and subtasks to 1.2.1.2 – Project Management, where Mamma’s business case, environmental factors, and organizational processes were identified and used to define the project plan. To strengthen the project plan and ensure all activities were conducive to the overall project, each requirement was verified to be clearly understood and quantified based on feedback from Mamma Mia, known as the voice of the customer.

Once these requirements were defined, the WBS was generated and distributed to all key stakeholders in the form of an activity network diagram that exemplified all logical relationships, or interdependencies, of the project’s activities to help demonstrate the workflow of the project. Additionally, risks and risk responses were identified within a risk register, see Appendix D – Team Business Project Risk Assessment which provided the overall cost of quality (COQ) that demonstrated any costs attributed to quality such as risk prevention/aversion, failures, and non-conformance costs (Lutzker, 2002).

Furthermore, comprehensive test planning was incorporated within the project plan under the both 1.6 – System Software and 1.7 – System Test work activities, testing each of their requirements and configurations, such as the Enterprise Resource Planning software, Point of Sale software, and e-commerce webpage and then testing the integration of these components to support Mamma Mia’s business case. The final tests executed upon delivery is the User Acceptance Testing, which provides the information necessary for the project team to identify any defects and establish a change control process to remediate any issues.

Specify the reporting mechanisms, report formats and information flows to be used in communicating the status of requirements, schedule, budget, quality, and other desired or required status metrics within the project and to entities external to the project.

Specify the methods, tools and techniques of communication.

Specify a frequency and detail of communications related to project management and metrics measurement that is consistent with the project scope, criticality, risk and visibility.

Specify the methods, tools, and techniques to be used in collecting and retaining project metrics.

Specify the following metrics process information:

· identification of the metrics to be collected,

· frequency of collection, and

· processes for validating, analyzing, and reporting the metrics.

Specify the risk management plan for identifying, analyzing, and prioritizing project risk factors.

Specify plans for assessing initial risk factors and for the ongoing identification, assessment, and mitigation of risk factors throughout the life cycle of the project.

Identify the plans necessary to ensure orderly closeout of the project.

Specify the following:

· a staff reassignment plan

· a process for archiving project materials,

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

· a process for postmortem debriefings of project personnel, and

· a plan for preparation of a final report to include lessons learned and an analysis of project objectives achieved.

· plans for assuring that safety, privacy, and security requirements are met,

· special facilities or equipment specification,

· product installation plans,

· user training plans,

· integration plans,

· data conversion plans,

· system transition plans,

· product maintenance plans, or

· product support plans.

Mamma's Sandwich Shop & Bakery

Project Start

Project Mgmt

IT System Design

System Networking

System Hardware

System Software

System Test

System Transition

Project Closure

Project Close

Initiation

Planning

IT Contractors

Initial Design

Review Design

Deliver Design

Reqs

Procure

Install

Reqs

Procure

Install

Reqs

Procure

Install

Integrate

Test

Delivery

Prepare Documents

Review Documents

Deliver Documents

Training

Lessons Learned

Update Files

Closure Meeting

Archive Files

Release Resources

Project Start

Project Mgmt

Project Planning

System Networking

System Hardware

System Software

System Test

System Transition

Initiation

Project Charter

Kickoff Meeting

Activity Planning

Procurement Mgmt

IT System Design

Integration

Delivery

Project Close

Documentation

Training

Lessons Learned

Project Files

Release Resources

M1 1.1 Project Start

M2 1.2.2 Project Initiation COMPLETE

M3 1.2.4 Project Planning COMPLETE

M4 1.3.4 Deliver IT Design Specs

M5 1.7.3 Deliver IT System

M6 1.8.3 Deliver IT System Documentation

M7 1.8.4 Provide Staff Training

M8 1.9.3.1 Gain Closure Accept -ance

M9 1.10 Project Close

Page 1 of 7