I was fortunate to speak again this year at IBM’s Pulse Conference (Maximo World last year). My presentation for this year’s event was entitled “A Project Management Approach to Implementing Maximo”. As described by IBM, the Pulse conference, held in Orlando, FL (USA) brings together an audience of more than 4000 Tivoli®, Maximo® and Tivoli Netcool® users with IBM partners, industry analysts, and IBM technical experts for one spectacular global event dedicated to the latest technology and best practices in service management.
One of the highlights of the conference so far was listening to one of the keynote speakers, Lance Armstrong. Lance has a passion for his foundation - LiveStrong - and his story regarding his battle with cancer and seven Tour De France victories was compelling and inspirational.
In closing, while my presentation focused on our organization’s Maximo IT project, I believe the presentation would be beneficial to any project manager whether they are managing an IT initiative or some other kind of project. If you would like a copy of the presentation drop me an e-mail.
Tuesday, May 20, 2008
Tuesday, May 13, 2008
End of Project Review/Audit Questions
Here is an excerpt of a document I found in my project document library (you have one don't you?). I don't have the author's name, but will be will be happy to credit him/her if somebody knows the source.
Project Audit Questions
The project audit questions are broken into four topic categories: project management practice, critical incidents, project results and suggestions for the future. These questions cover the major categories of importance for most projects. However, if for a particular project an important category is missed, additional questions can be proposed by team members.
Individuals should first answer all the questions in this section, and then analyze those with a "No" answer.
A) Project Management Practice
Was the project goal clear?
Was a core team established?
If yes, did it remain together for the entire project?
Was a detailed project plan developed?
If yes, did the core team participate in developing it?
Did the plan cover the entire process from concept to customer?
Was the project deadline truly negotiated with the project sponsors?
Were core team members made aware of the benefits of the project for themselves?
for the organization?
Were core team members continually aware of what was expected of them?
and when it was expected?
Did the top management support the project throughout its duration?
Was the customer or end user (or customer representative group) involved early in the project?
Was the customer always fully informed of project progress?
project changes?
project setbacks or failures?
project delays?
Were customer expectations
solicited?
included?
met?
exceeded?
Was project communication sufficient?
Were meetings held regularly?
Was timely project information readily available?
Did team members know who to contact if there was a delay or other problem?
Did the core team meet regularly with
top management?
customer(s)?
contributing department managers?
other interested parties?
Did the project have a detailed budget?
Was it a help during the project?
Now review those questions with a "No" answer. What problems do you think may have been generated by the lack of that factor? What could you, or did you, do to rectify those problems?
What changes or procedures would you recommend for future projects?
B) Critical incidents
Were there things on the project that seemed to go wrong due to a variety of outside forces? Describe these critical incidents. What could have been done (e.g. what signal heeded, data tallied or meetings held) to avoid or minimize these incidents? What do you recommend for future projects?
C) Project results
How well do project results relate to the original plan?
What were the major deviations from the original plan?
Of the major deviations listed, which ones were caused by:
-lack of planning or planning technique skill.
-lack of foresight, not seeing entire project process.
-change in technology.
-change in customer specification or expectation.
-"random" events.
What suggestions would you make to help minimize deviations? What suggestion would you make to help discover necessary product changes faster, more in the beginning of the project when making changes is much cheaper?
Project Audit Questions
The project audit questions are broken into four topic categories: project management practice, critical incidents, project results and suggestions for the future. These questions cover the major categories of importance for most projects. However, if for a particular project an important category is missed, additional questions can be proposed by team members.
Individuals should first answer all the questions in this section, and then analyze those with a "No" answer.
A) Project Management Practice
Was the project goal clear?
Was a core team established?
If yes, did it remain together for the entire project?
Was a detailed project plan developed?
If yes, did the core team participate in developing it?
Did the plan cover the entire process from concept to customer?
Was the project deadline truly negotiated with the project sponsors?
Were core team members made aware of the benefits of the project for themselves?
for the organization?
Were core team members continually aware of what was expected of them?
and when it was expected?
Did the top management support the project throughout its duration?
Was the customer or end user (or customer representative group) involved early in the project?
Was the customer always fully informed of project progress?
project changes?
project setbacks or failures?
project delays?
Were customer expectations
solicited?
included?
met?
exceeded?
Was project communication sufficient?
Were meetings held regularly?
Was timely project information readily available?
Did team members know who to contact if there was a delay or other problem?
Did the core team meet regularly with
top management?
customer(s)?
contributing department managers?
other interested parties?
Did the project have a detailed budget?
Was it a help during the project?
Now review those questions with a "No" answer. What problems do you think may have been generated by the lack of that factor? What could you, or did you, do to rectify those problems?
What changes or procedures would you recommend for future projects?
B) Critical incidents
Were there things on the project that seemed to go wrong due to a variety of outside forces? Describe these critical incidents. What could have been done (e.g. what signal heeded, data tallied or meetings held) to avoid or minimize these incidents? What do you recommend for future projects?
C) Project results
How well do project results relate to the original plan?
What were the major deviations from the original plan?
Of the major deviations listed, which ones were caused by:
-lack of planning or planning technique skill.
-lack of foresight, not seeing entire project process.
-change in technology.
-change in customer specification or expectation.
-"random" events.
What suggestions would you make to help minimize deviations? What suggestion would you make to help discover necessary product changes faster, more in the beginning of the project when making changes is much cheaper?
Wednesday, April 30, 2008
Be On Time!
Being late to meetings, family outings, or any other event is unacceptable. In preparing my presentation for this year's IBM Pulse08 Conference in Orlando, FL I used a quote in one of my slides from Tom Peters that says, "Don’t over-schedule - Running late is inexcusable at any level of seniority; it is the ultimate mark of self-importance mixed with contempt."
Being consistently late for meetings is unacceptable, rude, and tells others that you are more important than them. If you don't have time to attend all the meetings you are invited to then decline them. Don't accept a meeting invitation and show up late.
You are never too important or too busy to be on time. You own your schedule and it is your job to manage it properly.
DON'T BE LATE!