Search This Blog

Saturday, February 03, 2018

A Glimpse at my Project Management Beliefs

Remove people from your team that don’t ask questions, don’t talk with other team members, won’t provide documentation, or won’t do analysis

Only people that aren’t competent won’t show off their work

Question authority or live with the result

A sense of humor can help get teams through tough times

A working meeting should have no more than five people. Meetings with more than five should be reserved for providing updates or relaying information

Project failure is planned at the beginning of the project

Project initiation is the most important project phase

Be honest in all your dealings

Project managers are expected to offer their opinions, but be accountable for their words

When it comes to project scope, what is not in writing has not been said

Have verifiable milestones

End of project surveys must be completed and the results distributed to the team

Bad conclusions lead to more bad conclusions

Documented assumptions are believed to be true for planning purposes

The best lessons learned come from failures

Without data you only have an opinion

Data doesn’t tell the whole story

Bad data leads to bad decisions

Senior management is usually clueless when it comes to what your project is all about

A bad project team will never deliver good project results

If your project sponsor isn’t responsive you should put your project on-hold until such time they can become involved

The bottleneck is at the top of the bottle

A project manager’s main job is to keep the customer happy

At the end of a project if you have met all scope, quality, budget, and schedule objectives, but the customer isn’t satisfied your project is a failure

Documentation doesn’t replace knowledge

Most people want to do good work. Many times they don’t have the tools or information they need to perform well, or they aren’t managed properly

Project managers aren’t successful if their team members aren’t successful

Not all successful project managers are competent and not all unsuccessful project managers are incompetent. Sometimes you just have to be lucky

Good project managers are insecure by nature

An introvert can’t be a (successful) project manager

A project manager with lots of enemies won’t be successful over the long run

You must be a relationship guru and be ready to fall on the sword sometimes

A project manager must be a motivator

If you don’t listen, you can’t plan

Project managers deal with change. You must be the change agent for your project. Your project sponsor is the change salesman

Monday, January 22, 2018

Business Case Template - Adapt to your needs

Try this template out and make changes based on your needs.  This was used by a government organization, but can be easily modified for use by the private sector. 

CLICK HERE for the Business Template

Thursday, December 28, 2017

Stuff I Use - Classé Sigma 2200i Integrated Amplifier

Stuff I recommend...

A personal project this time, upgrading my two channel audio system.

The Classé integrated amplifier has a ton of features and sounds great.  I have owned it for eight months.  Awesome!

Classé Sigma 2200i integrated amplifier Measurements | Stereophile.com

Tuesday, March 28, 2017

Important Words for the Project Manager

The six most important words: "I admit I made a mistake"

The five most important words: "You did a good job."

The four most important words: "What is your opinion?

The three most important words: "If you please"

The two most important words: "Thank You"

The one most important word: "We"

The least important word: "I"

Cheat Sheets Give Teams a Helping Hand When Dealing with Change

Click here for a template I made years ago for an Operations and Maintenance Team

Monday, March 27, 2017

Project Management and Maximo Presentation - IBM Pulse Conference 2008

Click here for Slide Deck located on Google Drive

Feedback is appreciated!

Sunday, May 22, 2016

Estimates are Usually Guesstimates!

I have been burned more times than I can count by bad estimates. What can a project manager do to help ensure the accuracy of estimates?  First we should understand the basics behind the estimating process (there are many more than I have listed here). Some are:

• The more unique , complex, or larger the project, the more of a challenge it will be to get good estimates 

• Estimates are only as good as the estimator is at predicting the future 

• "Padded" estimates are not always bad as long as the padding is communicated (... and as long as the Project Manager is the one doing the "padding") 

• An estimate is not a bid

• Estimates using sound estimating practices, performed by experienced estimators from clear specifications should never be negotiated 

• Ballpark estimates are guesses and should be treated as much by the project team, management, and the project sponsor

Other items to consider when estimating are:

• Ensure the statement of work or contract is clear and understood by the person(s) doing the estimates 

• Ensure that a schedule or mandated date doesn't drive the estimating thought process 

• Include Risk Management in the estimating process 

• Ensure that estimates take into account the skill level(s) of the person(s) that will do the work 

• If your work breakdown structure (WBS) is flawed, your estimates will be inaccurate

Accurate estimating is an art and a science. The estimator (or team) must take into account historical data from past projects, the team's knowledge and experience, the project risks, the statement of work and other project information to make the best estimate possible.

Keep in mind when planning your project that estimates aren't hard and fast numbers. They are guesses, however they should be very good guesses if you have good estimators and are following tried and true estimating practices.