Project Initiation - It is only a start, or is it?

So you’ve just heard through the grapevine that a project you always wanted is going to be yours! You are going to be “the” Project Manager of this big, beautiful and popular beast everybody was buzzing about. How nice and exciting for you! Once the initial excitement is gone you switch to reality and all those uneasy thoughts about starting the project on the right foot. Right?

Project Initiation

We learned by now that the Initiation is the most important phase of any project. We are even told that with a good start and good high level planning one can consider half of the project complete. No pressure here, but it is more important to do a right project, than to do it right! So why is there so little literature available about this phase? Maybe it is due to the realization that you need to apply more common sense and less methodology, and there is no tool that can guarantee you a good start if you don’t have enough expertise, or if you are not guided by other experts on your way.

Since we are talking about common sense, it is up to the individual project manager to find the best way to deal with this most important, but also most grey area of his project. By the same token, the tips that I am suggesting here are just a collection of lessons learned I acquired throughout my informal and formal career as a project management practitioner. If I succeed in helping you avoid even one pitfall in your next project then this article will be worthwhile.

You will find many of these tips familiar and something that you are already doing and there are for sure some other tips not mentioned here. If so, I am inviting you to write to me about it and if I collect enough of additional material I promise to write about it again. Please email me at durica@sympatico.ca.

Before the project - Who I am and where am I?

First, you need to understand the culture, the vision, the mission and the project management structure of your organization. Apart from a myriad of technical and soft skills you have to posses, it equally important to understand the business side of your organization and your department.

Before you start with any project you need to understand the role you have in your organization. In addition, you need to know the position you are on your project management career ladder. The lower you are on this ladder (not that much experience or you have been recently hired), the more time you have to spend preparing for the project. This is ironic because the less experience you have, the more susceptible you are to the influence of others, which can sometimes be negative and hold you back even more. If you are lucky and have good mentors with enough power you will find yourself in the fast lane to potential success. On the other hand, if you are influenced by others in a counterproductive way, or have nobody to help, you will have to work much harder, but will gain bigger rewards in the end.

Before the project - What are my tools and techniques?

After you have the right orientation of your position in the organization, you need to look for your tools that will help you in your project management work. This is a very important phase and you should never rush through it, even if you are told otherwise. Just as you may not know the tools that a mechanic uses to fix your transmission, those around you may not realize what tools you need to develop your solution into a project.

The sophistication of your tools, or methodology and processes will greatly depend on the organizational structure and its maturity. The advantage of project- oriented, PMO-enabled and mature organizations is that they usually have a myriad of project management related tools and processes. A disadvantage is that they may be strict and impose them on you even if you feel that an alternative would better suit the situation.

If you are in a small, functional or a weak matrix organization, there most likely is no formal project management methodology. If you are in an average organization these days you probably have at least a Charter, Plan and Status Report templates. If you don’t, create them! Use this advantage and your creative senses to be a pioneer in helping establish a proper methodology for your organization.

The Project Charter should be your bible and your best ally. It should state clearly who is responsible for what on the project. This statement will frequently become very handy for some people who have short memories, unintentionally or otherwise.

The Project Plan should be your best friend and an all–in-one daily report, which you always have to keep in harmony with the Charter. Start the Plan like an empty book. Begin with the Preface (taken from the Charter), followed by the Table of Contents (written during the planning phase) and then Chapters will be written during the execution phase.

Your weekly Status Reports/Meetings are too important to miss, even if you are told otherwise. Those reports/meetings have a dual purpose as a great monitoring and control tool. They keep you in check, as you HAVE to know where your project is at all times and communicate it to others. While you are preparing for a status report you are also on top of your risks, issues, and of course status (time, scope, resources, and quality) of the project. If you are not required to have weekly meetings you should push the status reports in weekly e-mails to your management, sponsor and the client, at the very least.

It is very important to adopt project management standards, methodologies and procedures that work well in your circumstances. I understand the urge we all have to make shortcuts and try avoiding some stuff we find boring, such as documenting emails you get from your clients, or indicating in the Plan the exact outcome of your project and accurate measures of its success. What I discovered, however, is that my best and easiest project was the one where I applied project management methodologies taken from the industry best practices and tailored to my organization. I then followed, religiously in fact, the self-imposed process even in cases I was not asked to.

Finally, once you establish the methodology and processes, resist using Microsoft Project or any other project management application yet at this early stage. As I mentioned already, once you pass the stage of making sure that your project is right you want to make sure the project is done right. Make sure you establish a stable baseline first before entering your artefacts into the system to avoid the inevitable re-work imposed by changes.

Starting the project

It is rare, unfortunately, to have project managers involved from the very beginning of the initiation phase of projects. The early involvement from the business point of view would be of an enormous advantage to any project manager, as they would have better understanding and appreciation of the problems and opportunities they are supposed to solve.

If you are not that fortunate and are just being told to start your project today and finish it tomorrow, don’t worry. Try to put yourself in a position of people and departments affected by the problem and you will have a much better chance to lead your project and your team into a successful solution. By believing strongly in the project objectives and knowing the extent of the achieved benefits you will not even notice the burden of the responsibility you are taking. This strong belief will be an invisible shield that should comfort you on your way to success.

It is always good to know a little more behind the boundaries of your own project. The initiation is the perfect time and probably the only time to gather this knowledge. Once you are in, let’s say business requirements stage and you would like to know more about another project that can dangerously impact yours, I bet you the following will happen:

a) You have no time - You are up to your neck with your project
b) “It is not your business”, you are told and “Don’t you have enough in your own project?”

It is important to understand the position that any project has in an organization. Since the business and technical sides are usually acting in isolation, every project’s role is to merge these two sides effectively, by acting as a transition of its business objectives into its technical implementation. See Figure 1.


Figure 1 – Project is a strong connection between business and technical sides in an organization.

Hence, your project’s objective, and the reason you have this job after all, is the connection between a business need and technical delivery to accommodate that need.

If you have at least one of your project constraints flexible to some degree you will manage the project. If you have all these constraints fixed you will need to manage your stakeholder’s expectations to get some needed flexibility in your project. In order to manage them you need to understand them. The most important mission you have as a project manager is to put those stakeholder’s expectations into quantifiable statements and manage them within the boundaries of your own project. It is like your project is in a cloud floating above your organization, see Figure 1, and your goal is to clear up this cloud and land the project safely to the best place it can be between business and technical sides. You do not want to be lost in that cloud yourself, hence the reason to start questioning.

Ask questions, and then ask some more

As I indicated earlier, the most important fact to determine at the start is if your project is the right one. So you need to ask questions to find out. The other truth, which may be good or bad news depending on your inclination to be less or more technical, is that you will always have to ask questions throughout the project. What is happening, though, is that the more your project is advancing, the more and more questions others will ask you. Your exclusive opportunity to question others has a short timeline, so you need to use it to your advantage.

The initiation and planning phase of a project has a strong resemblance to the work that your Business Analysts are doing. They start with the requirements elicitation, including negotiation, validation and management of collected requirements, followed by test cases and so on. Similarly, you are determining the scope of your project, starting with interviews and meetings with your stakeholders; you gather and validate the scope and other constraints; you acquire the additional knowledge by research activities and finally you and your team document and manage all project-related artefacts. It is just that your scope is multi-faceted, with more dispersed activities across more functions, you are dealing with more stakeholders and finally you have more responsibilities. Even the responsibility for the requirements your Business Analyst is doing is also yours.

Ask as much as you can, but have your questions well prepared in advance and be careful about taking other people’s valuable time. In your wording you want to get your point across as a confident expert. So you will not say to your sponsor: “Are you sure that this project you initiated two years ago, spent so much time pushing through, started only briefly last summer and failed, is really right thing to do?” You may think that, but you need to say just the opposite; how you are honoured by this task, how you appreciate what management has done with this project so far and how you are the right person who will help them with this project, no matter how challenging it is.

You may have a Charter ready for you, you may even be involved in its creation and/or validation, or there may be no Charter at all. In any case, you need to have a written document, which is a contract between you and your management. By accepting the Charter you are taking responsibility to deliver, whatever is stated there. So you need to understand clearly what has to be done, why, who is doing what, who is responsible for what, when, how much it will cost and most importantly how anybody will know if the final outcome is success.

I can’t stress this enough, this is your best chance to probe, ask questions, negotiate your project’s position, address the existing organizational risks and not only understand, but also embrace completely its objective. All this, so you will be prepared to defend fiercely the path on which you and your project are going.

What to do and Why?
To be able to feel good about the project and feel confident throughout you need to ask your sponsor and client what has to be done and why. There are many other sub-questions on this topic you may ask, such us:

a) What will happen if this project is not done (in both quantitative and qualitative terms),
b) Why is it better if it is done and by how much,
c) In the scenario this project is a no go what would your workarounds be
d) Etc.

The more you know, the easier it will be when the tables turn when those same people, in addition to everybody else, ask you what you are doing and why. You better have an enthusiastic and uplifting response! The response will not be the same all the time as it is impossible to finish an average project without any changes. So when assessing any change request that will come your way you need to ask yourself what you are doing and why, before determining how the proposed change will affect your course.

In addition to knowing the objective of your project, you need to determine the success factors, i.e. what are the metrics that you should apply in order to know if the outcome is success. One of questions to your sponsor and client would be what their expectation of this project is and how exactly they would know if its outcome does not meet their expectation. If you can quantify what and why, you already have the answer to this third piece of the puzzle. For example, if the goal is to decrease customer calls for 20%, you need to know by when and determine other logistics about the benchmarks and you will have the answers.

How much will it cost?
This is an obvious question and I do not need to spend much time on it; pun intended. The most important discovery here is to determine the risk adverse factors from your sponsor in regards to financing. Is there any flexibility to increase the budget figure if necessary, how much, when etc. You need to know how much room you have for your project’s dance.

Who?

This is the trickiest and most risky area. If you do not ask proper questions here you may end up regretting it down the road. Starting with the Project Charter you do not want ambiguous statements and confusing roles. At a minimum you have to insist on clear statements for roles of yourself, your sponsor, your client and any other manager, or coordinator for any roles they will have on your project.

You should insist on having only one client. If not possible then you need to split the objectives to the appropriate clients as the Champions. Do not accept two clients for one requirement! It is same as you would give a project to two project managers, with absolutely same roles in it. Who will then be responsible when something goes wrong? And for sure it will, because it is not clear who will do what and who will not do what. Especially avoid having two clients with the opposing views, or even worse a sponsor and a client in conflict!

In one of my projects with the objective to enhance an application, one client insisted on adding an interface component, while the other fiercely resisted having that same component! What was interesting, both clients were telling me: “You should not forget that I am your client so you should do as I tell you!” After initial frustrations I finally negotiated one primary client, who was responsible for scope determination and approvals, while she negotiated separately with the other client. Your sponsor can also help to make sure these boundaries are set. To be safe you always need to know who has the last word and clearly state it, starting from the Charter.

At the very start of your project you need to have a sense of resources availability. Companies usually do not have the capacity planning in that regard, so you need to determine as soon as possible what your playing field is. Knowing you do not have appropriate or enough internal resources you could start asking your sponsor about it. It is very common for the sponsor or your manager to grossly underestimate resources and you can’t blame them, but since it is your project you need to make sure to cover all the bases for the project.

With what?
System resources are especially tricky, since they are not visible like people and can be easily forgotten. There may be some essential systems or parts of the systems that are most likely going to be unavailable when you need them for your project. If this is out of scope of your project you need to clearly identify them as the organizational risks as opposed to your project’s risks. Why would you take responsibility for something that is not yours and you do not have a control of? Don’t you have enough risks and responsibilities already?

For example, if your test phase depends on acquiring a test server, and the acquisition is not in your scope, do not write in the Assumptions section of your Project Charter, or worse Project Plan, something like: “It is assumed that Test server will be up and running a week before Test Phase starts”. If this is the only action you take nothing will happen. Even if you escalate this issue 2-3 weeks beforehand to your sponsor saying that the Test server is not ready, it will be of no help. You will have to defend your inaction, forgetting it was not even your responsibility in the first place. Start immediately with a list of the existing organizational risks, if such a list does not exist already.

Clearly indicate what resources have to be purchased/installed/configured/refreshed, by when it should happen, and most importantly, who will be responsible for this to happen. You will still monitor this activity, as it is impacting your project, but rest assured that whoever is responsible for this to happen will make it happen. If not, any change in your project status resulting from this activity will not be your responsibility.

Where and When
If you are aware what your role and your organization/department role is this part will be obvious to you. You will know by this time where you and your project are in the bigger picture, what other activities, as well as capital and/or operational projects are taking place at the same time as your project and the time constraints of your and other projects. You will also know what your role is in acquiring the best team you can get, as well as other resource dependencies that you have to watch for.

I already mentioned that you have to be aware of organizational and your project risks so you will add some of these in both lists of risks/issues. It would be good to point out to your sponsor and client that ultimately the organizational and/or departmental well being is your top prerogative and any serious changes in their course that impact your project will be taken into account accordingly, even at the expense of you project, if it needs to be.

At this point you should be busy and dig out any historical information, lessons learned and best practices from documentation available in your organization. If that is not available you should go through requirements elicitation process to gather this information by asking appropriate people.

And finally… how?
After you have answers to every other question, this one will address how you go about doing your project. This one is the easiest because you are very much in control of the way you do your job. Once you know what the objective is, who the players are and what tools you have, it is much easier to determine how you can achieve the objective, how to approach stakeholders and how you use your existing or acquire new project management tools.

Conclusion
There are many other questions that you could and will ask than the ones I mentioned. In order to address this topic in more detail, one would need to write a book and I am sure those books already exist. The intent of this article is to help you be aware of your environment so that you are well prepared and gain much needed confidence for the success of your project. Only if you know what you are doing, why, with whom you are dealing with and where, you will be well prepared for surprises on your way. With this awareness you do not need any luck on your project, but I wish you the best of luck anyway!

Niagara, Ontario, Canada, picture taken by Azra, 2007

The TO DO LIST – The essence of every project management endeavour

We all know that the planning phase is an absolutely critical process of every project life-cycle, regardless of its size and complexity. Moreover, every project manger understands that the success of a project depends, in major part, on how well the planning is done. Planning is usually the busiest phase and every good Project Manager knows that his project is at stake if the planning is not taken seriously throughout its lifecycle.
The complexity and the scope of the planning process in every project depends on the size, the budget approved, the scope, the three constraints, the organizational maturity and many other factors .

In order to do a formal planning process there is a myriad of different tools and techniques, with hundreds of software applications on the market available to project managers, with or without the cost. What is in common with these tools is that they contain a scheduling plan, which will help to determine what activity will be done and when, and who is responsible to carry it out. These tools range from the more sophisticated, such as MS Project to the very simple, such as a good old Excel.

My intent here is not to suggest that you need another software package, or to try to explain a complicated planning technique. I am leaving this to other professionals who are more qualified for such an endeavour. What I would like to get across is a tool that you have been using all along in your daily personal lives but may not be aware of its power. This tool has been around for a long time. It is simple, easily communicable and it won’t cost you a thing. I am talking about the TO DO LIST.

Throughout our lives we may have written hundreds, or even thousands of these lists of all shapes and sizes. These quirky creatures are usually jotted down, sometimes carefully and slowly, more often in a hurry, sometimes on a piece of paper and even in some instances in electronic format. There is probably no media type out there which was spared from our relentless to do lists. Apart from the most common writing on a piece of paper, there are other media, like an empty white border space in a newspaper or magazine, used envelopes (hopefully), tissue paper etc. In fact, our pre-historic ancestors wrote their to-do-lists on the walls of their caves.

For those of you who still believe that you will not waste your time by reading this to the very end, I want to present my own weekly groceries-menu-to do-and-anything-else list. I do not remember exactly when I started with this kind of list. Maybe it was when I started a family more than twenty years ago. I can assure you that this peculiar habit of mine helped me in organizing my daily life. What is more, years later, when I learned about formal project management disciplines and became one of the project manager species, this planning routine helped me even in my professional work. If we organize our projects in the most effective way and save time and money for our organization, why not do it for ourselves first? If we are more organized and efficient in our personal lives, which leads us to be more confident and happy, the same attitude will become only natural in our workplace.

Here is the layout that I am using for my weekly list:

Initially I thought to suggest this list only to people who cook on a daily basis. However, in today’s diet crazy world I believe everybody can benefit from this. Of course, if you are Paris Hilton, or other people who don’t care much about their budget and have lots of time on their hands, you can be excluded from this advice. I am sure those people either never read this type of material, or they abandoned reading this article long ago.

Shopping list

Now, let’s go back to the list. You will agree with me that a smart shopper won’t go shopping without knowing what they exactly need. With these kinds of lists you will consistently save money and you will avoid having rotten or spoiled groceries that you purchased when you did not need them in the first place. This front-end planning is very important! Are there times when you are coming from work and you are looking forward to having a relaxing evening at home? How many times have you suddenly come to realize: “Gosh, what am I going to cook today? Maybe I can cook pasta, it’s the fastest. But wait, is there any pasta left in the bag? But what if I don’t have any tomatoes left in the house for my pasta sauce? Should I make a quick trip to grocery store first? “In the end you end up microwaving a frozen meal, or ordering takeout, yet again. And for some strange reason you notice that your waist is not getting any slimmer despite your best efforts!

Menu

Before you start jotting down your shopping list you first need to plan your menu. Even in case you go out for dinner or get takeout, put that down too for the particular day. Of course you can have fast food, takeout or a dinner in a nice restaurant. We all need to indulge no matter the size of our wallets. What is important, however, is to plan it all so you will more than likely end up with a balanced diet, translating to quality assurance. Plan a meal with meat one day and then veggies the other, make sure to get fish at least once per week, and so on. You can control your diet in this way and also avoid too many fast food splurges. We usually forget these things if they are not written down, like when you ask yourself if you had pizza last week, or last month. Most likely it was a few days ago, but who can say? It can also help with conflict resolution with your family members. If your kids, for example complain that you had cooked broccoli a few days ago, you can always present the evidence that in fact the broccoli was nowhere in sight on your current and even last week’s lists. Not to mention the power of negotiation, when you can say:”We are going to have cabbage on Thursday, but pizza on Friday”. Nobody can refuse that generous offer!

Changes

Once you have decided on the menu and after you came back from your weekly shopping trip (almost all items on the left will be crossed out) you need to stick your list on the fridge door. As soon as you notice you are running out of a particular ingredient just add it to your list and make sure you will still have everything you need for your meal tomorrow. You can always feel free to change your menu choices on the fly; just make sure that you have all the ingredients for the new meal. Fortunately there is no need for the change management process as you are in complete control, provided that you are the cook! The section underneath the menu could be used for other meals that did not make the cut into the current week, or meals that you may prepare for emergencies.

Errands

Finally, there is a section for your general to-do list. An errand list if you will. An average person, especially if you live with family, may have more than can fit in the space. I would recommend you have only high priority items here, things that you have to do during that week. Another option would be to use the other side of the paper for an extensive to do list. Some people may prefer to have those lists in electronic format, such as MS Outlook tasks, or even using calendars, hard copy or electronic. Even this template could be made in electronic format, but the end result is usually different from person to person and the key is to find something that works for you.

Benefits

Hopefully there will be plenty of historical information for your weekly operational project of planning, shopping, cooking and eating activities. If you stick to this routine it will eventually become effortless and you will feel more in control. Of course many of you already have your own lists and routines, but for those who don’t, I believe this method will pay off. It should help in controlling your budget and your diet, reduce the waste and save time. The bottom line is that you are guaranteed to see a return on your investment.

If you have any comments or suggestions on this article or any other content on this site I would love to hear from you!

Click on Comments link below or send me your email at durica@sympatico.ca

Mom's Project

( Niagara on the Lake, picture taken by Azra, May,o7)

I cannot believe this day has finally come. My project, “Raise a Boy” reached its biggest milestone yet- Go Live Weekend- and it was a brilliant success. Or so I thought.

My company, called My Family, finally completed this project after 24 years of execution. The product, a-BOY-A, rolled into production last weekend, but the final phase, similar to the other phases, was not completed without many challenges.

I remember how the project was delayed for few years during its Test Phase when BOY-A took a trip to Europe. I had concerns that one of its tests failed when additional money suddenly had to be sent to Europe to pay for unexpected expenses. My sponsor, called My Husband, finally had enough and warned me that by prolonging this one I was jeopardizing other projects in our organization.

I still had a nagging feeling that there were many risks lurking, which could negatively impact BOY-A’s operation and that because of them, the operation could go astray. After many sleepless nights of deliberation, I had to admit that once the product was in production I would have to let it go. I would have to have complete trust in the production managers to do a good job.

Let’s go back to last Sunday, when the final step of the project was completed. A-BOY-A moved into an apartment in Toronto, shared with other two operational products, themselves being the results of other global projects. I am not sure what their names were; I only know that they are a boy-kind of product. This fact is very important because my sponsor did not agree with an idea that our product solution would be joining operations with even one of a girl-type product.

So, a-Boy-A was officially handed a set of house keys by a Landlord Operational Manager. Prior to this, I had given Boy-A a User Manual, with instructions like “What to cook for dinner every day”, or Boy-A could utilize “Different methods of status reports deliveries”, which could be done either verbally by phone twice a week, or via Skype communication over the Internet at least once per week. Another instruction was a face-to-face status meeting every weekend. I exacted a promise that this reporting execution would last for at least couple of months. Of course “Weekend visits back home” instructions had train and bus schedules attached, as well as detailed instructions on the light packing of dirty clothes in a bag, to be returned as a bag, of folded, clean clothes along with food and other interesting items.

This final phase of the project did not come without a lot of challenges. Along the way I tried to apply PMBOK, Possible Management of Boys, Body of Knowledge. I collected many templates, tips and techniques; I researched extensively the PMI – People Management Institute website and finally went to many PMI-CTT – Community Team Training Chapter dinner-meetings. I am hoping to achieve a PMP designation soon, which for those who do not know is acronym for “Projects by Moms Professional”.
I must admit that my sponsor, My Husband, did achieve his “People Management Professional” certification a few years back.

Even so, there were many activities that came out of nowhere and without any warning. I did not have them in my WBS dictionary; however, they needed an immediate attention. Once, during an automated test in a pilot “temp job” project, a-BOY-A announced that he had executed a “Quit job” task, which consequently shut down one of its pilot operations called “EB- part time customer support job”. I knew that this action would result in an issue escalation because additional budget would have to be approved. I must admit that this risk never even crossed my mind, let alone that I was prepared for it by identifying this risk, and applying appropriate strategies, such as risk response planning or monitoring and control.

I immediately called a meeting with My Husband sponsor, who is by the way also my primary client, and explained the issue, by announcing that project was in yellow status. I was criticized for not following the established communication plan framework, which by the way, was never signed off by this very same sponsor because of disputed verbal communication method. He insisted on written progress reports instead, to be read between dinner and evening news. He agreed though on weekly, preferably monthly status meetings, held during “TV commercials” tasks. These meetings, however, had to be randomly scheduled between “Soccer game” activities and such, as part of “Sports channel” work package activities.

When I explained that this was news to me as well, I was blamed for applying human resources practices and presented a-BOY-A organizational policies and procedures, such as “Do not quit a job without asking your parents first”. I tried to explain that a-BOY-A probably misunderstood another policy, which we have mentioned many times: “Your school is a priority number one job” and the other called” If you make mistakes you have to fix them yourself”. I knew at that time that I should have had more frequent verbal communications with a-BOY-A, but kept communications with the sponsor only at the high level.

To achieve good quality with “Second semester” work package, we needed to increase the budget, I explained to the sponsor. Because of lost revenue from “Temp job” we needed to find some other revenue sources towards grades improvement requirement. After all, “Raise a boy” project had to continue and without essential resources given to this project, such as new clothes, phone bill payments and occasional movie tickets the project could be still delivered on time, but the quality of final product would suffer.

Listening to my impact/analysis explanation, the sponsor became agitated (which reminded me of the time he was project managing “I Will Build a Shelf in the Basement Myself”. Though under budget, the project was delayed for two months, because as a one-man project did not have enough resources.)

Because of my knowledge of “Emotional Intelligence” I noticed sudden warning signs of an emotional amygdala hijack attack on my sponsor, so I quickly applied the SOSS formula I had learned about at a PMI Chapter meeting. SOSS is: Stop, Oxygenate (breathe deeply), Strengthen Appreciation (think about lying on a beach, for example) and Seek (remove the amygdala attack trigger (i.e. have a break). My approach was to suggest he stop for a coffee, or even better, a cappuccino, accompanied by a piece of home made cake I had previously baked for these critical moments.

My sponsor finally agreed that he would find a way to provide additional budget, which I suspected may eventually be re-distributed from my new shoes expenses. I quickly remembered a budget-related lesson learned during initiation phase of our company, when the cost of my “Shopping” project doubled. Only my sponsor’s double shift work for two months saved our company from bankruptcy.

After this successful negotiation I then had to negotiate with a-Boy-A to work harder to achieve a minimum of 80% average in his “Second semester” course load. This time, however, to break the news to my sponsor, I had to make sure that in addition to cappuccino and cake, home-made lasagna was served at our next status family meeting.

The meeting was success, the change order was signed and agreement was reached by all attendees that the project could continue, however, it would have to be closely monitored and all new milestones would have to be incorporated into the plan.

I also introduced regular performance reviews, as well as variance and trend analysis. I monitored performance by making sure some measures were incorporated in the project, such as “Not going out during the work week”, “Not missing any class”, “Doing assignments on time” and “Going to sleep before midnight”. I added appropriate activities in the quality plan to be sure that deliverables meet the identified quality standards. Finally, the next phase-end review was signed off by both client and sponsor, and an average mark of 87% was achieved. This project deliverable actually exceeded the stakeholders’ expectations by 7%, since a minimum of 80% was needed for the admission to university, which consequently was a pre-condition or dependency for “Raise a boy” project to proceed into next phase.

Lessons were learned, of course, which I recorded in our organization’s best practices database. Here is just an excerpt from this project, which could be applied to other similar projects very easily:
1) If you work on less important tasks, such as watching TV, you could be in danger of jeopardizing high important tasks, such as study for exams.
2) If you try to make up for lost time by compressing the test schedule and studying late at night, or even worse, in the morning before exam, it will impact negatively the quality of your product and your course marks will be lower than you expected.
3) By doing the above on regular basis, you will also miss some of your client’s, (read: teacher’s) signoff phases for assignments, or meetings with other clients, a.k.a. attending classes.

Consequently all the above will definitely lower the quality of your deliverables, even if you meet deadlines. These were the reasons that my sponsor explained why a-Boy-A had a deficiency of 13% on his “Second semester” marks; consequently as a PM I barely made a “Meet expectations” assessment in one of my performance evaluations/reviews.

I haven’t yet mentioned that this was not my only project. In fact, I have a whole portfolio of projects under my belt and also juggle different roles within these projects. Some examples are: House Cleaning, Cooking, Guests Entertaining, Shopping and Work for Pay projects. No matter what role I would take, even if given without consent, I was expected to deliver on time, on budget and in scope.

I have to mention that my sponsor also has lot of projects in which he is the PM, along with other roles. Some of these are: Yard Work, Fixing and Driving. For these projects I usually play a client and/or sponsor role and I make sure that I frequently criticize my PM so that he achieves perfect results.

The other critical project in our organization is “Raise a Girl”, which I must admit, is becoming even more of a challenge than with Boy-A, so My Husband and have I decided to work jointly on this project. We’ll need training for conflict resolution, as well as having to pay a visit to our PMO - Steering Committee, whose members are Grandpa, Grandma, Next Door Neighbour and Best Friend. We will go there next week to strategize the approach for this project. We may need to implement the Agile project methodology in this case. I will let you know how this turns out.

The project management discipline is becoming more complex and demanding. The competition is fierce as my sponsor will demand that the final product, a-GIRL-M, be nothing less but of the highest quality. As well, it will have to meet My Family’s strategic goals. In the meantime, the “Raise a Boy” project continues to be important, even though it is in the operational stage, and some day it might even become a capital project again.

Finally, the most important business objective of this project is to expect cash in-flows over the years and to gain ROI on its initial capital invested. It is also expected, looking at five and ten year’s organizational strategic plans, that these products will create future revenue generation, by planning critical projects in their own portfolios, such as “Get Job”, “Get Married” and “Raise Children” projects.

Comming Soon - My articles

Sarajevo

More coming soon...