Field Project – Cupcakes for Charity

Project Audit Report

(MGT598, MBA X)


“Cupcakes for Charity – Fundraising for the less privileged”

 Project Description & Analysis

“Cupcakes for charity” was the collective brain-child of our team when we were assigned to conduct a charitable event for the course. The event fulfilled multiple objectives:

  1. Apply project management principles, as taught in class, to a real-life project.
  2. Spread social awareness of our selected charity – what they do and how they do it.
  3. Raise funds for a charitable organization.
  4. Ensure that we enjoy ourselves.

Although we were quick to define what we wanted to do and how we wanted to do it, a structured approach was followed. At the outset we created a formal proposal for the project outlining the charity, what we wanted to do, our objectives, a brief plan of action and the perceived road blocks. The next step was to create an implementation plan that provided further details on how we were planning to accomplish our objectives. This involved detailed definition of the sequence of activities plus identifying the work packages for each team member. We also had a support or rather back-up for each team member in case the original team member was unable to perform the task for any reason. So, for example, Syed’s work package included venue and stall. Hamza was in-charge of arranging the Charity and the Sponsors. Further to that, Mahmood was back-up on the Venue. Presented below is a snapshot of the final definition of our project plan:


Now that we all had a clear idea of what needed to be done, we prepared a risk management plan for the charity event. This document contained a list of 12-odd “developments” that could potentially be detrimental to our progress. Each “development” was ranked depending upon its how critical it was (“1” considered as the most critical) and associated with a strategy for mitigation plus a contingency. Mitigation of the risk identified specific actions that would be taken to ensure it did not threaten progress; the contingency would provide an alternative to safeguard out interests. So, for example, venue identification was identified as the riskiest activity and the team agreed that mitigation lay in identifying a location that was easily accessible and well-known on the island. One thing we might add is that although we had a contingency plan, it wasn’t very thought out. With the initial response that we got from Seef Mall, the probability on relying on contingency was very low. As such, we did not take into account the low demand that we will face. So if we had a proper thought out contingency plan, we would have had an option to lower the number of cupcakes from the vendor.

Planning aside, we had to move quickly due to severe time constraints. The project completion date was approximately two weeks away coinciding with the end of this course. The first thing we approached was the venue and got approval in principal from Seef Mall. In parallel, we engaged with specific firms apprising them of our future event and exploring the possibility of getting sponsorships. We also spoke to a few bakeries to determine the level of discounts they were willing to offer if we purchased merchandise on a bulk basis. This phase of the project was the most crucial since the choices here would determine our capacity at a later stage.

Unfortunately, Seef Mall started delaying and became non-responsive a few days before the event and consistent with our contingency plan, we managed to obtain space in BIBF. In the meantime, our drive to obtain sponsorships bore fruit and we raised BHD 500 cash (~$1,300). Some organizations also contributed in kind – the stall rental cost was waived (BHD 400 equivalent value over two days) plus we received a batch of 150 free cupcakes.

The cupcake sale spanned two days during which we sold more than 400 cupcakes. As a small token of our appreciation we also gave away cupcakes to our various sponsors who helped us make the event possible.

Lessons Learned & Takeaways

Having been through every stage of the event ourselves, there were a few takeaways that we felt could be beneficial for the future:

  1. Setting Milestones – It is of utmost importance to set clear milestones and adhere to them. In our case, we had extremely limited time at our disposal and realized that any slippage could easily jeopardize the entire project. Clear milestones and deadlines need to be established upfront and adhered to so that there is no ambiguity of what is due when.
  2. Progress Monitor – Project progress and overall development needs to be established on a frequent and regular basis. This can be easily done through clear communication without even meeting face-to-face. If ignored, slippage can become uncontrollable very quickly putting the entire project at risk of failure.
  3. Activity Slack – It is a prudent habit not to depend on slack times. Although the implementation plan might show slack in some activities, this can quickly disappear especially if those tasks also involve external parties.
  4. Try to complete tasks as soon as possible although there may be slack available. Given the number of externalities in any project it is difficult to predict what and when something can go wrong. Doing this will ensure available time for any other activity that requires attention.

Advice for Similar Events

Our advice to other teams attempting to conduct a similar event would start with the list of lessons learned in the previous section. In addition, we would recommend the following to ensure a smoother implementation:

  1. Whenever any third party is involved, ensure there are written agreements so that neither party suffers due to any untoward event. In our case we made the mistake of not taking this route at the time of finalizing the venue. As a result, the Seef Mall management failed to appreciate our sense of urgency in the matter.
  2. Try to finish everything as soon as possible. Slacking is dangerous. Usually, a plan is as good as its implementation. But a plan cannot incorporate unforeseen risk as you as a planner are not very experienced in project management.
  3. One should have clear understanding with the charity organization as the things they are responsible for and their continuous support on the day of event is very important. Choosing a Charity that you are going to represent is also a very important decision. Charity and their causes have inherent fund raising power. In our case, the charity we chose had no specific cause and as such it was harder for us to rally support.


7 6 5 4 3 2

Team members:

Syed Ehsan-Ul Hassan

Mahmood Abdulla

Asim Qureshi

Mayukh Chaterjee

Hind Abdulla

Hamza Haroon


8 thoughts on “Field Project – Cupcakes for Charity

  1. It looks like this was a nicely planned, organized, and executed fund-raising project. It also includes lessons-learned and recommendations for executing similar future projects. It liked how the work was evenly divided for everyone in the group and hopefully was carried out with a big success.

  2. This is a simple and wonderful idea that I’ve seen work many times whether it has been to raised money for a HS sports team or raising funds for a charity. Of course your plan was a lot more detailed as the former. Considering the time constraints, I think you guys did a wonderful job in raising funds.
    I liked setting of the detailed plan early in the project phase as that sets clear direction for the remainder of the project as well as makes it easier to divide out tasks between the individuals on the team.
    I also liked the takeaways from the project, primarily the progress monitor as it goes hand in hand with the detailed plan to make sure you’re staying on track.
    Advice section will come in handy for us as you mentioned to have contracts in place. We’ll possibly be working with multiple venues and agencies so it is a good idea to have a contract in place to avoid any last minute changes as you all suffered!
    Great work!

  3. Thank you for your lessons learned advice and recommendations for working with a third party; these are all valuable suggestions for future teams. It seems that it would have been valuable to have a more flushed out contingency plan, that will be another recommendation that I will be sure to use on our project.

  4. I thought your lessons learned were great! I hope that our team uses the great advice that you have listed regarding slack time and a more detailed contingency plan.

    I feel continuing to move ahead with a project’s tasks even with available slack time is paramount to increasing the overall odds of success given no team has a crystal ball regarding future hurdles.

  5. The Cupcakes for Charity project seemed very well organized and executed. The project description and analysis was greatly detailed and helpful. It was nice to see the objectives layed out up front with respect to the charity, the project, the group, and the individuals. Everything seemed like it went well, aside from the delay from one of the parties, but a great point in highlighting that in the final additional advice section. The lessons learned and takeaways was much appreciated. Great work and thank you for sharing.

  6. I Thought The Cupcakes For Charity Project Was Well Thought Out And Demonstrated Strong Project Management Skills. The Risk Management Plan Helped The Team To Identify 12 Risks, Prioritize Those Risks, And Mitigate Them. The Formal Proposal For Project And Project Plan Helped The Team To Organize The Project From A High Level. The Lessons Learned And Advice For Similar Projects Were Insightful And Will Help Future Teams As We Work On Our Field Projects.

  7. I thought this was an interesting project. It was a great idea to take potential road blocks into consideration. I have participated in many projects where lessons learned were not taken into consideration and it resulted in the same issues arising. The concept of selling cupcakes in the Bahrain caught me off guard, I wouldn’t have thought of cupcakes as a hot item there. The comment about slack was especially insightful. As we learned from the capsim exercise, forecasting is very difficult to do.

  8. After going through this project and reading their project plan and project takeaways there is much to be learned that can apply to any project plan. The first thing to take way is the pre-planning and the organization needed to be able to monitor every aspect of the project. As the team pointed out “setting milestones” is a key factor in any project in order to be able to judge stage completion and status of the project as a whole. If the project is to be complete there is several milestones and mini deadlines that need to be met in order to be successful in the end. The next and most important takeaway in my opinion is to be able to monitor the progress of the project and be able to determine the level of progression of every milestone and correct that aspect of the project as needed. If one milestone or aspect of a project is slowed down or ignored in any way, it can cause a chain reaction jeopardizing the entire project as a whole and the end result.

Leave a Reply

Your email address will not be published. Required fields are marked *