Search This Blog

Tuesday, July 03, 2007

Good and Bad Leaders

Why are there so few good leaders in organizations today? While I can't answer that question, I am always willing to chime in with things I have learned and believe.

Good Leaders...

need to have a vision that is different, but still able to be accepted by the masses.

step outside of their comfort zones to make change happen

take risks, make sacrifices, and sometimes pay a cost to achieve their vision

instill confidence in others because they themselves are confident

build consensus

with charisma can change organizations

are encouragers

are positive

have the interests of others above their own

attract followers

bring new perspective to problem solving

are enablers

are an inspiration

Bad Leaders...

drive wedges in between people, teams, and organizational structures

don't stand up for their peers or their subordinates

behave like children when they don't get their way

gossip and spread rumors

don't reward others for their accomplishments

use "technobabble" and jargon to confuse others

believe they are smarter than everybody else

are unaware (sometimes) that most people don't respect them

dictate policy and doctrine almost exclusively via e-mail

are invisible to most of the organization

don't want rules, process, or procedure except for others

prescribe before diagnosing

don't solicit input from others unless it is to validate what they already believe

kill organizations through their arrogance and unwillingness to listen

are silent when they should speak

speak when they should be silent

Bad Leaders are hurting our organizations, our governmental institutions, our local schools, churches, and neighborhoods. Bad leaders ruin opportunities for our kids, run organizations into the ground, and are culture killers.

Do your part to eliminate the "cancerous" effect caused by Bad Leaders. Be a "good" leader by exhibiting the necessary leadership principles and ideals that inspire and motivate others. Don't be just another talking head. Be visible, don't gossip, be respectful of others, build consensus, and most of all be honest in all of your dealings.

Tuesday, June 26, 2007

The Value of a PMO

It takes courage for your organization's senior management to step up and support the concept of a professional Project Management Office (PMO). While forming a PMO shouldn't be taken lightly, the benefits are clearly documented.

According to Gartner Industry Research, "building a Project Management Office (PMO) is a timely competitive tactic". They believe that "organizations, who establish standards for project management, including a PMO with suitable governance, will experience half the major project cost overruns, delays, and cancellations of those that fail to do so". Gartner goes on to say that three basic types of PMOs have emerged.

Per Gartner, "at each end of the PMO spectrum are offices that on the one hand range from a repository, which collects and disseminates project management best practices and methodologies, to an internal consultancy model or enterprise project office, which directly provides project managers to run individual projects". "Between these two ends of the spectrum are variants of a coaching model". "These types of project offices provide expertise and oversight for the business (sometimes providing the Project Managers), in addition to advising on project setup, reporting (for example, via dashboard’ reports), and facilitating post-project reviews and metrics collection".

What Value can a PMO Offer?

Establish and deploy a common set of project management process and templates. These reusable components save time by allowing projects to start-up more quickly and with less effort.

The PMO builds and maintains the PM methodology and updates it to account for improvements and newly discovered best practices.

The PMO facilitates improved project team communication by having common processes, deliverables, and terminology.

The PMO sets up and supports a common repository so that prior project management deliverables can be candidates for reuse by similar projects. This helps to save start-up time.

The PMO is responsible for PM training. This training helps to build core PM competencies and a common set of experiences. This PMO training helps to reduce overall training costs paid to outside vendors.

The PMO coaches project managers to help keep projects from getting into trouble. At risk projects can be assisted by the PMO to mitigate further issues and risks.

The PMO serves as a tracking mechanism for basic project status information and provides a common project visibility report to management.

The PMO tracks organization-wide metrics on the state of project management, projects delivery, and the value being provided to the business by project management in general, and the PMO specifically.

The PMO is the overall PM advocate to the organization. This could include educating and selling management on the value of using consistent PM processes, or as a liaison to other business centers to provide project management training and support.

One fact is clear from the research I have conducted, a PMO is critical when it comes to supporting sound project management practices. The larger the project the more project management (PM) can help to bring about success. It is readily accepted that good Project Management processes support:

* Reduced Cycle Time and Delivery Costs
* Improved quality of project deliverables
* Early identification of project issues, budget, scope and risks
* Reuse of knowledge and the ability to leverage that knowledge on future projects
* Improved accuracy of project estimates
* Improved perceptions of the project management organization by our partners
* Improved people and resource management
* Reduced time to get up to speed on new projects

Questions or comments? Post directly on this blog, or e-mail me at sfseay(at)yahoo.com

Wednesday, June 13, 2007

Shared Vision and Goals

I found this document on line and found it very inspiring. I think it is an important message for Project managers since they must constanly get their project teams to agree to a shared vision and be willing to be flexible as conditions change.

Author Unknown
------------------------------------------------------

The Best-laid Plans

Climbing the world's highest mountain under normal circumstances requires months, sometimes years, of preparation. In May 1996, Breashears and his team faced a special challenge: making an IMAX film about their journey. Carrying and maintaining hundreds of pounds of filming equipment meant that planning was even more meticulous than usual. "We went to that mountain with a great plan, an elegant plan," said Breashears. For one, it was flexible. "A good plan makes you nimble, not stuck. Ours gave us options ... wiggle room." By rehearsing extensive "what if" scenarios long before they got to the mountain, the team was ready for the unexpected. So when a freak storm hit the day they were to approach the summit, Breashears' team turned back while other teams kept climbing. With the summit just within reach, the temptation to go on was enormous, Breashears recalled, especially since the team had already spent weeks on the mountain, passing through all four base camps and acclimatizing their lungs to the thin air. Yet, as Breashears noted, "We had to climb on the mountain's schedule, not ours," an acknowledgment that probably saved his life.

As Breashears' team went back down, they passed several other teams on their way up. By nightfall, eight people had perished, including Rob Hall, a world-renowned climber and friend of Breashears. Hall was leading a group of individuals who had paid him a substantial fee to lead them to the top. Jon Krakauer, a writer and outdoorsman who was on Hall's team, would eventually write the best-selling book Into Thin Air, chronicling in heartbreaking detail what had gone wrong.

Among the tragedies of that day was one event that many later described as a miracle. The storm that had hit as Hall's ill-fated team made its ascent caused many of the climbers to become separated. One small group was in desperate trouble: They had lost their way in the blinding snow and had run out of oxygen. In an attempt to save their own lives, they made the difficult decision to leave behind one of their team members, Beck Weathers, a doctor from Texas. By all accounts, Weathers was already close to death. He had no pulse and appeared to be frozen in the ground.

The next morning, however, as Breashears and his team helped with the rescue efforts for those teams still on the mountain, word came on the walkie-talkie that "the dead guy is alive." Weathers had spent the night in sub-zero temperatures fully exposed to the elements. The next morning, as the sun hit the mountain, he awoke from a hypothermic coma and, despite snow blindness and severe frostbite on his hands and feet, managed to stumble into camp. He was eventually flown off the mountain in a helicopter rescue that had its own share of danger and drama.

Having reached the summit of Mt. Everest five times, Breashears knows what he wants in a team. Surprisingly, he's not necessarily looking for the best climbers. "I look for talented people who believe in their craft, not those who are looking for praise," he said. "The most important quality is selflessness. I knew that no matter what, no one would leave me behind," he joked.
Sharing a common goal and vision is critical, and no one's ego can take precedence. "People who say 'me first' can be dangerous on Everest." Indeed, in Breashears' experience, the teams that operate best have a higher objective than themselves. Humility makes a great leader. "The kind of leader I want wakes up and asks, 'What did I do wrong yesterday, and how can I fix it today?' Your team doesn't need to like you, but they have to trust and respect you," he said. "A leader who puts his interests first is a highly demoralizing force."

Wednesday, June 06, 2007

More Ways to Reduce Stress

Get control of your stress before it controls you.

Do something everyday that you enjoy

Record your thoughts in writing (in a journal or blog) This can help you gain a new perspective on events

Do something nice for another person

Try a simple exercise to relieve stress. Inhale through your nose until you reach a count of seven, then exhale very slowly through your mouth to the count of 16, or for as long as you can. Repeat 10 times.

Turn off your phone(s). You can't relax if the phone is constantly ringing.

Tomorrow is another day. Learn when to let go of today.

Teach yourself to become the changes you want to see in others.

Seek first to understand, then be understood.

Make time for yourself! Schedule some quiet time, and relax.

Learn the art of compromise. No one likes a person that is always rigid.

Get up from behind your desk and take a short break several times a day.

Don’t take yourself too seriously or nobody else will either.

Don’t let pessimistic or negative people bring you down. Be positive.

Get past your fears and try something new.

Tuesday, May 29, 2007

Stress Busters

With two teenage daughters at home I know stress. In order to be effective and productive we all need to manage stress so that it doesn't control our actions (think road rage).

I think we all can agree that project management can be stressful, however we need to manage stress or it will manage us.

Here are some great ways to reduce stress.

----------------------------------------------------------------------------------

Schedule your day to avoid back to back appointments; allow time between appointments to gather your thoughts.

Reduce your intake of caffeine

Don’t depend on your memory. Write things down.

Learn to enjoy waiting. Take an iPod or book to read while you wait.

Don't procrastinate. Don't put off until tomorrow what you can do today.

Don't be Rigid. It isn't the end of the world if the yard doesn't get mowed this weekend.

Get enough sleep.

Learn to say "No"! Sometimes it is hard, but necessary to keep your sanity.

Don't be negative. Stop saying things like, "I'm not smart enough", or "I'm too old".

Learn the difference between "need" and "want”. We need food, water, and sleep. Most everything else is a "want". Don’t let life's "wants" take control of your time and resources.

Do the tasks you don't want to do early in the day.

Have a forgiving spirit. Accept that people aren't perfect, and they will make mistakes.

Be optimistic. Believe that most people are doing the best they can.

More to come next time.

Monday, May 21, 2007

Project Scorecard

I found this document in my inventory of Project Management templates. I apologize that I can't credit the original author. If someone knows who created this template let me know and I will edit this post and include the author's name.

Project Scorecard Overview

1. Identify criteria for success. Review the objectives and deliverables in the Project Definition, as well as any other existing information that is relevant to the project. Based on this existing documentation, define what information is needed to show that the project was successful. This can be from two perspectives:

• Internal – These characteristics indicate that the project was managed and executed effectively and efficiently. This might include having deliverables approved with no more than two review iterations, hitting major internal milestone dates on time and having a minimum amount of errors uncovered in user acceptance testing.

• External – These characteristics indicate that your project objectives were completed successfully. Examples here include completing the project within approved budget and timeline, ensuring your deliverables meet approved quality criteria and customer satisfaction surveys.

2. Assign potential metrics. Identify potential metrics for each success criteria that provide an indication whether or not the criteria is being achieved. These can be direct, quantifiable metrics, or indirect metrics that give a sense for success criteria For each metric, briefly determine how you would collect the information, what the effort and cost of collection would be, and what value would be obtained.

3. Look for a balance. The potential list of metrics should be placed into categories to make sure that they provide a balanced view of the project. For instance, you do not want to end up with only a set of financial metrics, even though they might be easiest to obtain. In general, look for metrics that provide information in the areas such as:

• Cost
• Effort
• Duration
• Productivity
• Quality of deliverables
• Customer satisfaction with the deliverables produced
• Project team performance
• Business value delivered

4. Prioritize the balanced list of metrics: Depending on how many metrics you have identified, prioritize the list to include only those that have the least cost to collect and provide the most value to the project. There can certainly be as many metrics collected as make sense for the project, but there may end up being no more than one or two per category. In general, look to provide the most information with the least amount of work.

5. Set targets: The raw metric may be of some interest, but the measure of success comes from comparing your actuals against a predefined target. The target may be a single value you are trying to achieve, or it may be a range. For instance, you may need to complete your project by a certain fixed date, but your actual cost might need to be +/- 10% of approved budget.

6. Add workplan detail: For each metric that remains, determine the specific information necessary to add the appropriate activities to the project workplan. This will include:

• What specific data is needed for the metrics?
• Who is responsible for collecting the metric?
• When will the metric be collected and reported?
• How will the metrics be reported (status reports, quarterly meetings, metrics reports)?

Note: Define your success criteria upfront and get project sponsor sign-off.

Monday, May 07, 2007

Why Is My Project Late?

Design Changes – Design changes during project execution almost always cause delays and impacts to your budget. Once the Scope document has been signed, any changes to the design need to go through your Scope Change Request Process.

Skill Sets – When planning, assumptions are made regarding people's skills. Sometimes these assumptions turn out to be wrong. Also, you will usually have people on your team who are new or are less experienced. These new or lower skilled workers won't be as productive or effective as higher skilled workers. Make sure your project plan has accounted for skill levels.

Unplanned Work or Workarounds – Many times changes must be made to the sequence of planned work. These changes can impact time, cost, budget, and quality. Think about these risks up front and discuss what if any workarounds will be used.

Rework – Rework happens; it is part of project management. Ensure your project plan accounts for rework.

Team Morale – Turnover, project conflict, sick time, vacations all can wreak havoc with your schedule and budget; plan for these things. A happy team is a productive team. Ensure your team is working towards a common goal and not working against each other. Remove disruptive team members from your project if their behavior can't be changed.

Schedules – Trying to do too much in too little time will result in delays. Once you get behind it is very difficult to catch up. Your project will have delays. You need to have contingency plans to get back on track quickly.

Work Environment – Ensure that your team has a proper workspace. Cramming people into poorly designed work spaces will lower productivity.

Tools – Ensure your team has the right tools to do the job. Having the right tool, but not getting into the teams hands at the right time will cause delays in your schedule.

Project Manager Overload – Too many people on a project team without the proper management oversight can cause major problems for the project manager.

Overtime – Adding hours to people's schedules in order to make a deadline will usually do nothing but increase your budget. Adding overtime rarely results in getting a late project back on track.

Executive – Executive apathy can kill your project. People are usually not going to make your project a priority if their boss isn't willing to tell them it is important.

Plan for the above "risks" and you will start to bring your projects in faster, cheaper, with higher quality.