I really do not like meetings. For the most part, I find my time would be better spent doing other things. As project managers, we will be involved in meetings. When we call a meeting we need to ensure that the meeting has an agenda and that meeting minutes are taken.
I find that one of the things that is usually missing from larger meetings is a good facilitator. As a project manager that has called a meeting it is usually best if you have a person (other than yourself) designated as a meeting facilitator.
A Facilitator is: one who brings organization and process to the meeting so attendees are able to interact effectively and make sound business decisions. They enable good meeting habits and support the group to achieve exceptional outcomes.
A Facilitator provides leadership without taking control. They get others to assume responsibility and help them to participate and lead effectively.
Facilitators should:
Assist the group to identify goals and objectives around the meeting topic
Help identify attendee needs
Guide discussions to keep them focused on the agenda
Ensure assumptions are brought out and discussed
Guide the group to consensus on issues by ensuring all attendees are heard
Use tools and processes to ensure the meeting is run efficiently and good decisions are made
Lead brainstorming sessions
Help attendees to assess their skills and assist them in building new skills to support the meeting's objectives
A good facilitator can bring clarity and focus to a meeting. There are many resources on the internet, and there are many good books on the subject. Effective meetings help to build effective outcomes. Ineffective meetings can be seen as time-wasters and can alienate some of the people you need the most.
Make sure your meetings are efficient and effective. One way to do this is to survey meeting attendees to gather feedback.
Until next time…
Thursday, August 04, 2005
Monday, July 25, 2005
Strategic MRO and Asset Management
I just returned from a conference entitled MRO-World. The purpose of the conference was to enhance learning around activities that support Asset Management and the Maintenance, Repair, and Operation (MRO) of those assets. How does this fit in with Project Management? As we all know, Operational activities are focused on maintaining, while Project activities are focused on change. Having said that, Operations activities still have change that needs to be managed.
Strategic MRO is composed of business processes, and is not meant to be an activity management mechanism. Strategic MRO is focused on managing change and continuous improvement in regards to a company's assets. Where I work, we have Strategic Assets that must work nearly 100% of the time. Our systems consist of Water Distribution, Waste Water Treatment, Storm Water Management, Land Fill Operations, Roads, Traffic Control, IT Systems, etc. How these assets are maintained, repaired, and operated can have a huge impact on the bottom line.
In my opinion Project Management can help in the implementation of software to manage assets, in helping scheduling the work to support the MRO of the assets (preventative maintenance for example) , and additionally through communicating the status of critical work and changes to assets going on in the Enterprise.
Part of any organization's responsibilities is to manage their assets to maximize their value. To do this they must:
Define the current state of the asset
Determine the future asset state objectives
Perform a gap analysis between the current and future states
Develop a prioritized task list of what needs to be done to close the gaps
This sounds a lot like project management to me. As I said, I will be doing more research in this area and will report my findings here. As always I welcome your feedback.
Strategic MRO is composed of business processes, and is not meant to be an activity management mechanism. Strategic MRO is focused on managing change and continuous improvement in regards to a company's assets. Where I work, we have Strategic Assets that must work nearly 100% of the time. Our systems consist of Water Distribution, Waste Water Treatment, Storm Water Management, Land Fill Operations, Roads, Traffic Control, IT Systems, etc. How these assets are maintained, repaired, and operated can have a huge impact on the bottom line.
In my opinion Project Management can help in the implementation of software to manage assets, in helping scheduling the work to support the MRO of the assets (preventative maintenance for example) , and additionally through communicating the status of critical work and changes to assets going on in the Enterprise.
Part of any organization's responsibilities is to manage their assets to maximize their value. To do this they must:
Define the current state of the asset
Determine the future asset state objectives
Perform a gap analysis between the current and future states
Develop a prioritized task list of what needs to be done to close the gaps
This sounds a lot like project management to me. As I said, I will be doing more research in this area and will report my findings here. As always I welcome your feedback.
Monday, July 11, 2005
What is a Project?
As the readers of this blog know, I try to cover the basics of Project Management. As project managers, we get in trouble when we try to complicate things. In my career, I have worked for many different types and sizes of organizations. Some have embraced Project Management and others have made excuses so as not to be constrained by what they believe is a process that slows things down (adds cost and overhead). I have preached the same message for years. Project Management is designed to help reduce or eliminate rework and surprises at the end of a project.
So why don’t some organizations see the value of Project Management? Usually it is because they do not understand the benefits of Project Management, they do not trust the Project Managers they currently have, or the ones they have encountered in the past. OK, we can accept that, however, what we should never accept is the idea that Project Management just adds cost and overhead.
We need to educate those around us about the difference between projects and other organizational work. Senior management needs to realize the fact that work is basically broken down into two areas: Operations (focused on Maintaining) and Projects (focused on Change). Most organizations do an adequate job of managing their operations; however, my experience (limited as it is) has shown that projects and the support of project management vary greatly.
Every organization has projects; sometimes they are just too busy to realize it. As project managers, we need to keep fighting the good fight of educating the influencers in our organizations about the benefits of Project Management. In addition, we need to realize that the benefits of Project Management are demonstrated in the successful implementation of projects. Do not preach the benefits of Project Management; demonstrate them by walking the walk and talking the talk.
Therefore, to answer our central question and wrap this up, a project is:
A temporary endeavor to create a unique product or service
Unique
Constrained by a finite budget
Constrained by a finite timeline (defined start and end date)
Composed of interrelated activities
Focused on attaining one or more clearly defined objectives
The last point needs to be stressed. Without clearly defined and agreed upon objectives your project is doomed to fail from the start. I would also add that your project does not have a chance for success unless you have an engaged, influential, and respected executive in the role of project sponsor.
So why don’t some organizations see the value of Project Management? Usually it is because they do not understand the benefits of Project Management, they do not trust the Project Managers they currently have, or the ones they have encountered in the past. OK, we can accept that, however, what we should never accept is the idea that Project Management just adds cost and overhead.
We need to educate those around us about the difference between projects and other organizational work. Senior management needs to realize the fact that work is basically broken down into two areas: Operations (focused on Maintaining) and Projects (focused on Change). Most organizations do an adequate job of managing their operations; however, my experience (limited as it is) has shown that projects and the support of project management vary greatly.
Every organization has projects; sometimes they are just too busy to realize it. As project managers, we need to keep fighting the good fight of educating the influencers in our organizations about the benefits of Project Management. In addition, we need to realize that the benefits of Project Management are demonstrated in the successful implementation of projects. Do not preach the benefits of Project Management; demonstrate them by walking the walk and talking the talk.
Therefore, to answer our central question and wrap this up, a project is:
A temporary endeavor to create a unique product or service
Unique
Constrained by a finite budget
Constrained by a finite timeline (defined start and end date)
Composed of interrelated activities
Focused on attaining one or more clearly defined objectives
The last point needs to be stressed. Without clearly defined and agreed upon objectives your project is doomed to fail from the start. I would also add that your project does not have a chance for success unless you have an engaged, influential, and respected executive in the role of project sponsor.
Wednesday, July 06, 2005
Quality Project Management
Continuous Improvement is the output of a good Quality Management process, and Continuous Improvement requires the proper application of Quality Tools and Techniques. One of the most recognizable Quality Tools is the "Deming Wheel". The Deming Wheel is a simple diagram that focuses efforts around: PLAN, DO, CHECK, and ACT (PDCA Cycle). While this diagram may seem simplistic at first sight, it is a very powerful tool when applied to projects. In fact, Project Management is dependent upon the PDCA Cycle to deliver effective results.
A quick summary of the PDCA Cycle follows.
Plan is the intial phase of the PDCA Cycle. High levels goals and objectives are agreed upon and resources are acquired. In this phase we are identifying a particular problem or problems and breaking them down into manageable tasks. We want to decide specifically how we will solve the problem and establish metrics to measure progress.
Do is executing the Plan. Also, reporting is done in this phase to check progress. Do can be prototyping in the IT world, designing experiments, constructing a building, buiding a model, etc.
Check is the evaluation phase. Did we do what we said we were going to do? Did we meet the project's objectives? What does the data tell us? This is where are metrics are analyzed. We are looking at our KPIs (Key Performance Indicators) and making reccomendations for action.
Act is the adjustment phase. What are we going to do to get back on track or to make improvements? Should we continue or cancel the project? Do we need to replan and start the cycle over again? Here we are acting on our findings from the Check phase. We want to make sure we are acting on the right information at the right time.
The PDCA Cycle is a great tool to help us be successful in Project Management. Using proven Quality Management tools that support Continuous Improvement will help project managers to do a better job managing their projects.
Remember the Four Principles of Quality Management are:
Customer Satisfaction
Plan Do, Check, Act (PDCA) Cycle
Management by Fact
Respect for People
Combining these Quality Principles with your Project Management Processes will lead to powerful results for your customers.
A quick summary of the PDCA Cycle follows.
Plan is the intial phase of the PDCA Cycle. High levels goals and objectives are agreed upon and resources are acquired. In this phase we are identifying a particular problem or problems and breaking them down into manageable tasks. We want to decide specifically how we will solve the problem and establish metrics to measure progress.
Do is executing the Plan. Also, reporting is done in this phase to check progress. Do can be prototyping in the IT world, designing experiments, constructing a building, buiding a model, etc.
Check is the evaluation phase. Did we do what we said we were going to do? Did we meet the project's objectives? What does the data tell us? This is where are metrics are analyzed. We are looking at our KPIs (Key Performance Indicators) and making reccomendations for action.
Act is the adjustment phase. What are we going to do to get back on track or to make improvements? Should we continue or cancel the project? Do we need to replan and start the cycle over again? Here we are acting on our findings from the Check phase. We want to make sure we are acting on the right information at the right time.
The PDCA Cycle is a great tool to help us be successful in Project Management. Using proven Quality Management tools that support Continuous Improvement will help project managers to do a better job managing their projects.
Remember the Four Principles of Quality Management are:
Customer Satisfaction
Plan Do, Check, Act (PDCA) Cycle
Management by Fact
Respect for People
Combining these Quality Principles with your Project Management Processes will lead to powerful results for your customers.
Monday, June 20, 2005
Project Communications Plan
Project Communications Planning is a process that is continuous throughout a project. When building your initial Project Communications plan focus on the following:
Define Your Audiences - Who needs to know What, and When and How do they need to know it. Communication needs and audiences will change as the project moves forward. Plan for it.
Start from the Top and Work Your Way Down the Chain - Start your Communications with the highest levels of the organization first, then work your way down to the team members. Repeat this cycle.
Target Your Message to the Different Groups - Different groups (and sometimes individuals) may require different types of communications media (e-mail, status reports, web site, face-to-face, memo, etc.). Plan for these different types of communications vehicles up front.
Define Roles and Responsibilities - Ensure that your Project Communications Plan includes Roles and Responsibilities for key stakeholders.
Status Reports - Status Reports are a great form of Project Communication if kept short and to the point.
Repetitive Messages will be Required - The same message delivered using different mechanisms and sources will help to reinforce your message.
Anticipate Conflict - Tailor your communications to overcome Conflict before it occurs. Keep in mind that Conflict will always occur on a project. Conflict needs to be anticipated and managed continuously throughout the project.
Allow for Anonymous Feedback - Create a way for people to relay their positive and negative feedback anonymously.
Project Managers need to recognize that good Communication is important because it helps to reduce conflict, increases information distribution, and helps to silence critics while reinforcing the positive aspects of your project.
Define Your Audiences - Who needs to know What, and When and How do they need to know it. Communication needs and audiences will change as the project moves forward. Plan for it.
Start from the Top and Work Your Way Down the Chain - Start your Communications with the highest levels of the organization first, then work your way down to the team members. Repeat this cycle.
Target Your Message to the Different Groups - Different groups (and sometimes individuals) may require different types of communications media (e-mail, status reports, web site, face-to-face, memo, etc.). Plan for these different types of communications vehicles up front.
Define Roles and Responsibilities - Ensure that your Project Communications Plan includes Roles and Responsibilities for key stakeholders.
Status Reports - Status Reports are a great form of Project Communication if kept short and to the point.
Repetitive Messages will be Required - The same message delivered using different mechanisms and sources will help to reinforce your message.
Anticipate Conflict - Tailor your communications to overcome Conflict before it occurs. Keep in mind that Conflict will always occur on a project. Conflict needs to be anticipated and managed continuously throughout the project.
Allow for Anonymous Feedback - Create a way for people to relay their positive and negative feedback anonymously.
Project Managers need to recognize that good Communication is important because it helps to reduce conflict, increases information distribution, and helps to silence critics while reinforcing the positive aspects of your project.
Wednesday, June 08, 2005
Wow! Projects
As many of you may know from my previous blog entries I really like Tom Peters. Tom has so much energy and passion, and additionally, he has some great ideas regarding reinventing work. In my opinion, his ideas around Project Management are revolutionary, bleeding-edge, and way out in front of what is considered the "norm". Recently while reviewing his website I found myself reading about what Tom calls "WOW! Projects". If you have a moment, take the time to read what Tom has to say about WOW! Projects.
To reflect a bit, as I look back over my career I do not think I have ever worked on a WOW! Project, and in hindsight that is a disappointment. As a Project Manager, I struggle every day trying to manage my projects to a "successful" conclusion. Over the course of my career when managing individual projects how that project's success is measured has many times been a moving target. Stakeholders and the project sponsor change their minds in the middle of the project regarding what they want and the ensuing scope changes cause the project success measurement bar to move.
While the project manager is responsible for project success and scope management, the project sponsor can influence project success when stakeholders have more influence over the scope of the project than the project manager does. While this does not happen on every one of my projects, a lesson to be learned is that I must be vigilant regarding stakeholder management.
NOTE: Remember the number one measure of Project Success (according to PMI) is Customer Satisfaction.
In my opinion WOW! Projects require a strong executive sponsor and a well-oiled projectized organization (in addition to many other things) that is not opposed to taking risks. In addition WOW! Project stakeholders must be committed to supporting the following goals of a WOW! Project.
A WOW! Project's Goals are:
An enhanced "customer experience" (internal and external)
Dramatically increased sales
Sharply reduced costs
Improved operating margins
Accelerated leadership and talent development
Innovative solutions to wide-ranging issues
Improved employee morale and job satisfaction
Accelerated post-merger integration
Enhanced stakeholder and community involvement
Cultural transformation
I recognize that I have a lot of work to do to turn my projects into WOW! Projects. Personally I do not think every project that we are assigned can be a WOW! Project, but I do believe if we keep the WOW! Project goals in mind our projects will add more value to the organizations we serve.
What do you think? Until Next Time...
To reflect a bit, as I look back over my career I do not think I have ever worked on a WOW! Project, and in hindsight that is a disappointment. As a Project Manager, I struggle every day trying to manage my projects to a "successful" conclusion. Over the course of my career when managing individual projects how that project's success is measured has many times been a moving target. Stakeholders and the project sponsor change their minds in the middle of the project regarding what they want and the ensuing scope changes cause the project success measurement bar to move.
While the project manager is responsible for project success and scope management, the project sponsor can influence project success when stakeholders have more influence over the scope of the project than the project manager does. While this does not happen on every one of my projects, a lesson to be learned is that I must be vigilant regarding stakeholder management.
NOTE: Remember the number one measure of Project Success (according to PMI) is Customer Satisfaction.
In my opinion WOW! Projects require a strong executive sponsor and a well-oiled projectized organization (in addition to many other things) that is not opposed to taking risks. In addition WOW! Project stakeholders must be committed to supporting the following goals of a WOW! Project.
A WOW! Project's Goals are:
An enhanced "customer experience" (internal and external)
Dramatically increased sales
Sharply reduced costs
Improved operating margins
Accelerated leadership and talent development
Innovative solutions to wide-ranging issues
Improved employee morale and job satisfaction
Accelerated post-merger integration
Enhanced stakeholder and community involvement
Cultural transformation
I recognize that I have a lot of work to do to turn my projects into WOW! Projects. Personally I do not think every project that we are assigned can be a WOW! Project, but I do believe if we keep the WOW! Project goals in mind our projects will add more value to the organizations we serve.
What do you think? Until Next Time...
Wednesday, June 01, 2005
Best Practices for Project Management
Good Planning will Eliminate Many Surprises - Most project problems can be traced back to poor planning desicions, or inadequate planning. Take the time to plan your project properly.
Have Agreed-Upon Project Objectives - Ensure that the project has several agreed-upon objectives that can be reviewed throughout and at the end of the project to ensure they have been met.
Create Verifiable Milestones in your Project Schedule - To measure progress make sure you have milestones that can be verified by someone outside your team. This will assist you to measure real progress.
Manage Scope - Ensure the Project Sponsor approves all Scope Change Requests. Make sure you give the project sponsor your opinion whether the Scope Change Request (SCR) should be approved and why or why not.
Track and resolve Project Issues in a Timely Manner - Ensure that you keep an accurate log of Project Issues and that this log is distributed to the Project Team and Sponsor on a regular basis.
Continue to Assess Your Project Risks throughout the Project - When meeting with your team it is a good idea to reassess the Risks you identified in planning and to see if any new Risks have surfaced that need to be captured.
Communicate Status on a Regular Basis - Depending on the size of your project a status report can be delivered orally, via e-mail, formally, via a website or some other mechanism identified in your Project Communications Plan.
Be Personable and Approachable - Many people will be more willing to help the Project Manager if they are friendly, personable, and trustworthy. Don't be arrogant, rigid, or unreasonable. The project probably won't be successful if your team members distrust and dislike you.
Look for the Warning Signs - Is your team's morale low? Is your schedule off course? Are your team members fighting all the time? Is the team working excessive amounts of overtime? You better regroup now before the situation gets out of hand. Bring the sponsor in to your next meeting and let them assess the project by asking then team for a collective status report. Have the sponsor interview team members one-on-one to look for hidden agendas and unspoken fears.
Most of all, Have Fun.
Have Agreed-Upon Project Objectives - Ensure that the project has several agreed-upon objectives that can be reviewed throughout and at the end of the project to ensure they have been met.
Create Verifiable Milestones in your Project Schedule - To measure progress make sure you have milestones that can be verified by someone outside your team. This will assist you to measure real progress.
Manage Scope - Ensure the Project Sponsor approves all Scope Change Requests. Make sure you give the project sponsor your opinion whether the Scope Change Request (SCR) should be approved and why or why not.
Track and resolve Project Issues in a Timely Manner - Ensure that you keep an accurate log of Project Issues and that this log is distributed to the Project Team and Sponsor on a regular basis.
Continue to Assess Your Project Risks throughout the Project - When meeting with your team it is a good idea to reassess the Risks you identified in planning and to see if any new Risks have surfaced that need to be captured.
Communicate Status on a Regular Basis - Depending on the size of your project a status report can be delivered orally, via e-mail, formally, via a website or some other mechanism identified in your Project Communications Plan.
Be Personable and Approachable - Many people will be more willing to help the Project Manager if they are friendly, personable, and trustworthy. Don't be arrogant, rigid, or unreasonable. The project probably won't be successful if your team members distrust and dislike you.
Look for the Warning Signs - Is your team's morale low? Is your schedule off course? Are your team members fighting all the time? Is the team working excessive amounts of overtime? You better regroup now before the situation gets out of hand. Bring the sponsor in to your next meeting and let them assess the project by asking then team for a collective status report. Have the sponsor interview team members one-on-one to look for hidden agendas and unspoken fears.
Most of all, Have Fun.