Occasions for All Gala Project Plan
University of Maryland Global Campus
PMAN 635, Professor Hall
Submitted on April 23, 2020
Olalekan Adams
Tavarus Cockrell
Amanda Nicolet
Rachel Overman
Donaldson Smith
Derian Thomas
Bryony Trickey
Table of Contents
Occasions for All Gala Project 4
Introduction 4
Company Overview 4
Project Selection 4
Project Scope Statement 6
Project Overview 6
Project Requirements 6
Assumptions and Dependencies 7
Constraints 8
Budget Summary 9
Schedule Summary 10
Project Organization 12
Roles and Responsibilities 12
PM and Authority Level 12
Project Team 12
Project Sponsor or Customer and Authority Level 13
Project Resources 14
Project Monitoring and Control Plan 15
Responsibilities 15
Monitoring 16
Controlling 17
Reporting 18
Change Management 19
Tools 20
Earned Value Management 20
Risk Management Plan 21
Reserve Calculations 21
Risk Probability and Impact 22
Project Closeout 22
Project Closeout 23
Customer Closeout 23
Organizational Closeout 23
Closeout Checklist 24
Customer Satisfaction Survey 25
References 26
Appendix A 27
Appendix B 28
Appendix C 29
Appendix D 30
Appendix E 31
Attachment F 32
Attachment G 33
Attachment H 34
Attachment I 35
Occasions for All Gala Project
Introduction
St. Xavier Academy is one of the most prestigious schools in the country with both a West Coast campus (San Francisco) and an East Coast campus (New York City). The Music Program operates on funds from the St. Xavier Academy’s annual budget and is supplemented by fundraising efforts. The Music Program’s needs currently outweigh the funds that they are allocated so the school has decided to initiate a three-year fundraising project to meet the budget needs of the Music Program.
Company Overview
Occasions for All is a nationally recognized company that specializes in large fundraising events for high-profile non-profit organizations. They have over 20 years of experience in event planning and coordination and were chosen by St. Xavier Academy to raise funds over the next three years for the school’s renowned music program. Each fundraising event goal is to bring together alumni, current students, prospective students, and possible patrons/donors.
Project Selection
Occasions for All identified three potential projects, all with the goal of raising funds for the St. Xavier Academy Music Program. The projects were evaluated by a weighted scoring chart that considered such criteria as: cost, possible amount of funds to be raised, attendance goals being met, ability to appropriately allocate funds, prestige, net present value (NPV), and length of project.
| Project | Criteria | (A) Importance | (B) Score | x (B) Weighted Score |
|
Project 1 Fundraising Gala Project | Cost | 3 | 2 | 6 |
| Potential of funds to be raised | 3 | 3 | 9 | |
| Attendance goals | 2 | 3 | 6 | |
| Allocation of funds | 3 | 3 | 9 | |
| Length of project | 1 | 3 | 3 | |
| Prestige | 3 | 3 | 9 | |
| NPV | 3 | 3 | 9 | |
| Project #1 – Total Score | 51 | |||
|
Project 2 Carnival Event Project | Cost | 3 | 1 | 3 |
| Potential of funds to be raised | 3 | 2 | 6 | |
| Attendance goals | 2 | 3 | 6 | |
| Allocation of funds | 3 | 2 | 6 | |
| Length of project | 1 | 1 | 1 | |
| Prestige | 3 | 1 | 3 | |
| NPV | 3 | 2 | 6 | |
| Project #2 – Total Score | 31 | |||
|
Project 3 Candy Sales Project | Cost | 3 | 3 | 9 |
| Potential of funds to be raised | 3 | 1 | 3 | |
| Attendance goals | 2 | 1 | 2 | |
| Allocation of funds | 3 | 2 | 6 | |
| Length of project | 1 | 1 | 1 | |
| Prestige | 3 | 1 | 3 | |
| NPV | 3 | 1 | 3 | |
| Project #3 – Total Score | 27 |
Table 1: Simplified Scoring Model
Occasions for All gave the most weight to the criteria that were determined to have the most potential positive impact for the academy as St. Xavier Academy is a prestigious institution. The criterion of adding prestige to the academy was ranked as important as the criteria for cost, possible amount of funds to be raised, and allocation of funds. The project with the highest weighted score was selected, which was the Gala Project that met all the requirements to meet funding raising goals in the shortest duration (see Table 1: Simplified Scoring Model).
Project Scope Statement
Occasions for All will organize annual charity galas over the next three years to raise $45 million for the St. Xavier Academy Music Program. The goal for each charity event is to raise a minimum of $8 million for auditorium renovations, $2 million for program supplies (instruments, uniforms, etc.) and performance expenses, and $5 million for scholarships, to be used at both campuses (San Francisco and NYC) for a total of $45 million. The events will be galas with fine dining, premium alcoholic beverages, world-class entertainment, and live-silent auctions. Occasions for All will coordinate and execute the three events to stay within the total budget of $3.6 million; which equates to $1.2 million per gala, and will meet the fundraising goals by negotiating and soliciting donations on behalf of the St. Xavier Academy Music Program.
Project Overview
This fundraising project will ensure that all interested students will have access to music instruments and equipment, and that there will be financial support for performances, competitions, and scholarships. At the end of the project, it is expected that the music program will be able to support every student and be able to last long term. The funds raised will ensure the longevity and continued success of the St. Xavier Academy Music Program.
Project Requirements
Occasions for All will use the following benchmarks to ensure the success of the fundraising gala project.
Technical Requirements
- Each of the three events scheduled must be able to raise a minimum of $15 million: for a grand total of $45 million after the three-year project.
- Funds from the fundraising events need to be made available within one month after each gala.
- Gala location must support a minimum of 150 people and be located within 25 miles of the school area.
- Donated auction items must account for at least 75% of each fundraising goal.
Functional Requirements
- Stakeholder satisfaction surveys must be completed within two months after each gala.
- Each gala must be closed out with detailed recommendations for future fundraising events based on lessons learned captured from the current project’s events within two months of the completion of each gala.
- Updating the donor database after each gala must be done within three months of each gala and reviewed prior to the next gala.
- The level of awareness of the St. Xavier Academy Music Program must increase as a result of this project, which will be measured by a 20% increase in telephone and website inquiries to the St. Xavier Academy within one year after the first gala.
- All local, state, and federal regulations pertaining to fundraising activities must be adhered to. Compliance will be verified through project audits.
Assumptions and Dependencies
While projects function with some uncertainty, there are elements that are certain or absolute in order to proceed with planning. The following factors are considered to be true:
- $1.2 million in funds will be available for each event (three events over three years for a total of $3.6 million).
- The venue will have functional HVAC services and facilities to accommodate the gala on the day of the event.
- Supplies (food, beverages, decorations, auction items, etc.) will be delivered on time prior to each event.
- Vendors will be responsive during the planning stages and will be punctual on event days.
- The St. Xavier Academy will approve the dates and venues, or alternatives proposed by the Project Team within seven days and will not request changes once contract(s) have been approved and signed.
- The venue and all vendors will have insurance.
- At least 75% of all auction items will be donated.
Constraints
It is imperative that Occasions for All stay within the project budget of $3.6 million for all three galas, which is $1.2 million per gala. The project must be completed within the project life cycle of three years. In addition to the constraint regarding completing the project on time, the schedule for planning and executing each event must be adhered to in order to ensure that each event is completed as scheduled, since each event must occur as planned to avoid complications as a result of the events not occurring on time. Occasions for All must start planning the next gala immediately after the previous gala is closed out.
Budget Summary
This project spreads over a three-year period with the cost breakdown shown for the budget of the three gala events and high level phases of the project per Work Breakdown Structure (WBS).
WBS Level 1 activities include:
| Initial Planning | $27,844.87 |
| Gala 1 Total | $1,038,968.38 |
| Gala 2 Total | $1,049,665.66 |
| Gala 3 Total | $1,053,180.98 |
| Project Closeout | $8,664.20 |
| Project Management | $134,043.04 |
| Total Project Cost | $3,312,367.13 |
WBS Level 2 activities for each gala that are included in the Level 1 totals are:
| Gala 1 Event Planning | $93639.72 |
| Gala 1 Event Contracts | $191,258.90 |
| Gala 1 Event Administration | $730,419.36 |
| Gala 1 Closeout | $23,650.40 |
| Gala 2 Event Planning | $108,945.12 |
| Gala 2 Event Contracts | $183,731.30 |
| Gala 2 Event Administration | $733,228.32 |
| Gala 2 Closeout | $23,760.92 |
| Gala 3 Event Planning | $124,190.60 |
| Gala 3 Event Contracts | $177,569.26 |
| Gala 3 Event Administration | $730,065.76 |
| Gala 3 Closeout | $21,355.36 |
Due to the unique nature of this project (three separate fundraising events over the course of three years), the following cost breakdown is provided for ease of reference. These costs are the total project expenses for all three galas in the provided categories:
| Initial Planning | $27,844.27 |
| Event Planning | $326,775.44 |
| Event Contracts | $552,559.46 |
| Event Administration | $2,193,713.44 |
| Gala Closeouts | $68,766.68 |
| Project Closeout | $8664.20 |
| Project Management | $134,043.04 |
| Total Project Cost | $3,312,367.13 |
Resource Summary:
| Total Materials and Equipment | $2,193,713.44 |
| Venue Costs | $639,948.80 |
| Total Labor (Work) | $2,833,662.24 |
Schedule Summary
This project is broken down into several tasks, which are recorded in the WBS and can be found in Attachment G. The tasks are all grouped into phases that are distinguished by a project planning phase, each gala event, and a project closeout phase. Within the WBS are various milestones that represent significant achievements within the project. Each gala has milestones for the completion of the planning process, the completion of the signing of all contracts, the completion of each gala event, and the completion of closeout activities, as pictured below with the milestone dates.
| Milestone Name | Baseline Milestone Date |
| Gala 1 Planning Complete | 10/19/2020 |
| Gala 1 Contracts Complete | 12/18/2020 |
| Gala 1 Event | 03/11/2021 |
| Gala 1 Closed Out | 06/18/2021 |
| Gala 2 Planning Complete | 12/02/2021 |
| Gala 2 Contracts Complete | 02/22/2022 |
| Gala 2 Event | 05/16/2022 |
| Gala 2 Closed Out | 08/19/2022 |
| Gala 3 Planning Complete | 02/01/2023 |
| Gala 3 Contracts Complete | 04/24/2023 |
| Gala 3 Event | 07/05/2023 |
| Gala 3 Closed Out | 10/06/2023 |
The Occasions for All St. Xavier Academy Music Program Fundraising Project is scheduled to last a total of 958 days from start to finish. Due to the importance of holding each event on the date scheduled, any tasks on the critical path that are behind schedule will need to be crashed. The critical path can be viewed in Attachment G. The cost associated with changing an event date after invitations have been ordered, contracts have been signed, the venue and entertainment have been booked, would be catastrophic to the project as a whole. If there are weather-related events that prohibit the galas from taking place as scheduled, the alternate dates would be used; however, this is a risk mitigation plan and is not to be used due to scheduling delays.
Project Organization
Roles and Responsibilities
The project hierarchy for Occasions for All shown below corresponds with the matrix in Attachment I to illustrate the roles and responsibilities for the Occasions for All gala project execution with the customer a dashed line for communication status.
Project Manager and Authority Level
Mrs. Bryony Trickey is the Project Manager (“PM”) of Occasions for All and has the authority to make decisions and changes within the authority of Occasions for All. As PM, Mrs. Trickey will be present at all project meetings and at all meetings with the stakeholders and project sponsor in order to facilitate and direct communications and can therefore make decisions without the project team’s consensus when necessary. Mrs. Trickey has the authority to hire, fire, and discipline the team members assigned to the project, and has the authority to allocate resources and adjust budgets as controller of the project’s funds. Mrs. Trickey will oversee all aspects of the event planning and coordination and conflicts should be brought to her attention as soon as possible as she has the authority to deal with them. Mrs. Trickey is responsible for all stakeholder communications including and in addition to the once every two weeks project status meetings.
Project Team
The project team consists of Team Leads: Project Manager Assistants, Administrator, Donation Manager, Event Planner, Financial Analyst, Security Manager, and the Social Media Expert. They oversee their departments and the team members within. The project team is responsible for the implementation, monitoring, and documenting of the event coordination activities and will report any change requests or status updates to their Team Lead. Team Leads are responsible for monitoring their department and reporting to the PM.
Project Sponsor or Customer and Authority Level
The project sponsor is Mrs. Doe, the president of the St. Xavier Academy’s PTA, which has overall accountability for the fundraising events. The primary concern is ensuring that the fundraising events deliver the desired revenue and donations to the benefit of the St. Xavier Academy Music Program. The PTA President acts as the community representative of the school, playing a critical leadership role by:
- Providing expertise and guidance to the PM and Occasions for All.
- Ensuring funding and priority for the project.
- Acting as the final decision-maker for decisions and issues that exceed the authority of the PM.
- Acting as an additional line of communication between team members and stakeholders.
- Acting as the link between the project and the community.
The project sponsor, Mrs. Doe, and the PM, Mrs. Trickey, depend on each other for the success of this project and will work together to ensure the successful outcome of this project.
Project Resources
Occasions for All will procure the services of subcontractors for the event day set-up/clean-up, catering, decorating, and entertainment to be executed. The contract used for each of these services is a fixed price contract which will help control cost and reduced risk within the project. Having a fixed price contract for these services places the entire risk of completing the task within the budget upon these contractors and hence avoid cost overrun in the project.
The project resources hired by Occasions for All for the majority of project tasks (not including smaller roles such as security) are as follows:
| Resource Title | Level of Effort | Project Role |
| PM | 40 hours/week | The PM is responsible for overseeing the planning, and for monitoring and controlling all phases of the project. They will report to the customer. |
| Admin 1 – 4 | 40 hours/week | Admins (1-4) are responsible for planning and coordinating logistics to fulfill project objectives such as contracts, permits, rentals, staffing, budget monitoring and reporting, and guest communications. |
| Donation Manager | 40 hours/week | Responsible for compiling the donors list and procuring donations. |
| Event Planner | 40 hours/week | Responsible for planning all event elements and logistics, which will be supported and carried out by the Admins and PM Assistants. |
| Financial Analyst | 40 hours/week | Responsible for budget monitoring and reporting. Oversees contracts. |
| Financial Analyst 2 | 40 hours/week | Responsible for budget monitoring and reporting. Oversees contracts. Reports to Financial Analyst 2. |
| PM Assistant 1-3 | 20 hours/week | Assists PM (1- 3) in logistics and coordination of project. |
| Social Media Expert | 10 hours/week | Responsible for social media campaign design. |
| Social Media Assistant | 20 hours/week | Responsible for social media campaign research and implementation. |
Project Monitoring and Control Plan
The Occasions for All project team will conduct regular reviews of activities that are taking place in a project and keep a record of them. Time, cost, requirement fulfillment, and deliverables must all be reviewed throughout the phases of the project to ensure that the project will be successfully completed on schedule and within budget. As this project is event based, it is imperative that the project is monitored as there is less flexibility for schedule overages when there is a fixed event date. The monitoring plan set forth intends to keep the project on track, and to communicate its status and progress to the appropriate stakeholders, most importantly to the customer St. Xavier Academy. It also sets forth the tools and techniques that will be used to control risk management, scope creep, project schedule, and project budget
Responsibilities
The following resources from the project plan (Attachment G) are considered Team Leads and are responsible for managing their team’s responsibilities and ensuring that project requirements are met and will attend team meetings with the PM: PM Assistant, Administrator, Donation Manager, Event Planner, Financial Analyst, Security Manager, and the Social Media Expert. The PM will be responsible for the EVMS outlined in this plan and will use the project status updates provided by the team leads to produce the quarterly analyses and communicate them to the project stakeholders.
Monitoring
The project team has a proper structure in place to ensure proper monitoring of the project. Occasion for All employees will send weekly status updates to their Team Lead who would then use it to monitor aspects of the project. Team Leads will monitor their team’s progress and will communicate to the PM who is monitoring the entire project through meetings, status reports, change requests, and the other tools described in this project to ensure that the project is on schedule, within budget, and within scope. Using all the information available from project team members and other stakeholders, the PM can make projections about the project. Comparing these projections to the progress of the project will help in the monitoring of progress and ensuring every aspect of the project is on task and on goal. The lower level managers will be tasked with monitoring the resources required to complete tasks for the project. They will report this information back to the PM and the team to ensure optimal work is being done. The PM and the Financial Analyst of the project will be monitoring budget, overall project schedule to ensure things run smooth.
Occasions for All will also utilize several tools to monitor and ensure the project remains on track. Occasions for All will be using EVM systems to help with forecasting, the identification of issues with the project, and problem solving. This system will provide data that stakeholders can use to monitor the progress of the work and ensure everything remains on schedule. The EVM system gives the project team a chance to prepare for a scenario where work is behind schedule and decisions need to be made about potentially crashing the project or finding ways to close gaps in the project.
At the end of each gala, the project team will meet to evaluate the project thus far. There will be an evaluation of how the event went, and what can be done better to improve performance before the next gala. Major stakeholders will be included in this review process for recommendations for the next event. Success reports and lessons learned reports will be produced.
Controlling
Control is a key aspect of project management. Project control ensures that the requirements of the projects are met by ensuring the PM verifies project scope throughout the project life cycle, and especially when changes are made, and milestones are completed. If there are any issues with tasks or scheduling, adjustments must be made to ensure the project does not deviate from its critical path. There will be weekly team status updates, as once every two weeks project status meetings. These updates to stakeholders are performance reports which will highlight project status and show projections for schedule and budget. Any issues with budget, schedule, or scope must be immediately accounted for in the project control plan to ensure that all deliverables will meet project requirements that we are on budget and on schedule.
Quality control is a very important step in control. Feedback from closeout meetings and surveys from attendees of each gala will be important to ensure the success of the next event. Quality control processes will also ensure that deliverables and all project objectives were met in order for project acceptance. Feedback will be collected from project team members, other relevant stakeholders, and attendees of the gala to ensure maximum lessons learned before the start of the next one. They will be done via QR code surveys for gala guests and the feedback will be reported through Lessons Learned reports produced at the closeout meetings, post gala and post project.
The critical path of the project cannot be deviated from so it will be controlled differently than other aspects of the project. Tasks on the project critical path affect the other tasks in the project, so it is imperative that they are focused on and completed on time. The tasks in the critical path have to be completed so the level of control for those tasks to ensure completion will be different than other tasks that have some level of slack. There will be more resources allocated to critical task activities to ensure that there are no issues with competition.
Crashing the project is a vital tool for the PM to have in the arsenal. The PM for Occasions for All may elect to crash the project due to scheduling issues. This project has a set timeline that is rigid and hard to move around. It is a priority to meet the dates set at the beginning of the project. The PM will have to find low cost high reward tasks that help ensure the project remains close to its original schedule to crash to ensure project success. With this being a multiyear event, the PM could also in the future galas crash some other activities using lessons learned to cut down on the schedule as well.
Reporting
Occasions for All will utilize several reporting methods throughout this project’s life cycle. Project progress is reported by team members to their managers with status updates, who then communicate it to the PM on a weekly basis, or when the task is complete, via a project status report (Appendix C). Thresholds for ad hoc reporting are task completion, change requested, or evaluation performed of a project component, schedule, or budget that do not have a scheduled meeting or report within 48-hours. The PM will provide the customer with once every two weeks project status reports noting current standing on budget, schedule, and fulfilling project requirements. The PM will hold monthly meetings with the customer to report project status and discuss/respond to any project scope changes or changes in requirements from the customer. An Earned Value Analysis will be used to measure the project progress in addition to cost and schedule. The EVA will compare current project progress with our baseline project plan (Attachment G) and provide a report on the project status measured as a dollar value. The EVA reports will include schedule and cost variances and will calculate the EAC using the formula EAC= AC + (BAC – EV) / (CPI * SPI). This method is described in more detail further in this plan. Any changes made will be reported in the change log, as described below.
Change Management
Changes will be proposed via a Project Change Request Form (Appendix D) and will be discussed and decided by the PM at weekly team meetings. When considering changes to the project, the integration of those changes and their impact on time, budget, scope, procurements, resources, etc. will be discussed. The discussion and decision will be noted in the meeting minutes and the change will be reported in the change log. Any changes that impact the project schedule, budget, or scope to the degree requiring customer authorization per the project scope statement (Occasions for All Project Scope Statement, 2020) will need to reflect both PM and customer sign-off in the change log. Team leads may make minor changes when necessary, that do not impact the project schedule or budget (i.e. approving alternate food or décor options). Changes that pass the thresholds of a projected 5% increase to planned schedule and budget for the task, or a change to a project requirement or specification will require a Team Lead to propose the change to the PM, who if approving of the need for the change will then bring it to the change management board which includes the PM, the Financial Analysts, and a representative from the customer (St. Xavier Academy) to approve the change. Changes will be integrated in the project, and their implementation and subsequent impact will be monitored and recorded with the procedures discussed above regarding project status.
Tools
Occasions for All will utilize Microsoft Project as a resource management tool throughout the project lifecycle. Using this tool will allow for the PM to provide real-time updates to the stakeholders associated with the project. The project’s Gantt chart will be used to help monitor the project’s schedule. The milestones that are in the Gantt chart are an important component to tracking the project’s schedule and overall progress. Occasions for All will monitor the progress of the project and compare the project status against the project plan to determine if the project is moving according to schedule. Tasks that are on the critical path will receive special attention, since any scheduling deviations of these tasks will affect the event dates that have been set and must be adhered to.
Earned Value Management
Occasions for All will conduct a monthly EVM analysis of the project, comparing the project’s current path to the baseline created in the planning stages. Occasions for All will use the data measured regarding the earned value, planned value, actual costs, and variances to identify the cost performance index (CPI), scheduled performance index (SPI), estimate at completion (EAC), and the to complete performance index (TCPI) in order to track costs and the project’s performance in regards to schedule. Occasions for All will use the following EAC formula: EAC = AC + (BAC – EV) / (CPI * SPI), which assumes that the remaining project cost is affected by the schedule and cost variances to date. The analysis of all of this data will help Occasions for All keep the project on target and correct any deviations before they get out of control and cause the whole project to derail. The table in Appendix B shows the EVMS that Occasions for All will use while monitoring and controlling the St. Xavier Academy Fundraising Project.
Risk Management Plan
The PM created a risk management plan with the project team that identified potential and probable risks that would have a significant impact on the project. Four major risks were identified and were then analyzed for their probability and impact, and strategies were discussed to mitigate the risks (Attachment H). The risk register identified the WBS element(s) impacted and details of the risks and mitigation strategies were documented there. Mitigation strategies included calculating schedule and labor reserves. For T-E calculations, optimistic and pessimistic estimates were drawn from durations from similar projects that Occasions for All has conducted in the past, and the most likely estimates were the initial schedule created by Occasions for All for the St. Xavier Academy project.
Reserve Calculations
The PM has complete authority over allocation of the reserve to meet the scheduled gala milestone date risk. The reserve budgets were calculated by taking the material costs at 90% and subtracting them from the material cost forecast at the “most-likely” level for each material cost. Then the material cost reserve and the risk management material costs for all three events were added together to calculate the total material reserve. The project T-E duration was subtracted from the calculated 90% certainty duration for completing the project. The work cost reserve was calculated by dividing the total work cost of the project by the project T-E duration and then multiplying that figure by the reserve number of days, calculated as stated above.
- Schedule Reserve: 26 additional days to complete the project at the 90% certainty rate
-
Total Budget
Reserve: $182,148.69
- Materials: $127,295.56
- Labor: $54,853.13
Risk Probability and Impact
| ID | Risk | Probability | Impact |
| OFA R-01 | If contracts are signed for an event that needs to be canceled due to weather and the event cannot be rescheduled within the contracting period | Low | Schedule delay, cost increase |
| OFA R-02 | Venues of choice are booked, and more venues need to be identified and selected from (adding more time to the venue selection process) | Low | Schedule delay |
| OFA R-03 | Entertainment costs increase due to setup needs in venue space (ex. the venue has weird acoustics, and the DJ’s equipment won’t suffice) | Medium | Cost increase |
| OFA R-04 | Conflict of events. A major event to be held the same day and time as the Gala preventing celebrity attendance which reduces the prestige of the event. | Low | Schedule delay |
| OFA R-05 | Shortage of donated auction items | Low | Cost increase |
Project Closeout
Occasions for All has planned for project closure as it is a key component to ensure project financial success, assess the project’s performance, identifying lessons learned and confirming that all contractual activities have been completed. Occasions for All plans to ensure that all facets and components of the entire project need to be properly finished and signed off on before the team can begin their next project assignment. The PM is responsible for conducting the project closeout phase to confirm that all project requirements have been completed. The PM will conduct the closeout in three main phases: project closeout, customer closeout and organizational closeout. The PM will lead the closure process with the three assistants support.
Project Closeout
Occasions for All will validate that all work for the three galas has been completed as outlined in the original contract and if something is missing, incomplete or not done correctly based on policy then they will document this issue and put into execution corrective actions to correct the missing, incomplete or incorrect document. The PM will also review the legal requirements and ensure that all terms have been met as well as review any change orders to ensure that these have been completed prior to customer closeout. The PM will also review the customer (St. Xavier Academy) notes to ensure that any requests have been attended to and the clean-up and equipment rentals have been returned. The PM will also start the closeout report and schedule the lessons learned meeting(s).
Customer Closeout
Customer Closeout is critical to the business model for Occasions for All and ensuring that the customer is satisfied with the execution of the gala events and has received the deliverables will solidify the relationship for future proposals. The PM will coordinate a closeout meeting with the customer (St. Xavier Academy) to listen to their feedback and address any concerns immediately before they become blown out of proportion or too far gone to fix. The PM will validate the customer satisfaction survey feedback given at the end of each gala for incorporation into the final project report.
Organizational Closeout
Occasions for All PM will notify any subcontractors or other parties of the last date of the project to verify the release of any borrowed or rented equipment. The PM assistants will coordinate conducting an audit of any inventory, gala reports, photos or video from the three events and adjudicating any missing information into the project archive. The PM will reconcile the budget, comparing the money spent with the money budgeted and paying outstanding invoices and interfacing with the in-office accounting team to start the finance sign off and contract closure.
Closeout Checklist
The three closeout phases will be implemented using a comprehensive, step by step approach to project closeout to ensure the customer ends up happy with the experience and results as well as the organization. The closeout process entails several steps and a closeout checklist (Appendix A) for properly wrapping up all facets of a project.
Here are the key steps for formally closing a project:
- Revisit the project scope, requirements, and final feature checklist. Make sure everything has been met 100%.
- Secure approvals and signatures. Ensure full stakeholder approval or customer satisfaction about your work by getting them to sign off on relevant deliverables. Close all outstanding contracts and agreements with internal partners or third-party vendors.
- Settle all payments. Process outstanding invoices, commissions, fees, or bonuses. Build positive relationships by being prompt on payments. Note down variances, cost efficiencies, and other financial information that will help you optimize the budget for the next project.
- Identify, and document lessons learned. Conduct a thorough postmortem process. Gather feedback from all stakeholders. Highlight important issues and lessons learned that will help improve the quality, value, workflow, speed of completion, cost-efficiency, and team synergy of the next project.
- Finalize all required reports for closing a project. Focus on insight-generating reports that will help improve the delivery of succeeding projects.
- Index/archive project documentation. Archive relevant documents that were used in the project from start to finish, including business requirements, project plans, meeting minutes, financial documents, contracts, agreements, and other materials into your organization’s knowledge base. This will help improve corporate data analytics and provide relevant insight for subsequent projects.
- Release project resources. Free up team members and resources that are scheduled for inclusion in other projects.
- Conduct a project closeout meeting. Whenever possible, conduct a final project meeting involving all team members, stakeholders, and the new project owners to a) officially transition the project, b) explore issues, lessons, and opportunities, c) acknowledge outstanding efforts, and celebrate. Letting your team and stakeholders enjoy an atmosphere of celebration and camaraderie to help energize and inspire them for the next project.
Customer Satisfaction Survey
Occasions for All will also conduct a customer satisfaction survey with the customer (St. Xavier Academy) to as part of the closeout report gathering information to rate the overall events, organization of the events, event locations, overall expectations and finally feedback for any improvements. This input is critical to the continued growth of Occasions for All and executing future events and potential customer growth organizational goals.
References
Occasions for All Project Charter, 2020
Occasions for All Risk Register, 2020
Occasions for All Project Schedule, 2020
Occasions for All Project Scope, 2020
Appendix A
Project Closeout Checklist
| Step | Step Description | Assigned To | Artifact for Closure | Quality Assurance Date for Validation |
| 1 | Verify all project requirements have been completed based on the project scope |
|
|
|
| 2 | Verify all deliverables have been handed off and signed by stakeholders getting their approval |
|
|
|
| 3 | Verify other project documents have been signed by site coordinator or POC (contracts, agreements) with vendors and other contractors |
|
|
|
| 4 | Pay all outstanding invoices and closeout any project related contracts |
|
|
|
| 5 | Audit project files to ensure all files are accounted for and archive project |
|
|
|
| 6 | Conduct Lessons Learned Meeting to include feedback from all stakeholders, vendors, contractors and project personnel |
|
|
|
| 7 | Conduct Analysis of lessons learn and update policy, procedures, estimation/actuals database |
|
|
|
| 8 | Assign a transition support person to validate closure report and audit archive |
|
|
|
| 9 | Celebrate with project team and release/reassign project resources |
|
|
|
| 10 | Write Project Closure Report |
|
|
|
Appendix B
Occasions for All EVMS
| Activity | Pred. | Duration | BAC | PV % (week 13) | PV $ (week 13) | AC | % Complete (week 13) | EV | CV | SV | CPI | SPI | Critical Ratio | EAC |
| Totals |
Appendix C
| Occasions for All Project Status Report | ||||
| PROJECT SUMMARY | ||||
| REPORT DATE | PROJECT NAME | PREPARED BY | ||
|
|
|
| ||
| STATUS SUMMARY | ||||
|
| ||||
| PROJECT OVERVIEW | ||||
| TASK | % DONE | DUE DATE | DRIVER | NOTES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| BUDGET OVERVIEW | ||||
| CATEGORY | SPENT | % OF TOTAL | BUDGET STATUS | NOTES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RISK/ISSUE HISTORY | ||||
| ISSUE/RISK | RESPONSE | OWNER | DATE | |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
| CONCLUSIONS/RECOMMENDATIONS | ||||
|
|
Appendix D
| Occasions for All Project Change Order Request | ||||
| REQUEST DATE | PROJECT NAME | REQUESTED BY | ||
|
|
|
| ||
| CHANGE REASON | ||||
|
| ||||
| IMPACT OF CHANGE | ||||
| SCOPE | BUDGET | SCHEDULE | RESOURCES | OTHER |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| PROPOSED ACTION | ||||
| DESCRIPTION | ASSOCIATED COST | APPROVED BY | DATE | |
|
|
|
|
| |
| NOTES | ||||
|
|
Appendix E
| Occasions for All Reporting Matrix | |||
| Deliverable | Owner | Audience | Frequency |
| Project Status Report | Team Members | Team Leads | Weekly |
| Project Status Report | Team Lead | PM | Weekly |
| Project Status Report | PM | Stakeholders | Every Two Weeks |
| Change Requests | Team Lead | PM and Stakeholders | Weekly or Ad Hoc |
| End of Gala Evaluation Report | Project Team | Stakeholders | Annually |
| Gala Surveys | Social Media Expert | PM and Stakeholders | Annually |
Attachment F
Occasions for All Project Charter, 2020 (see attached file)
Attachment G
Occasions for All Project Schedule, 2020 (see attached file)
Attachment H
Occasions for All Risk Register, 2020 (see attached file)
Attachment I
| Deliverable | Owner(s) | Approval | |
| WBS/Time | Title |
|
|
| Weekly | Project Status Report (department) | Admin 1, Donation Manager, Event Planner, Financial Analysts, Social Media Expert | PM |
| Bi-Weekly | Project Status Report | PM | Customer |
| 1.1 | Proposal | PM | Customer |
| 1.4 | Venue List | Event Planner | Customer |
| 2.1.2 | Donor List | Admin 2 | PM |
| 2.1.3 | Budget Reports | Admin 3, Financial Analyst | PM |
| 2.2 | Event Contracts | PM Assistant | PM, Customer |
| 2.3.1.1.2 | Invitations | Admin 3 | Admin 2 |
| 2.4.1 | Donation Tax Letter | Admin 4 | Financial Analyst |
| 2.4.2.2 | Success Report | Financial Analyst 2 | PM |
| 2.4.3 | Fiscal Audit Report | Financial Analyst | PM |
| 2.4.4 | Lessons Learned Report | Admin 2 | PM |
| 3.1.2 | Donor List | Admin 2 | PM |
| 3.1.3 | Budget Reports | Admin 3, Financial Analyst | PM |
| 3.2 | Event Contracts | PM Assistant | PM, Customer |
| 3.3.1.1.2 | Invitations | Admin 3 | Admin 2 |
| 3.4.1 | Donation Tax Letter | Admin 4 | Financial Analyst |
| 3.4.2.2 | Success Report | Financial Analyst 2 | PM |
| 3.4.3 | Fiscal Audit Report | Financial Analyst | PM |
| 3.4.4 | Lessons Learned Report | Admin 2 | PM |
| 4.1.2 | Donor List | Admin 2 | PM |
| 4.1.3 | Budget Reports | Admin 3, Financial Analyst | PM |
| 4.2 | Event Contracts | PM Assistant | PM, Customer |
| 4.3.1.1.2 | Invitations | Admin 3 | Admin 2 |
| 4.4.1 | Donation Tax Letter | Admin 4 | Financial Analyst |
| 4.4.2.2 | Success Report | Financial Analyst 2 | PM |
| 4.4.3 | Fiscal Audit Report | Financial Analyst | PM |
| 4.4.4 | Lessons Learned Report | Admin 2 | PM |
| 5.1 | Project Event Report | PM | Customer |
| 5.1.2 | Project Success Report | Financial Analyst | PM |
| 5.2 | Project Fiscal Audit Report | Financial Analyst 2 | PM |
| 5.3 | Project Lessons Learned Report | Admin 2 | PM |
The post Occasions for All Gala Project Plan appeared first on My Assignment Online.