Tips, hints, links, and helpful information related to the discipline of Project Management.
Search This Blog
Wednesday, December 14, 2005
Dr. Kerzner's 16 Points to PM Maturity
One of the things I find valuable that Dr. Kerzner created is his "16 Points to Project Management Maturity". They are listed below and discussed in the book mentioned above.
1. Adopt a project management methodology and use it consistently
2. Implement a philosophy that drives the company toward project management maturity and communicate to everyone
3. Commit to developing effective plans at the beginning of each project
4. Minimize scope changes by committing to realistic objectives
5. Recognize that cost and schedule management are inseparable
6. Select the right person as project manager
7. Provide executives with project sponsor information, not project management information
8. Strenghten involvement and support of line management
9. Focus on deliverable rather than resources
10. Cultivate effective communication, cooperation, and trust to achieve rapid project management maturity
11. Share recognition for project success with the entire project team and line management
12. Eliminate non-productive meetings
13. Focus on identifying and solving problems early, quickly, and cost effectively
14. Measure progress periodically
15. Use project management software as a tool - not as a subsitute for effective planning or interpersonal skills
16. Institute an all-employee training program with periodic updates based upon documented lessons learned
Until next time...
Stephen F. Seay, PMP
Thursday, December 08, 2005
Paradoxes of Project Management
Total Ego versus No Ego - On the one hand, project managers must be consumed by the project before them. On the other hand, they must have almost no ego. They deal with many outsiders and insiders whom they can hardly command. This means the project manager must take a smaller share of the credit for accomplishments and give a larger share of the credit to other participants.
Autocrat versus Delegator - When the chips are down, the project manager must issue orders fast. At the same time, the project managers must turn ownership over to the contributors.
Leader versus Manager - Effective project managers must match their passion for inspiring others with a passion for the grubby nuts and bolts of doing the job.
Oral versus Written Communication - Communicating orally and on the run comes easily to effective project managers. But, the must also be masters of the detailed plan and the daily checklist.
Complexity versus Simplicity - Nothing is more complex than dealing with a sophisticated, multi-organization project. The effective project manager must juggle, sometimes for years, hundreds of balls of differing and ever-changing shapes, sizes, and colors. On the other hand, the project manager must be adept at keeping it simple.
Big versus Small - Project managers must appreciate forests and trees equally. They must be able to see the relationship of the small to the big and the big to the small, and do so at every moment simultaneously.
Patience versus impatience - Smart, independent leaders spend lots of time on relationship building and networking. This is a s important as pushing project participants for action.
As long-time readers of this blog know, I value the insight of Tom Peters. I believe he hit the nail right on the head in regard to a Project Manager's behavior when managing projects.
Until next time...
Wednesday, November 30, 2005
Lessons Learned?
Capturing lessons learned at the end of a project is important. My problem has always been how do I archive the learnings for use in the future? Post implementation meetings are good for capturing lessons learned, but outside of the team members that attend the meeting where does this knowledge go? How can it be used in the future? Where and how should it be stored?
One idea I read about related to how Boeing maintains diaries of lessons learned from each airplane project. I wonder how these diaries are accessed and utilized on future projects? Are they searchable, indexed by topic, etc...
If anybody reading this has ideas, let me know and I will publish them here.
Until next time...
Monday, November 14, 2005
Quality Revisited
Most of you know that this blog deals with the basics of Project Management. For this week’s blog we will talk a little about Quality in Project Management. Quality is a heavily tested knowledge area on the PMP exam and as such we should all be familiar with the subject.
According to Philip B. Crosby, Quality is “conformance to requirements”. He goes on to state the Four Absolutes of Quality as:
- The definition of quality is conformance to requirements
- The system of quality is prevention
- The performance standard is zero defects
- The measurement of quality is the price of nonconformance.
Another Quality Guru is Joseph Juran. He states that “Quality is fitness for use”. He also defines something called the Quality Trilogy. It is:
- Quality Improvement
- Quality Planning
- Quality Control
Juran also goes on to define the “Ten Steps in the Quality Improvement Process”. They are:
- Build awareness of the need and opportunity for improvement
- Set goals for improvement
- Organize to reach the goals
- Provide training throughout the organization
- Carry out the projects to solve problems
- Report progress
- Give recognition
- Communicate results
- Keep score
- Maintain momentum by making annual improvement part of the regular systems and processes of the company.
Lastly, we look at what Dr. W. Edwards Deming says about Quality. According to Dr. Deming, Quality is “continuous improvement through reduced variation”. His five principles are:
- The central problem in lack of quality is the failure of management to understand variation.
- It is management’s responsibility to know whether the problems are in the system or behavior of people.
- Teamwork should be based upon knowledge, design, and redesign. Constant improvement is management’s responsibility. Most causes of low quality and productivity belong to the system.
- Train people until they are achieving as much as they can (within the limits of the system).
- It is management’s responsibility to give detailed specifications.
Do the above statements reflect the situation in your work environment? Is your management engaged in Quality? Are they hands-on, hands-off, or asleep at the switch?
Quality is everyone’s job; however Quality cannot be managed with out the participation of management. I would even be so bold to say that “poor quality equals poor management”.
Wednesday, November 02, 2005
Backwards Planning
Backwards Planning6 Simple Rules for Scheduling Next Year
“Russian Submarine Captains don’t (go to the bathroom) without a plan.” -Fred Thompson, in The Hunt for Red October
There’s another saying that goes: “The more you do of what you’re doing, the more you’ll get of what you’ve got.” Tired of getting the same results year and year out? It is time to start planning for success. It is time to try something different. Here’s 6 Steps to guide you in planning ahead for success in the year ahead. Use them in your next meeting and see how the orient your entire organization’s thinking.
1. RESULTS – Try planning backwards - Start with the results in mind. Most mid-level managers plan around their schedule in an effort to “fill the calendar.” If your group’s goal is to stay active and keep everyone busy this is a great idea. But if your goal is to accomplish something like, oh I don’t know, let’s say your organization’s mission or turn a profit, this is the dumbest way to start out. Really, what are you in business to do? Move the sand pile left then move it back right the next quarter?
Smart planners begin with the results they want to achieve. They ruthlessly eliminate everything that doesn’t support this goal. They never hesitate to say, “No, that’s not what we are about.” Great leaders stay focused on the main thing they and never deter from it. What do you want to see occur next year? Where do you want to be? Set that as your planning goal and let everything fall in to place around it. Guard this and don’t let any other activity or program get in the way.
2. ACTIVITIES – Next plan the activities it will take to accomplish your goal(s). Don’t schedule them yet. Just sit down and determine what it will take to get to the destination you have set. Some activities may be impossible to pull off, but this will give you a good idea of what you need to be doing and how you need to distribute resources to get things done. Planning activities will help you determine the Big Three questions that need to be answered in planning guidelines:
(A) What do you think you are doing?
(B) What ought you to be doing?
(C) What are you actually doing?
Examining all three perspectives will give you valuable insight into your job and time problems.
Activities that don’t meet these criteria or don’t support the mission of your company, corporation or mission should be eliminated, no matter how sacred they are. How many exercises do you do for no other reason than, we’ve always done them? Read Sacred Cows Make Great Burgers. Yes, it is risky to ask “Why?” but you’ve got to take a few risks to venture into new territory. Have some fun. Go around and ask people how certain historical practices originated and why they continue to schedule them every year. You’ll be surprised at how many people are clueless, but continue to perform them like mindless sheep.
3. PRIORITIES – The next step will happen almost automatically. You and your staff will begin to re-evaluate your priorities and find out what you need to be about in the year ahead. You’ll be surprised to find consensus when you have eliminated useless activities that don’t accomplish your mission or goals. Determining your goals and activities will help you establish clear priorities for the time period you are planning. It will help you enforce the “If it doesn’t support or goals, we’re not doing it” rule.
Use the Paretto Principle to establish priorities: “Eighty percent of our activities produce 20 percent of the results, while only 20 percent of our activities produce 80 percent of the results.” Vilifredo Paretto was a 19th Century Italian economist who established a rule for economics that works in almost every realm of planning. It is simple: List your top ten priorities in order, then circle the top two. Concentrate planning on those two and the other eight will take care of themselves. More organizations waste time on useless trivial activities that produce almost no results. The wisdom of life consists of eliminating the non-essentials.
4. TIME ESTIMATES – How long will it take? How much time will each activity require to get you closer to your annual goals? The key to successful planning is to plan both work and time. Start to determine what will take big blocks of time, how many people will be required to get it done and where will the resources be needed to accomplish each task. Next look at the smaller blocks of time and find out how they can be batched together to eliminate waste in funding and time. Where are the wasted time slots? How can they be reduced or wiped away completely?
Determine what time of the year is the peak performance time to get each task accomplished. Where are the slow periods annually that you can get more “behind the scenes” work done? When is your “showtime,” when visible tasks are best accomplished? Remember these are only estimates but they will give you a good idea as to when you need to be concentrating on the right tasks at the right time.
5. SCHEDULING - Now look at your actual calendar. Things that are scheduled tend to happen on time. Things that are not scheduled may never happen. As I said earlier, most managers tend to schedule first in an effort to fill the calendar and eliminate gaps. Knowing what you are about, why you are about it, and how long it will take will be the greatest ally you have in putting things on in ink.
Use this guideline for scheduling: Flexibility in time: Start early on major efforts, Big blocks come first; smaller jobs/activities come second; and group items that are similar in nature. Scheduling along these lines will do more to eliminate wasted time in your calendar. It will allow for the time estimates to become realities and your people to know what they are doing, why they are doing it and how it fits into your overall mission/goals.
6. FLEXIBILITY – Allow time for error and the uncertainty. This can only be done if you have set out to allow the proper amount of time for big projects. No one can predict the future (although we seem to have an abundance of philosophers, pundits and fanatics who attempt to do it every day). A well-known television economist spent the first two months of his new program telling everyone not to buy home improvement company stocks (Lowe’s, Home Depot, etc.) then was forced to retract every prediction when they soared following the devastating hurricanes in the Gulf Coast areas. One good rule: Don’t take advice from anyone who isn’t personally invested in the suggestions they are giving. You probably have example in your own life of people who said to do one thing only to change when things weren’t as certain as they assured you. Don’t get stuck paying the bill for their mistakes.
Planning flexibility allows you to adjust your schedule as needed. It allows you to drop back and re-evaluate your intentions and redistribute resources and personnel in key areas as are required. Be flexible about your schedule, but not your results or goals. Times change and although you can’t predict the future, the great leaders are able to see through the present times and prepare for both good and bad events. Those with the best outlook on life are always expecting the best, but prepared for the worst, just in case. To deny that problems will arise is foolishness. In summary, our ability to control our time is directly related to our attitude toward controlling our environment. Now you are in control of your schedule. You determine what to do and when to do it based on a simple rule: What results do we want? Henry Ford said, “Whether you think you can or you can’t, you are right.”A year from today, evaluate the tasks you accomplished. How did your employees, support staff come together to meet your goals? How long did it take for everyone to get in step with the master plan and find ways to cut wasted time and reallocate resources? How prepared were you for unforeseen events in the market and society? How much more can you accomplish next year? Try “Backwards Planning” and see how everything fits better into place.
Permission is granted to reproduce this article in whole or in part provided the following byline below appears along with the article and that a copy is sent to me after publication. Thank you: JIM MATHIS is an International Speaking Professional and Trainer.
To subscribe to his FREE personal and professional development newsletter, please send an email to subscribe@jimmathis.com with the word SUBSCRIBE. An electronic copy will be sent out to you every month. For more information on how JIM and his programs can benefit your organization or group, please call 888-688-0220, or visit his website: www.jimmathis.com
Thursday, October 27, 2005
Accepting Criticism
There are many types of criticism, and usually none of it is welcome. Destructive criticism seldom offers any value to the person receiving it and can cause them to be close-minded regarding any future criticism. While the criticism I received was presented in a constructive way, it still didn't make it easier to take. And for what it is worth, we must remember that criticism is just one person's opinion.
What is my point regarding all of this? Constructive criticism can help make us better by forcing us to stop and think about how we act, and interact with others. We need to remember that a positive, optimistic attitude will help us to build strong relationships and obtain the trust and respect of others.
Criticism is something we can avoid easily - by saying nothing, doing nothing, and being nothing - Aristotle
Friday, October 14, 2005
Organizational Project Management Best Practices
Formal (agreed-upon) Project Management Structure
Companies that successfully implement and use project management have a formal structure in place. These organizations have repeatable project management processes, and executives of the company are engaged and accountable for the success of project management and the project’s that they sponsor.
A Repeat Project Management Process
Repeatable processes that are aligned to PMBOK (Project Management Body of Knowledge) Guide’s Nine Knowledge areas have been shown to increase the probability of project success.
Alignment of Projects to the Organizations Strategy
Projects that aren’t aligned will probably not be given a high priority (or proper support) within the organization. Projects that are aligned will have an executive sponsor that is engaged and measured against the project’s success.
Use of Tools
Project Managers need tools to do their job just like any other profession. The tools can be project management software, templates, and other items. The tools need to be closely aligned around the organization’s project management processes.
Experienced Project Managers
This was found to be the single most important success factor in the companies studied. The skills that successful project managers exhibit were:
Experience in Project Management
Ability to see the big picture
Excellent communications skills (verbal and written)
Willingness to do what it takes
Leadership and organizational skills
Problem solving skills
Collaborative and cooperative
Positive Attitude
The book is a great Project Management reference, is well written, and contains a wealth of information that will help you to be a better project manager.
For more information go to: http://www.pcigroup1.com/home_frm.htm
Thursday, October 06, 2005
Wasted Time
I was recently sent a link to a website that brings the topic of time to the forefront. It has significant meaning, especially when applied to our personal lives. Be sure you have your sound turned up on your PC and give the link a try.
Hopefully in will enlighten you about the concept of time, and its importance in your personal as well as your business life.
Check out the site at: The Time Movie
Tuesday, September 27, 2005
The Project Manager as Planner
Some items to consider are:
- Define your tasks using non-technical language, and include descriptions or notes detailing the work involved
- Create milestones in your schedule to help track progress and use them as quality gates
- Ensure you have agreement with the line managers about the skill sets required of his or her resources
- Define up front how you will measure performance
- Define up front how you will measure quality
- Ensure you have a strong project sponsor that is engaged and supportive
- Use Communication plans to keep everyone informed
Doing the above (and lots of other things) will help ensure that everyone involved with the project will better understand their roles and have a vision of what the end product or service will look like.
Wednesday, September 21, 2005
Knowledge Management
Organizations have a lot of knowledge. This knowledge is critical to the organization’s success and is housed in many places. Knowledge transfer among employees is always a challenge, and most importantly most organizations do not have processes in place to ensure that timely knowledge transfer takes place.
An organization’s culture can inhibit effective knowledge transfer. Ineffective knowledge transfer can cause knowledge to be lost or be unclear when and if it is transferred.
Some ways to overcome ineffective knowledge transfer are:
- Face-to-face meetings
- Create an environment that is conducive to collaboration
- Set performance objectives around formal and informal knowledge transfer mechanisms
- Establish regular knowledge transfer procedures (meetings, documents, reports, etc)
- Hire people that are flexible and open to good knowledge transfer practices
- Conduct brainstorming sessions and document the what is learned/transferred
- Reward collaborative efforts
- Use failures as a way to create new knowledge
A common language is important for effective knowledge transfer to take place. Glossaries, scope statements, project objectives and project assumptions will help you to begin the process of knowledge transfer in the early stages of your project.
Monday, September 12, 2005
PMI World Congress - Toronto, Canada
One of the areas I plan to focus on in the new year is expanding my skills around communications and scope management. We can never stop learning if we want to excel in our careers.
Have a good day, eh!
Thursday, September 01, 2005
Project Management Insights - The Human Face of Project Management
Project Management Insights - The Human Face of Project Management
Thursday, August 25, 2005
DISCLAIMER *** Yesterday’s Project Management Best Practices Checklist posting
Just so I don’t get in trouble, I didn’t author the checklist that appeared on the blog yesterday. I found it buried in the reams of documentation, templates, and various Project Management documents that I have in my possession. While virtually all of the postings on this blog were written by me, I will always credit sources when available. I am unsure of the source of yesterday’s posting.
Thanks
Stephen F. Seay, PMP
Wednesday, August 24, 2005
Project Management Best Practices Checklist
Identify the participants and their roles.
Identify potential project team members as well as the major players in the user community that will test and except the final product or service.
Assign an experienced project manager early
This Project Manager will make or break a project. Be sure the individual has the expertise to manage the project and works well with others. Don't hesitate to look at outside sources if there is no one on staff that qualifies.
Assess the qualifications and experience of the planned project team members
Along with the project manager, assess carefully the qualifications and experience of each team member as they pertain to the specifics of this project. Keep in mind the importance of team players, and the ability to get along with others.
Complete a detailed workplan
A preliminary workplan with major milestones should have been completed while developing the PIJ. Now is the time to work with the project manager in identifying the tasks involved for each milestone. The workplan should list the tasks for each milestone with the estimated hours, start and stop dates, costs and responsible parties. Sample workplans and templates are available through GITA upon request.
Establish an issues control tracking system
Establish a method by which, all issues pertaining to the project are recorded and can be reviewed regularly and tracked by the project team. All issues should eventually have a documented resolution. Software to perform these functions may be available through GITA upon request.
Establish a regular project team review meeting schedule
Regularly scheduled project review meetings should be incorporated into the workplan. These meetings are to review the current progress of the project including the percentage of completeness of workplan tasks.
Establish a participant update meeting schedule
Periodic participant update meetings should be incorporated into the workplan. These meetings are to present the current progress of the project to upper management and major participants in the user community.
Conduct a project kickoff meeting
Officially start the project with a meeting of all parties involved. The project team should be introduced, the milestones reviewed with estimated completion dates, and expectations as to the level of participation, should be outlined.
Monday, August 15, 2005
Keep IT Simple
The Pareto or 80/20 Principle can help us realize the power of keeping things simple.
Some popular statistics that relate to the Pareto Principle are below:
80% of beer is consumed by 20% of the beer drinkers
80% of classroom participation comes from 20% of the students
80% of traffic jams occur on 20% of roads
20% of your clothes will be worn 80% of the time
80% of sales are generated by 20% of the sales staff
80% of problems are generated by 20% of the employees
80% of problems come from 20% of the customer base
Now that we know this, how do we make things simpler? The answer is "simple". We need to analyze the data. We cannot guess where the problems are. We cannot just use emotion. As I have stated in previous posts, it is important to look at your business processes to eliminate waste and complexity.
Questions to ask yourself and your organization when seeking to simplify your business processes:
What are our processes?
Who are our customers?
What systems do we use? Do we have the right systems in place to support our business?
What services do we offer internally and externally? Are they still valuable today?
Look for the 20% that adds value and eliminate or redesign the rest. Keep in mind that we are looking to automate, minimize, isolate, reduce, redesign, or reallocate those things that are not helping us to achieve simplicity.
Keep it Simple!!!
Wednesday, August 10, 2005
Project Management Behavior
I know that I have lived a sheltered project management life, but I think many project managers haven't sufficiently mastered the "Behavior" competency. My experience is limited, but I have worked with many project managers, and I believe that we all could improve our skills as they relate to the "Behavior" competency. We should all be able to agree that in order to motivate people a project manager needs an understanding of human behavior and how to motivate teams. How many project managers do you know have mastered these skills? How well do you do in this area? I can admit that I have room for improvement.
As I said, "Behavior" was listed in the top three of the most important competencies. I find that to be interesting because other surveys of CIOs find that the number one complaint about project managers is that they are whiners and excuse makers. How can we change that? Collectively we must decide as project managers we will exhibit the highest ethical and behavioral standards. We will empathize with others, we will be known as good listeners, and we can be trusted to not gossip and participate in destructive office politics.
Thursday, August 04, 2005
Project Managers and Meeting Facilitation
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…
Monday, July 25, 2005
Strategic MRO and Asset Management
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?
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
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.