By Andrew Villafuerte
If you find the resolution too low, try the version that uses Google Video.
Back to the table of contents.
Showing posts with label communications management. Show all posts
Showing posts with label communications management. Show all posts
Communications Management Lessons Learned and Documents
What worked
- Making a communications management plan, as always, was quite helpful
- A site visit prior to committing the project is a must
- Budget for cellphone and long-distance bills
- If you are using prepaid, bring extra credits to the site
- Brochures, videos, newsletters and other media are useful for promoting future projects
- I should have given more importance to communications with the local sponsors. I should have engaged them with the nitty-gritty of the project earlier than I did.
- Workcamp 08 Communications Management Plan
- Workcamp 08 Brochures (front) (back)
- Workcamp 08 Newsletter
- Workcamp 08 Video (Google Video) (Youtube)
- Project summary for donors
- Kick-off presentation to students at the start of the project (hack job)
- Another presentation to students at the latter half of the project
- A sample of the weekly report I gave to the major stakeholders
Integration Management Lessons Learned and Documents
In the typically dry language of the PMBOK: “The Project Integration Management Knowledge Area includes the processes and activities needed to identify, define, combine, unify, and coordinate the various processes and project activities within the Project Management Process Groups.”
What worked
What worked
- Making a project charter organically. I did not follow a template, but created one from need (the way it should be). There were four sets of stakeholders: the beneficiaries, the non-profit group, the volunteers and the donors. The project charter, or at least its equivalent, is the project summary I made for primarily the prospective donors. Another “project charter” is the presentation I gave to students.
- Project management plans. E.g., communications management plan.
- Weekly project reporting to the non-profit leadership team. At certain points where I was a bit immersed in my day job, the reporting forced me to see where I was behind in the project.
- Still to come (part of project closure): news-letter and video (for showing to the sponsors and for marketing for future workcamps)
- I should have planned to manage the fundraising better. For instance, we could have asked for gifts in kind like transportation rather than just money. For projects like the workcamp, fundraising should be a section in itself in the management plans.
- Some misses in project closure. E.g., volunteer satisfaction survey, lessons learned sessions with the volunteers and the non-profit leadership team. This should have been documented as part of the closure section of the integration management plan.
- Preparing the team. I was not able to plan this well. This only turned out well because Paul, the director of Maynilad, took charge of this. Next time, how this is to be managed should be included in the management plans. I think this was very helpful in getting the team to mesh.
- Plan out fundraising better
- Plan out closure better
- Plan out volunteer team preparation better
- Project summary for donors
- Kick-off presentation to students at the start of the project (hack job)
- Another presentation to students at the latter half of the project
- Communications management plan
- A sample of the weekly report I gave to the major stakeholders
Subscribe to:
Posts (Atom)