Showing posts with label albay '08. Show all posts
Showing posts with label albay '08. Show all posts

What This Blog is All About

The first thing that gets pounded into your head as you study for the PMP Exam is that all projects must have and must start with a project charter. Being a blog which purports familiarity with project management, I couldn't but start it with one. While this blog, strictly speaking, isn't a project,* I think it would prove useful for us to follow the 400-page wisdom of the Project Management Body of Knowedge, 3rd Edition (PMBOK), and start with a sort of charter for this blog.

The first part of the project charter is usually the high-level description of the endeavor. For this blog, it is the subtitle that tries to capture this: “Project Management Shop Talk on Youth-oriented and Socially-relevant Volunteer Construction Projects.” I wish to discuss in this blog two interests I have had for several years. One is project management. After working here then here, getting PMP'd,** and leading trainings on project management, my pedantic tendencies have been piqued by this area of knowledge, and have gotten me to try to talk shop in blogosphere (where you don't see people rolling their eyes in exasperation). It's like chess geeks talking about special moves only eleven people in the world care about, but perhaps a tad more exciting.

The other interest I always wanted to write about is the Workcamp. The Workcamp is a volunteer program for university students. It usually consists of two weeks of construction work for a community in need. The first Workcamp I attended was ten years ago, where we cleaned and cemented the sewage waterways of a community of farmers in Bukidnon. That was sort of a turning point for me. Before that Workcamp I was a cynical and bored teenager. After the Workcamp, I was still a cynical and bored teenager. But a good seed was planted in me. I think I started to realize that doing good is actually fun, and being good (or at least trying to) makes one happy. Perhaps the fumes from the sewage waterways had something to do with my epiphany.

So, after I got out of the corporate world early this year, one of the first things I did was to organize a Workcamp. The project had two phases. The first phase was the preparation. We had to raise money for the transportation, food and construction, as well as look for a site and people to sponsor us there. At the same time, university students had to be marketed to, selected and prepared for the Workcamp. The site we got was a typhoon-ravaged elementary school in Sto. Domingo, Albay. Two years after the devastation of super-typhoon Reming, most of the classrooms have already been reconstructed. They had walls and roofs, but that was pretty much it. When we asked the school principal what their biggest problem was, she said that when the sun is out, the ceiling-less classrooms are like ovens, and when it rains, they are as noisy as a steel drum pounded by a death-metal drummer (not her exact words).

The second phase of the project was the actual construction work of fixing the school. There were twenty-six of us volunteers, and we stayed Sto. Domingo for ten days. What we did was to install insulators (those 10mm foam sheets with a metallic foil on one side). These are more effective in insulating from heat versus a plywood ceiling. They should also be effective noise absorbers. They are also much, much more cost-efficient than plywood. The volunteers had to become experts in using the gun tucker, which is like the regular office stapler minus its lower jaw. Instead, it has a four-inch trigger at the back which you squeeze with your hands to shoot-out the staple. You could kill someone with the thing. There were two teams of insulator-installers. We got a carpentry consultant, Mang Seming, who is a local there. He helped us make coco lumber ladders, which the gun tucker guy would stand on to install the insulators. The insulators could easily get torn from the staples, so we reinforced it with diagonal lattices of metallic wires held by umbrella nails at the intersections. The staples were for quick installation; the lattice for longevity. On our first day, each of the teams was only able to install insulators on one-fifth of a room's roof. On the last day both teams jointly installed insulators and wires for the last room in half-a-day. They declared that they had an alternate career path in case their university course does not work out.

We also painted the interiors of the classrooms. Another team was in charge of this. The painting team first scraped-off the old paint using a tool which looks like a metallic credit card with a wooden handle. They then wet the wall with “neutralizer,” which is supposed to make the paint stick better to the concrete wall. This may be slightly biased, but after several layers of latex paint, the interiors of the classrooms looked pretty close to a mac store. The Workcamp last year was painting of classrooms as well. Hans, the one who organized Workcamp '07, was with us, so the learning curve for painting didn't have to be as steep as installing insulators. In the mornings, four members of the painting team taught local kids personal hygiene (one of them is a medical student).

The Workcamp is not all work. After our workday, we played basketball or football. Every other day, the volunteers were given short talks on leadership. On several after-meal get-togethers, the Workcampers got to share their musical and comic talents, with presentations and games. For those who wanted, there were traditional practices of Christian piety. On the last Sunday, the Workcampers went to the Cagsaway ruins in Mayon Volcano, and on the night before that, friends of the Workcamp who own a restaurant in the next city treated the volunteers to a Chinese multi-course dinner.

I plan do a project like this as often as I can. It is a small project compared to what I used to do, but it is not a walk in the park. However, if the Workcamp opens up new vistas of life, service, joy and appreciation of the finer points of hammering nails for even just one fellow—the way it did to me a decade ago—it is undoubtedly worth it. I plan to blog about the “lessons learned” in the project—another practice that gets hammered on you when trying to be a PMP. All contents of this blog is licensed under CC-BY.

I could not talk about the Albay Workcamp 2008 without mentioning the people who made it happen. Thanks to our hosts, Dr. Manuel Lorenzo and Jess & Dette Abrera. This Workcamp is dedicated in memory of Dr. Patria Lorenzo. Thanks to our major donors—the anonymous friend of Fernan and Karlo, Metafoam of the MaraƱon family, and the Foundation for East Asian Development (FEAD). Special thanks to Mr. and Mrs. Jerry Gregorio, Ma'am Reaso, Sister Merit, Architect Cesar Olmos, Josef Lim for the posters and brochures, Fujitsu, Philtranco for the discount, Mayor Boss Boy, Glenn Nares, and all the wonderful people of Sto. Domingo. Salamat!

Of course, this Workcamp wouldn't have been successful without the teamwork, creativity and hard work of the volunteers: Mark, Michael, Kevin, Fritz, Not-Not, Arvin, Kiko, Erold, Meyrick, Andrew, Aibar, Jonathan, Luis, Carlos, Kaiser, Cedric, Gian, Jezer, Jon, Kenneth, Jeremy, Miguel, Raffy and Charles. I hope that ten years from now, there'll be twenty-four new blogs that talk shop about project management of Workcamps :)

*The PMBOK defines a project as “a temporary endeavor undertaken to create a unique product, service, or result.” “Temporary” here means you have the intention of ending the undertaking at some point, and you have some idea when that point is. This blog doesn't have those characteristics. This blog, strictly speaking, is operational work. This is the example I usually give to differentiate projects and operations: a wedding is project (even the typically week-long Hindu wedding eventually ends); marriage is operations ('till death do us part).

**The pun, to a certain degree, is intended.


Back to the table of contents

Fundraising Lessons Learned

In the Philippine context it is more effective to ask donations from a wealthy few than to ask from a broad base. We actually concentrated on the latter approach. But the biggest donation (almost half of the total expense) came from a businessman from the locality where we did the Workcamp, a friend of one of our champions (I only suspect this since the person asked to be anonymous, and not even I know who the friend of my friend is).

Have funds for advancing pledges – this is especially applicable for donations from companies. They usually have bureaucratic processes for donations and would usually ask for a Deed of Donation so they could apply for a tax exemption. This takes a while to process. The earliest you can collect the donation might be after the Workcamp.

Back to the table of contents

Procurement Management Lessons Learned and Documents

What worked
  • Have more than 1 supplier
  • Show vendors that you are conscientious about prices of materials –If your project is non-profit, people could think that you are not price-conscious. They can jack up prices if so. One must be price-conscious both in fact and in appearance, since one's ability to manage finances is directly proportional to the impact of the project.
  • Pay in chunks but regularly – I was warned by our host not to pay the caterer in full immediately. Instead, we were to pay, ideally, for each day of catering. The reason was that the caterer may not be used to managing the volume we required. If we paid in full the first day, it might happen that they give us fiestas for the first five days and starve us the rest of the Workcamp...
  • Certain vendors need to sign receipts – No need to do this for official establishments (e.g., the hardware had their own receipts), or for vendors which receive small and regular payments (e.g., the jeepney we hired to bring us to and from the site everyday). However, it proved to be very helpful for the payments to the caterer, since the payments were not uniform (they were based on head-count which was fluctuating daily). The procedure of signing a receipt for each payment forced the vendor to understand the way I was paying them. I gladly explained to them the payment plan one night when they approached me. We avoided misunderstandings (which are always nasty when it comes to money).
Daily food expense tracker and receipt

Back to the table of contents

Risk Management Lessons Learned and Documents

This was the most sloppily managed aspect of the Workcamp. I cannot use my being a first-timer as an excuse. I could have organized a risk identification workshop with the people with Workcamp experience. But I didn't. So to make up for it, here's a post-project Risk Breakdown Structure for the Workcamp. I'm embarrassed to say this, but during the planning, I only identified two (2) risks, a storm and not having sufficient work for the volunteers (I'm an optimist). This RBS has more than 60 risks. It will be useful for the next Workcamp.

post-Workcamp Risk Breakdown Structure (download pdf)

What I'll do next time

  • Reuse this RBS
  • Have a risk identification workshop with my core team
  • Come up with a risk register with options for mitigation and contingency. See an example of a Risk Register.
Documents
Back to the table of contents

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
What didn't work
  • 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.
Documents
Back to the table of contents

Cost Management Lessons Learned and Documents

What worked
  • Overall estimate was accurate – The overall cost of the Workcamp was within +5% to -5% of the estimate (including risk reserve). I expected higher, since this is my first time to manage a Workcamp. The category estimates, however, were more inaccurate. The overestimates and underestimates evened out, so the overall actual cost was near to the overall estimate. I consulted architects and construction contractors for estimates of materials given certain dimensions and plans, and asked suppliers for estimates of the prices of materials.
  • A glorified excel sheet – I have discovered an enhanced version of excel. It is extremely mobile and energy efficient, has an infinite battery life, no license cost and multi-user (with an option for concurrent usage). It is extremely useful for tracking expenses.
a future version of excel

  • Not carrying all the cash – The site was 30 minutes away from a city. And we brought our own van. So instead of carrying cash, we deposited to several ATM cards, and just withdrew cash as needed.
  • Included management reserve in the budget (buffer for unknown risks) – Part of the budget was for unknown risks. I pegged it at ~25% of the budget, since this was the first time I organized a Workcamp. This was also useful for positive risks (ie, opportunities). Instead of painting just one classroom, we decided to paint three.
  • Having some accounting background – I did accounting work for a non-profit for around two years before this Workcamp. Since I did not have any formal accounting training, those were two painful years. But accounting, it turns out, is one of the most useful things in life. For the Workcamp, it was quite useful. Creating the financial reports were straightforward, but it wouldn't have been that simple if I didn't acquire the habit of accounting for each single centavo.
What didn't work
  • Category estimates were way off the mark:
  • Food: 15% lower than budgeted (we were 27% fewer than expected). Food was 32% of the total expense.
  • Transportation of volunteers: 50% higher than budgeted. In the last minute, I decided to bring only 1 van. Most of the volunteers had to take the bus. I was supposed to be the driver for other van, but I did not want to have on my shoulders the risk of driving teenagers in a 13-hour drive. My estimate was also not sufficiently conservative. Transportation, like food, was 32% of the total expense.
  • Transportation of materials: I was not able to anticipate this. This ended up being 4% of the expense.
Documents
Back to the table of contents

Time Management Lessons Learned and Documents

What worked
1) Combined school and project calendar – combining important schedules made it easier to plan
2) Detailed and comprehensive schedule for times with a lot of interrelated tasks by several people – Zooming-in the most critical days (getting the materials and volunteers from Manila to Sto. Domingo)
3) You don't need MS Project!
I prefer to use the simplest tool I can use to accomplish a task. In this case, I used a spreadsheet for the schedule. In my opinion, you only need to use MS project (or other specialized PM software) when:
  • There are a lot of tasks distributed to many resources
  • You need to make repeated computations that are automated by PM software (e.g., Earned Value, resource billing)
What didn't work
1) What is useful for the project manager may not be useful for others - The detailed and comprehensive schedule was very useful for me as a project manager. However, it did not work for one of the people responsible. The leadership personnel exchange at the middle of the workcamp was a bit complicated (a four-man exchange with a requirement that at least two are always present in the site). I had to go home 1 day earlier than planned :-( since there was a miscommunication. I should have made a clearer schedule model just for the personnel exchange.

Documents

Back to the table of contents

Scope Management Lessons Learned and Documents

What worked
1) Using mindmaps and mindmapping software for the work breakdown structure (WBS).
  • Very useful for project control. I colored the completed tasks green. This gives a very visual way of seeing how far you are in the completion of the project tasks.
  • Gives you an idea of what type of work to expect. For this project, half of the WBS was taken up by logistics. This was a pretty accurate prediction of the actual project work.
  • The software I used was Mindman, which has a 1998 freeware copyright. Mindmapping software seems to be a commodity; there does not seem to be significant differences between mindmapping software. Mindman is one of the first mindmapping software I got hold of, given by my manager back in P&G. It never occurred to me to look for another one, not because it is a brilliantly written software, but simply because I did not feel the need for anything more.
The WBS of the Albay Workcamp
See how the logistics branch takes up half of the WBS
Download the PDF of this here


2) Have some rigidity with the scope...
  • We pinned down certain aspects of the scope like venue and dates as soon as possible. These are needed for marketing, fundraising and some of the logistics. Changing them entails a lot of replanning and rework, so it is very important to agree on these as soon as possible with the major stakeholders. I worked with some very opinionated people, so I had to defend the scope a few times from brilliant ideas :-P
3) ...but some flexibility as well
  • One has to remember that the purpose of the project is not really to fulfill the documented project scope to the letter, but to make the vision of the project a reality. In this case, the purpose was not really to “install ceilings to damaged classrooms;” it was to help a community and at the same time form young men through that act of helping. My natural tendency was zealous adherence to the documented scope, schedule and budget. Fortunately, I had some iron-willed people with me who counteracted my rigidity. The original scope was just painting of one classroom. We ended up painting three. We went over-budget, but it was worth it.
  • I was more open—quite enthusiastically open—to innovations in solutions. For instance, I thought we could use insulators rather than plywood to act as ceilings. These would be cheaper and better at insulating from heat. I had some resistance from a risk-averse stakeholder. But when one of our informal consultants (a construction expert) suggested the same thing, I shamelessly made use of his authority, and we ended up with the insulator solution.
  • One has to be even more flexible using solutions one is not familiar with, like using the insulator. Since we were not planning to put a plywood ceiling to cover the insulated roof, the flimsy insulator attached to the wooden frames with tiny staples had to be reinforced. Many decisions had to be done on the fly. The original option was to cover it with chicken wire. It would have cost us around 25% of the total budget if we did that. I decided to have us make our own lattices using aluminum wires held in the intersections by mushroom nails. The regular mushroom nail turned out to be too difficult to drive in the wood (for our untrained arms hammering up side down). Fortunately, we discovered a thin type of nail with a plastic “mushroom head.” No one else seems to have been using it, so the hardware store was only too eager to get rid of that old inventory (I think we got it at a discount). It worked perfectly. Most of these decisions were made in the hardware store as we took a look at the different materials available. It was fun. I almost felt like McGyver.
Documents and software
1) Workcamp 08 Work Breakdown Structure (WBS) in PDF
  • Includes post-Workcamp additions (unanticipated tasks)
  • Historical WBS's are useful for planning similar projects
2) Workcamp 08 Work Breakdown Structure (WBS) in mindman
3) Mindman software (shareware)

Back to the table of contents

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

  1. 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.
  2. Project management plans. E.g., communications management plan.
  3. 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.
  4. Still to come (part of project closure): news-letter and video (for showing to the sponsors and for marketing for future workcamps)
What didn't work
  1. 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.
  2. 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.
  3. 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.
What I'll do next time
  1. Plan out fundraising better
  2. Plan out closure better
  3. Plan out volunteer team preparation better
Documents
  1. Project summary for donors
  2. Kick-off presentation to students at the start of the project (hack job)
  3. Another presentation to students at the latter half of the project
  4. Communications management plan
  5. A sample of the weekly report I gave to the major stakeholders
Back to the table of contents

Project Initiation – Gathering Lessons from Previous Projects

What worked
  1. Asking people with a lot of experience organizing workcamps (I asked two guys who have lead a non-profit called UCF)
  2. Asking “what questions should I ask?”
  3. Including project management work, particularly gathering of lessons learned from similar project in the past, in my work breakdown structure
  4. The experienced workcamp PM's having documentation (see below)
  5. Having contacts with different expertise (e.g., my architect friend helped a lot in estimating the materials needed)

What I'll do next time (or now)
  1. Paying forward—what I'm trying to do with this blog. The handbook, templates and notes of experience that UCF provided was extremely helpful. I'm hoping to share my lessons learned as well.

Documents
  1. UCF Workcamp Organizer's Manual (An excellent document. Thank you Jun!)
  2. Questions to ask the prospective hosts (compiled from the organizers manual and correspondences with UCF)
  3. Sample letter to hosts (from UCF):
I am currently scouting for possible volunteering activity for Taiwanese and Hongkong Chinese volunteers on January 2008. The Taiwanese volunteers are organized by xxxx, while the Hongkong Chinese are organized by xxxx.

I would like to seek your assistance in exploring volunteering opportunities in Cebu. I am looking for organizations (NGOs, Pos, Community Orgs, LGUs) who are willing to host volunteers for a few weeks to help in their programs and projects. For your reference, mentioned below are the preferences of the volunteers:

1. Type of work: basic manual work not requiring specialized skills such as digging ditches, painting, basic construction work, etc.

2. The manual work should be part of a project of a local organization of any of the following kind:

a. Social projects for cultural minorities, children, and elderly people.

b. Environmental projects such as tree-nurseries, tree-planting, cleaning of rivers and the sea, construction of educational paths in protected areas.

c. Educational projects such as classroom repair and renovation in schools.

d. Reconstruction projects such as repair of public or community buildings destroyed by disasters.

e. Rural development and renovation projects such as community infrastructure work.

f. Low-cost housing for under-privileged families.

g. Cultural heritage preservation (with assistance from professional experts) such as renovation of historical structures, repair or renovation of churches/chapels.

3. Group accommodations for 10-15 boys of a dormitory-type. It could be a big room where they could lay their sleeping beds with toilet facilities.

4. Food could be prepared by local cooks for breakfast, lunch and supper.

5. Tap water for toilet use, preferably.

Please let me know of possible work activity (scope of work and estimated cost of materials). Then we can do an ocular site visit. During the site visit, negotiations could be made to identify the job description, cost of materials and other things.

University Center Foundation (UCF) is a private NGO based in Metro Manila. Among its programs is the International Volunteer Service Program (IVSP) where UCF coordinate with some foreign organizations to undertake volunteer projects that could benefit local communities. For more information, please visit our website, http:\\ucf.ph.

Thank you for your time and best regards.


Back to the table of contents