Saturday, October 6, 2007, 12:25 PM
One of the greatest stress relievers in life is laughter. So, here is a joke for those days when you need a quick relief.
--------------------
Joke 1: Quoted from unknown author
A project manager and two programmers are working on an urgent project. One day they decide to walk to the nearby beach during their lunch hour. Halfway up the beach, they stumble upon a lamp. As they rub the lamp a genie appears and says “normally I would grant you 3 wishes, but since there are 3 of you, I will grant you each one wish.”
One of the programmers says, “I’d like to spend the rest of my life living in Hawaii, in a huge house, with no money worries and surrounded by beautiful women who worship me.” The genie grants his wish and sends him off to Hawaii.
The next programmer says, “I would like to spend the rest of my life living on a huge yacht cruising the Mediterranean, with no money worries and surrounded by beautiful women who worship me.” The genie grants his wish and sends him to the Mediterranean.
Then finally the genie asks the project manager, “And what would your wish be?”
The project manager replies, “I want them both back after lunch."
-------------------
I thought that was absolutely hilarious. I hope you enjoyed it too. Kudos to whoever came up with that joke.
Talibah Adenouga, PMP
Founder of JANOP
tadenouga@janop.com
www.janop.com
[ add comment ] | permalink
Saturday, September 15, 2007, 11:57 AM
After you have developed your project requirements, determined and received approval for your project budget, developed your project plan or timeline, developed an issues or status log, as well as a risk document and contingency plan, executing the project is gravy and pretty uneventful until launch. However, before you kick your feet up, you should hold a “Go / No Go” meeting. This is a meeting where you sit down with your team and get a vote from each team member on whether to move forward with project implementation or delay launch.
You should hold your Go / No Go meeting at least 2 weeks prior to the launch date of your project. You should document the time and date of when this meeting was held, the name of the persons who attended, each person’s Go / No Go vote, and each person’s role or the group they are representing. On the meeting invitation for your Go / No Go meeting, you should request that those who cannot attend reply to your e-mail with their vote. Then keep the response provided or follow up with that group if no response is given.
You can use the Go / No Go Register example, accessible via the "related link" below, as a tool to help you record the votes from team members on whether you should move forward with the launch of the project.
Remember to document the votes of the project team members, and their role during the project. The last you want is for a team to get upset with you about something you implemented and not be able to show them that their team's representative was fully aware and agreed to move forward with the project.
Talibah Adenouga, PMP
Founder of JANOP
tadenouga@janop.com
www.janop.com
[ add comment ] | permalink | related link
Thursday, August 23, 2007, 11:27 AM
Once everything is said and done, the project has been launched and all post implementation issues have been resolved, it is important to formally close out the project by creating a close out binder. If you create a close out binder, you can refer anyone to that binder when a question arises about the project. This will allow you to separate yourself from the project after you’ve implemented it.
At a minimum, the project binder should include the following:
- Project team roster or a list of individuals on your core team, including their role during the project
- A copy of all the detailed meeting minutes you created
- Requirements Document
- Issues or Status Log
- Project Timeline
- Risk Document
- Project Budget
- Lessons learned
- Go / No Go Document
- Outcome of the project
- Post implementation issues and resolution steps taken
- Any additional documents or information you feel necessary, such as exceptional activities taken that were "outside of procedure/process" but necessary for implementation of the project and clear executive/leadership approval of such activities.
Formally closing out your project with a close out binder is very important if you want to seperate yourself from the project after it's been implemented. It is also important for those times when you have to quickly explain why you did certain things that may seem questionable at first glance.
The last thing you want is for someone to ask you a question about the project three years down the line, and you either cannot remember or have to spend hours, even days, trying to find supporting documentation for what you did and why...especially if there is a potential legal issue.
So, be sure to take a little time to create your close out binder. You'll be glad you did.
Talibah Adenouga, PMP
Founder of JANOP
tadenouga@janop.com
www.janop.com
[ add comment ] | permalink
Tuesday, July 31, 2007, 06:22 AM
Conflict arises when two groups or individuals have strong views that are in opposition, and neither wants to abandon their position. When it does arise, managing conflict is not always easy, but definitely achievable.
Healthy conflict, such as disagreements, can be beneficial to your project, because it can bring to the surface new and innovative ideas that may not have been identified otherwise.
Conflict becomes a problem the moment it stops being a discussion where two parties are sharing differing opinions based on fact, to two parties having a heated argument based on emotion.
Conflict should not be suppressed. However, both healthy and negative conflict should be addressed immediately.
Whether you encourage those involved to share their conflicting views in a respectful manner or you have to step in and resolve the conflict before it becomes counterproductive, make sure you acknowledge and address the conflict in some way.
The first step to resolving any issue is a proactive one. So, you should strive to reduce the risk of unhealthy conflict arising by maintaining an environment of respect, trust, and open communication.
Since conflict may still arise, even in an extremely positive environment, here's how to handle it.
You should intervene to resolve conflict:
- before the persons involved begin to personally attack each other
- when the disagreement begins to turn into an emotional debate
- when it starts affecting the project and the other team members in a negative way
When you intervene to resolve a conflict, you must:
- listen carefully to both sides
- remain neutral
- ask open-ended questions to encourage dialogue
- observe the emotions of the persons involved
- help the persons involved see things from each other’s perspective
- help the persons come to a compromise that suits both parties
Although you may have to address conflict during your meeting, to prevent it from escalating, make sure you follow-up with the persons “offline” by speaking with them when there is no audience. Remember, your objective is to encourage an environment of team work, not to embarrass the team members.
Consider speaking with each person individually, and then talk through the conflict with them collectively. This will make your efforts to resolve the conflict much more effective.
Remember to maintain an environment of respect, trust, and open communication, in an effort to reduce conflict. When conflict does arise, be sure to intervene quickly and respectively.
Talibah Adenouga, PMP
Founder of JANOP
tadenouga@janop.com
www.janop.com
[ add comment ] | permalink
Saturday, June 30, 2007, 08:50 PM
The next time you find yourself dosing off while attending one of those unbelievably long and boring meetings, find creative ways to engage yourself and relate more to what is being presented.
Pretend that you are a reporter, and the meeting you are attending is your ground breaking story. Take lots of notes and ask the right questions at appropriate times. Afterward, write or record a “news release” on what was discussed or presented.
Then, when you’re done, present the finished product to your leadership. Be warned … you will definitely want to think hard before presenting your "report" to leadership. If it’s good, doing this kind of report on a regular basis could end up being one of your assumed responsibilities … or you might get your feelings hurt if your finished product is lacking (nice way of saying bad).
If you don’t have the time or drive to do something like this ongoing, nor the patience to deal with people bothering you about when the next report is going to be released, keep it to yourself.
This little trick will not only give the appearance that you are engaged and have initiative, but it is also a great way to improve your written communication skills; which is a key skill for all Project Managers to have.
Hate the idea of writing or recording a report or “news release”? Then try to do something else creative.
The objective is to get engaged so that you are perceived as someone who is always attentive during meetings, rather than the one who is always falling asleep.
NOTE: If you sit in close proximity to others during the meeting, doodling or drawing pictures unrelated to the subject of the meeting (ie: a sketch of your boss with horns on his/her head) may not be the most effective way to express your creativity.
Boundaries are limitless, so get creative, get engaged, get recognized, and get paid.
Talibah Adenouga, PMP
Founder of JANOP
tadenouga@janop.com
www.janop.com
[ add comment ] | permalink
Next
