In my more than 20 years of experience managing technical projects, most project managers move directly from engineering into project management - do not pass go, do not collect $200. Does this count as the experience necessary to manage a complex technical or non-technical project? Does his or her ranking as a subject matter expert qualify her for the position of manager? Are the skills necessary for each so different? It’s often been said that the best way to lose both a good engineer and a good manager is to move the engineer into management.
Far too many projects fail to achieve their purpose, or scope, within the established schedule and budget. If we assume that the schedule and budget are achievable and reasonable, then what causes these projects to fail? The possible causes are too numerous to list and each project would require a root cause analysis, but every “tiger team review” that I’ve attended have determined that the seeds of failure were planted in the early stages of the project, especially during the initiation and planning phases. So, what roles do education and experience play in preventing these project failures?
Starting with education, managing a project is much like managing a small or medium sized business with the exception that a project is time limited, whereas a business is expected to continue operating indefinitely. I use “business” rather than “department” because a department is most often organizationally and functionally limited, as opposed to a project that has elements of management, human resources, engineering, manufacturing, marketing, sales, and even government relations responsibilities. There are also a number of specialized processes associated with a project, each of which includes a set of specialized tasks. These high level processes are initiating, planning, executing, controlling and closing. Addressing just the initiating process, the project manager has to consider the initiator or sponsor of the project; the contract, if it’s an external project; the scope, or the final deliverables expected; organizational culture; project management tools available; standards, guidelines, defined processes; human resources availability; historical assets and lessons learned from previous similar projects. She must also identify all stakeholders, both positively and negatively affected individuals and organizations, to the project. Her experience as an engineer or subject matter expert is of minimal benefit as a manager of a project, but experience as an assistant project manager is of immeasurable value. Also, education in the form of an MBA or business degree, backed up by certification as a Project Management Professional (PMP®) from the Project Management Institute, provides an excellent background for the new project manager.
The question of whether experience or education is more important to the success of a project manager is that both education and experience are essential, but the experience must be in the field of project management as opposed to the field of the subject matter expert. Project management experience at some point will trump formal education, but that point is after many years of managing complex projects.
About the author:
Owen Murphy has more than 20 years experience managing successful projects in Europe and Asia as well as domestic projects in the USA. He has both the education and the experience to manage projects of all sizes. He holds the PMP certification as well as the Certified Management Consultant certification from the Institute of Management Consultants. See http://www.transglobalconsulting.com.
Saturday, February 25, 2012
Rediscover Project Management Knowledge
Do you ever notice how after learning a concept many years ago, when you come
across it again, you understand it either differently or better?
As we experience "life" in project management -- managing various projects, working with new teams and wearing different hats on those teams -- we get to see various aspects of project management in action. We add to that knowledge from our own successes and failures.
We usually refer to those experiences as growth and development. The experience alters how we see things and how we communicate with people: our teammates, suppliers, third party partners, customers and clients. It also alters how we perform work because we gain a new point of view or change in our current point of view.
As such, it's valuable to review what you already know by reading through chapters of A Guide to Project Management Body of Knowledge (PMBOK® Guide) to focus on the key areas that you work in, be it in risk management, scope management or resource scheduling.
When you review the material after having had some experience, you not only remind yourself of what you learned initially, but you see it differently. You catch some elements that you didn't see how to implement before, or you recognize how to relate to something in a way that you didn't before. Having that "life" experience in project management alters how you see the material and how you apply it in everyday work.
This happened to me when I reviewed the PMBOK® Guide recently. After reviewing the chapter on risk management, I realized that my company needed to include additional steps for how we handle a backup or restore operation. While many companies have testing strategies, ours only documented this step conceptually. I may not have noticed this if I hadn't reread the PMBOK® Guide.
I challenge you to review the knowledge in the PMBOK® Guide and see how you can apply it to your active projects. Areas that you can improve on will turn up and will add value to your project management practice.
How do you rediscover your project management knowledge? Have you rediscovered practices from the PMBOK® Guide recently?
Article by Dmitri Ivanenko, PMP, for Voices on Project Management.
As we experience "life" in project management -- managing various projects, working with new teams and wearing different hats on those teams -- we get to see various aspects of project management in action. We add to that knowledge from our own successes and failures.
We usually refer to those experiences as growth and development. The experience alters how we see things and how we communicate with people: our teammates, suppliers, third party partners, customers and clients. It also alters how we perform work because we gain a new point of view or change in our current point of view.
As such, it's valuable to review what you already know by reading through chapters of A Guide to Project Management Body of Knowledge (PMBOK® Guide) to focus on the key areas that you work in, be it in risk management, scope management or resource scheduling.
When you review the material after having had some experience, you not only remind yourself of what you learned initially, but you see it differently. You catch some elements that you didn't see how to implement before, or you recognize how to relate to something in a way that you didn't before. Having that "life" experience in project management alters how you see the material and how you apply it in everyday work.
This happened to me when I reviewed the PMBOK® Guide recently. After reviewing the chapter on risk management, I realized that my company needed to include additional steps for how we handle a backup or restore operation. While many companies have testing strategies, ours only documented this step conceptually. I may not have noticed this if I hadn't reread the PMBOK® Guide.
I challenge you to review the knowledge in the PMBOK® Guide and see how you can apply it to your active projects. Areas that you can improve on will turn up and will add value to your project management practice.
How do you rediscover your project management knowledge? Have you rediscovered practices from the PMBOK® Guide recently?
Article by Dmitri Ivanenko, PMP, for Voices on Project Management.
Thursday, February 23, 2012
The Silent Generation on Project Teams
As projects teams have become more dispersed around the world during the last two decades, the multigenerational project team inadvertently came into existence. Since then, I've dealt with diversity, virtual teams and multicultural issues.
As a project manager of multigenerational teams, my main objective is to figure out how to reconcile generational differences. These differences occur in everything from values and characteristics to priorities and motivation to feelings toward technology and management styles.
In order to more effectively manage multigenerational project teams, I not only need to focus on a team member's visible characteristic actions and behaviors, I have to find out more about his or her generation's beliefs and attitudes. From here, I can tailor my management style.
Take the Silent Generation, for example. Members of this generation were born pre-World War II. In the United States, this generation grew up in a time of economic turmoil and world conflicts. They set their values on discipline, respect and self-sacrifice.
For me, it's very important to understand that discipline, loyalty and working within the system are among the values that members of the Silent Generation will bring to my project team. I have to appreciate that those members have a vast knowledge to share and high standards on work ethic.
In communicating with members of the Silent Generation, I've found that face-to-face meetings are more effective than using e-mail or conference calls when discussing project matters.
Team members who belong to the Silent Generation have a clear understanding of authority, regardless of how old the project managers they work for are. This, along with respect for authority, was prevalent in their early years as they grew up in homes where the mother typically stayed at home and the father went to work.
Members of the Silent Generation bring experience and balance to the project team environment. Their views are based more on common sense than on technology -- as is the case with some in younger generations.
Article by Conrado Morlan, PMP, PgMP for Voices on Project Management.
As a project manager of multigenerational teams, my main objective is to figure out how to reconcile generational differences. These differences occur in everything from values and characteristics to priorities and motivation to feelings toward technology and management styles.
In order to more effectively manage multigenerational project teams, I not only need to focus on a team member's visible characteristic actions and behaviors, I have to find out more about his or her generation's beliefs and attitudes. From here, I can tailor my management style.
Take the Silent Generation, for example. Members of this generation were born pre-World War II. In the United States, this generation grew up in a time of economic turmoil and world conflicts. They set their values on discipline, respect and self-sacrifice.
For me, it's very important to understand that discipline, loyalty and working within the system are among the values that members of the Silent Generation will bring to my project team. I have to appreciate that those members have a vast knowledge to share and high standards on work ethic.
In communicating with members of the Silent Generation, I've found that face-to-face meetings are more effective than using e-mail or conference calls when discussing project matters.
Team members who belong to the Silent Generation have a clear understanding of authority, regardless of how old the project managers they work for are. This, along with respect for authority, was prevalent in their early years as they grew up in homes where the mother typically stayed at home and the father went to work.
Members of the Silent Generation bring experience and balance to the project team environment. Their views are based more on common sense than on technology -- as is the case with some in younger generations.
Article by Conrado Morlan, PMP, PgMP for Voices on Project Management.
Subscribe to:
Posts (Atom)