Search

The Three Most Fundamental Aspects of Project Management

Over the years I have found that my most popular blog posts are those that speak to entry-level project managers. They value information which is clear and concise and which helps them understand what tools and techniques to use. Project management is a vast practice area and for somebody who has only recently started managing projects, it can seem overwhelming. It is my observation that there are more entry-level project managers coming into the field. And there is a good reason for that. With more and more changes taking place at a faster rate, we have a need for more people to manage those changes. This can be anything from integrating new technology to streamlining business processes or producing cheaper and better consumer goods. With that being said, let’s look at the three most fundamental project management tools and techniques that will help entry-level project managers get their project off the ground.Project DefinitionProjects need to be defined and scoped before they are planned and executed. That is true for all projects irrespective of the type of methodology they use. Defining the project helps us understand what it is meant to deliver, what the benefits are, what the costs might be and by when it is needed. This may sound like a plan to you, but it’s more like a high-level description of the project without the details having been fleshed out. The main question we ask during project definition is whether the project is worthwhile doing or not. There may be lots of ideas for new projects but not all of them have a good business rationale. Therefore they shouldn't be executed at this moment in time with this particular scope. In the company where you work, I’m sure there are many things you could improve on and many ways in which you could enhance your products or services. But not all of these enhancements will be viable business ideas, perhaps because there is a small market for some of those products or too low a margin.When we define the project, we’re essentially looking at the project’s business case and ascertaining if it provides a strong enough foundation for the project to go ahead. Defining the project can take as little as a couple of days for a very small project and several months for a larger one. You can capture the conclusion of this phase in a Project Definition Document, Project Charter, Terms of Reference or Business Case. Different companies use different terms for this document, but they may essentially contain the same information. What I recommend you to put in the document is: Aims and objectives of the project, high-level deliverables, expected benefits, high-level constraints, assumptions and risks, expected costs, future revenues, expected end date, name of project sponsor, project manager, and core team members.Milestone plan  Once the project has been approved, meaning that the Project Definition Document has been signed off, you can move to the next part of the project, which is to plan it. The way you plan a project and lay out its phases, stages, and milestones will look a bit different depending on the methodology your company prefers. If you’re in a more traditional waterfall environment you’d be planning the project in a sequential way, beginning with requirements gathering and detailed statements of scope. You’d then plan for the build or execution phase to take place followed by some testing and final delivery or implantation. And of course, you’d plan for a project review to take place at the end. In more agile environments you’d carry out the above activities (requirements gathering, build, test, deliver, and review) in much shorter intervals or iterations. In addition, you’d deliver something tangible after each phase or iteration instead of all products or features being delivered at the end, which is what we do with a waterfall methodology.No matter how you plan your project, it’s a good practice to plan it collaboratively with the team. Those days are over where the project manager was sitting in isolation behind their desk doing all the planning. That approach simply doesn't create buy-in from the team members. They want to be involved in planning the work that they are expected to carry out.There are several collaborative planning techniques out there that you can make use of. I favour an old-fashioned post-it note-approach where you get people together and brainstorm what the phases, work streams and milestones of the project might look like. You’ll need lots of post-its and a white board or a wall to stick the notes onto. You also need a good facilitator (perhaps your good self) who can guide the team through the process. At the end, you should have a rough idea of which milestones and outputs will be delivered by when. You should also assign ownership to each milestone or deliverable as otherwise, the project manager may end up owning most of the items. Ask the owners to carry out the detailed planning of their individual items and revert at the next meeting with a confirmation of exactly what will be delivered by when. If your team is remote you can make use of virtual post-it-note planning tools.The outcome of your collaborative meetings and planning activities can be captured in a milestone plan. This would be a simple Excel sheet listing the project’s top ten milestones, the owner of each milestone and the expected delivery date. Very simple! As a project moves forward you can also use the spreadsheet to record whether each milestone is on track for delivery and comment on their status. In that way, this simple one-pager overview of milestones becomes a high-level plan and a tracking tool in one. This is an ideal overview sheet to use as a communication tool to your stakeholders so that they can ascertain the status of the project. Your stakeholders don’t need a detailed plan. An overview of the top ten milestones will be sufficient. The detailed plan is reserved for the core team.Risks listBe warned that no matter the size, complexity or methodology of your project, I can assure you that it will be full of risks. That’s because all projects are about creating change, meaning that the project will result in something that hasn’t been done before in that exact setting. In other words, every project is unique and therefore contains a certain element of risk. Project management methodology is essentially there to control risk and to help us execute a project with some level of predictability in spite of its uncertain elements. Defining a project, identifying and analysing user needs and requirements, planning how these requirements will result in outputs and deliveries, clarifying roles and responsibilities and prototyping the solution are all examples of activities we undertake in project management with the aim of driving down risk.Managing risks is a dynamic process as the project’s environment changes on a daily basis. Identifying and mitigating risks is, therefore, something which shouldn’t just be done when the project starts up. It’s an essential project management activity that should be carried out on a regular basis to make sure that new risks are identified and managed and that the existing ones are reviewed. In essence, I suggest that you sit down with your team every couple of weeks to go through the risk list. The collaborative element is important, as the project manager cannot identify all the risks on her own. The team has the knowledge, not only of the things that could go wrong but also in terms of generating ideas for how to overcome potential roadblocks.The outcome of the collaborative risk management meetings is risk list. This is a simple Excel tool, which lists and describes all the risks, the date they were logged, what the potential impact of the risk is and how it can be mitigated. The risk list should also contain information about the probability and likelihood of each risk (high, medium, low) as well as an owner. In many projects, there is a tendency that the project manager ends up owning most of the mitigation strategies. But in many cases, a team member or a stakeholder is the best person to manage a specific risk because they are closer to the detail.In summaryProject management tools and techniques can be difficult to navigate for an entry-level project manager. Three of the most important tools for a project manager to make use of on any project are: a Project Definition Document, a Milestone Plan and a Risk List. Whereas the project manager owns all of these tools, it’s not sufficient to simply fill them in on their own. Irrespective of whether we are running an Agile, Waterfall or a hybrid project, it will be the collective effort of the people involved who will get the project delivered. For that reason, the tools we use must be as collaborative as possible so that we can make the most of our precious team.

The Three Most Fundamental Aspects of Project Management

1K
The Three Most Fundamental Aspects of Project Management

Over the years I have found that my most popular blog posts are those that speak to entry-level project managers. They value information which is clear and concise and which helps them understand what tools and techniques to use. Project management is a vast practice area and for somebody who has only recently started managing projects, it can seem overwhelming. It is my observation that there are more entry-level project managers coming into the field. And there is a good reason for that. With more and more changes taking place at a faster rate, we have a need for more people to manage those changes. This can be anything from integrating new technology to streamlining business processes or producing cheaper and better consumer goods. With that being said, let’s look at the three most fundamental project management tools and techniques that will help entry-level project managers get their project off the ground.

Project Definition

Projects need to be defined and scoped before they are planned and executed. That is true for all projects irrespective of the type of methodology they use. Defining the project helps us understand what it is meant to deliver, what the benefits are, what the costs might be and by when it is needed. This may sound like a plan to you, but it’s more like a high-level description of the project without the details having been fleshed out. The main question we ask during project definition is whether the project is worthwhile doing or not. There may be lots of ideas for new projects but not all of them have a good business rationale. Therefore they shouldn't be executed at this moment in time with this particular scope. In the company where you work, I’m sure there are many things you could improve on and many ways in which you could enhance your products or services. But not all of these enhancements will be viable business ideas, perhaps because there is a small market for some of those products or too low a margin.

When we define the project, we’re essentially looking at the project’s business case and ascertaining if it provides a strong enough foundation for the project to go ahead. Defining the project can take as little as a couple of days for a very small project and several months for a larger one. You can capture the conclusion of this phase in a Project Definition Document, Project Charter, Terms of Reference or Business Case. Different companies use different terms for this document, but they may essentially contain the same information. What I recommend you to put in the document is: Aims and objectives of the project, high-level deliverables, expected benefits, high-level constraints, assumptions and risks, expected costs, future revenues, expected end date, name of project sponsor, project manager, and core team members.

Milestone plan  

Once the project has been approved, meaning that the Project Definition Document has been signed off, you can move to the next part of the project, which is to plan it. The way you plan a project and lay out its phases, stages, and milestones will look a bit different depending on the methodology your company prefers. If you’re in a more traditional waterfall environment you’d be planning the project in a sequential way, beginning with requirements gathering and detailed statements of scope. You’d then plan for the build or execution phase to take place followed by some testing and final delivery or implantation. And of course, you’d plan for a project review to take place at the end. In more agile environments you’d carry out the above activities (requirements gathering, build, test, deliver, and review) in much shorter intervals or iterations. In addition, you’d deliver something tangible after each phase or iteration instead of all products or features being delivered at the end, which is what we do with a waterfall methodology.

No matter how you plan your project, it’s a good practice to plan it collaboratively with the team. Those days are over where the project manager was sitting in isolation behind their desk doing all the planning. That approach simply doesn't create buy-in from the team members. They want to be involved in planning the work that they are expected to carry out.

There are several collaborative planning techniques out there that you can make use of. I favour an old-fashioned post-it note-approach where you get people together and brainstorm what the phases, work streams and milestones of the project might look like. You’ll need lots of post-its and a white board or a wall to stick the notes onto. You also need a good facilitator (perhaps your good self) who can guide the team through the process. At the end, you should have a rough idea of which milestones and outputs will be delivered by when. You should also assign ownership to each milestone or deliverable as otherwise, the project manager may end up owning most of the items. Ask the owners to carry out the detailed planning of their individual items and revert at the next meeting with a confirmation of exactly what will be delivered by when. If your team is remote you can make use of virtual post-it-note planning tools.

The outcome of your collaborative meetings and planning activities can be captured in a milestone plan. This would be a simple Excel sheet listing the project’s top ten milestones, the owner of each milestone and the expected delivery date. Very simple! As a project moves forward you can also use the spreadsheet to record whether each milestone is on track for delivery and comment on their status. In that way, this simple one-pager overview of milestones becomes a high-level plan and a tracking tool in one. This is an ideal overview sheet to use as a communication tool to your stakeholders so that they can ascertain the status of the project. Your stakeholders don’t need a detailed plan. An overview of the top ten milestones will be sufficient. The detailed plan is reserved for the core team.

Risks list

Risk Management Lists


Be warned that no matter the size, complexity or methodology of your project, I can assure you that it will be full of risks. That’s because all projects are about creating change, meaning that the project will result in something that hasn’t been done before in that exact setting. In other words, every project is unique and therefore contains a certain element of risk. Project management methodology is essentially there to control risk and to help us execute a project with some level of predictability in spite of its uncertain elements. Defining a project, identifying and analysing user needs and requirements, planning how these requirements will result in outputs and deliveries, clarifying roles and responsibilities and prototyping the solution are all examples of activities we undertake in project management with the aim of driving down risk.

Managing risks is a dynamic process as the project’s environment changes on a daily basis. Identifying and mitigating risks is, therefore, something which shouldn’t just be done when the project starts up. It’s an essential project management activity that should be carried out on a regular basis to make sure that new risks are identified and managed and that the existing ones are reviewed. In essence, I suggest that you sit down with your team every couple of weeks to go through the risk list. The collaborative element is important, as the project manager cannot identify all the risks on her own. The team has the knowledge, not only of the things that could go wrong but also in terms of generating ideas for how to overcome potential roadblocks.

The outcome of the collaborative risk management meetings is risk list. This is a simple Excel tool, which lists and describes all the risks, the date they were logged, what the potential impact of the risk is and how it can be mitigated. The risk list should also contain information about the probability and likelihood of each risk (high, medium, low) as well as an owner. In many projects, there is a tendency that the project manager ends up owning most of the mitigation strategies. But in many cases, a team member or a stakeholder is the best person to manage a specific risk because they are closer to the detail.


In summary

Project management tools and techniques can be difficult to navigate for an entry-level project manager. Three of the most important tools for a project manager to make use of on any project are: a Project Definition Document, a Milestone Plan and a Risk List. Whereas the project manager owns all of these tools, it’s not sufficient to simply fill them in on their own. Irrespective of whether we are running an Agile, Waterfall or a hybrid project, it will be the collective effort of the people involved who will get the project delivered. For that reason, the tools we use must be as collaborative as possible so that we can make the most of our precious team.

Susanne

Susanne Madsen

Blog author

Susanne Madsen is an internationally recognised project leadership coach, trainer and consultant. She is the author of The Project Management Coaching Workbook and The Power of Project Leadership. Working with organisations globally she helps project managers step up and become better leaders.

Prior to setting up her own business, Susanne worked for almost 20 years in the corporate sector leading high-profile programmes of up to $30 million for organisations such as Standard Bank, Citigroup and JPMorgan Chase. She is a fully qualified Corporate and Executive coach, accredited by DISC and a regular contributor to the Association for Project Management (APM).

Susanne is also the co-founded The Project Leadership Institute, which is dedicated to building authentic project leaders by engaging the heart, the soul and the mind.

Join the Discussion

Your email address will not be published. Required fields are marked *

1 comments

Sukran 09 Jun 2018

Consulting is good for the fresher visiting this site .thanks m really interested in it program.

Suggested Blogs

Remove Your Mental Block, Open Up and Think in Terms of PMBOK’s Best Practices

Excerpt from the personal blog of KnowledgeHut Faculty – Satya Narayan Dash, PMP Aswin Krishnan H is a proud PMP today. His success is not only due to sound preparation, but also handling stress during the exam. He names it as the “smile” factor, as he has told below so uniquely. Aswin was part of my class in May, 2015. He is a very lively person and participates fully. In fact, I remember few instances where his enthusiastic participation were bringing surprised looks on some faces. In my view, enthusiasm is a great quality in any team member. But, unfortunately, it is highly underrated. I believe, enthusiasm is contagious and brings many into the fold of discussion. He called me after he was certified and I asked – “How does it feel to be a PMP?” He had a sense of happiness, relief and immense satisfaction. Below, he has outlined his experience in preparing for it, going through the PMP program and finally cracking the exam. Go on and read his experience.                                                               ************************************* Introductory – Why I decided on it and how I started? I was motivated to do PMP as part of my job and wanted to understand properly the Best Practices and how to use them with confidence in day to day activities as far as possible. Three of my friends were equally interested in doing Industry standard certification and when we began our search we had PRINCE 2 and PMP in our mind. Finally, we settled down with PMP which has huge demand in any industry. We then started our search for Training provider, found that it’s the Coach and his approach that help a lot in this kind of Certification, though online and word of mouth reviews we shortlisted Knowledge Hut. One of my friend had a successful experience in securing his PMP within a month after training with the Coach Mr. Satya Narayan Dash, He was really impressed by his practical approach, knowledge and personal commitment. He has previously attended PMP trainings from various centers but never could understand the concepts clearly, and failed in the exam miserably. He came from Chennai to do the course in Bangalore, just for the Coach. My PMP Training Experience: The training was very precise and covered all Knowledge Areas from the 5 Process Groups: Initiating, Planning, Executing, Monitoring and Controlling and Closing. Satya was very kind and use to share his personal experiences with certain problems which helped to see insights of approaches and reason why or what suits best based on the PMBOK Guide. He always helped us think about all the process and why each Input is given and what is the output of each process and why it is important, often in many of the companies we don’t practically use all the process or tools but the Coach’s insight in all tools and approaches was very helpful in understanding the Input, Tools and Techniques and Output (ITTO) for each Processes. We had classes on Weekends, the coach was very punctual and kept his timelines very strict. He was very happy to help even after the classes and he would stay back for us even if it was raining just to make sure that we get the idea of what is happening or why it is happening, He use to explain ‘Change Request’ or ‘Deliverable’ Flow by drawing pictures as it goes through each processes. These insights really helped in understanding the concept and the interrelationship between each process and ITTO. In the entire class there was fun, all were active and were participating which the coach always managed to make it interactive. Lot of things we need an actual physical person to explain to us rather than just going through hours and hours of Videos. I understood that having a real person standing in front of us will build that physiological effect, which will help me learn more and get motivated easily. My Own Study: I really wanted to complete the exam within 2 months after completing the class, but due to personal commitments it got extended to 4 months. Every-day I use to spend at the least 2-3 hours reading PMBOK 5th Edition, Rita Mulchay. This really solidified my understanding that was gained in the Classroom training.  In the last one or two months I use to keep on giving Mock Tests in the early mornings (4 -7 am) and then review them after coming back from work (7 – 8 pm), I kept on giving mock test from various places and was not be very subjective in selecting the source for exam. I felt that giving these mock tests really boosted my confidence and triggered to schedule the exam. While doing the mock tests most of the times I was in panic and I didn’t read all options and selected the wrong one. Rita Mulcahy’s recommendation helped. I read the options from D to A instead of A to D. This really increased my hit percentage. My PMP Exam Experience: I became a member, filled in my application, got my references and waited for a week to get it approved; luckily it was not selected for any audit. That was half way done, second challenge was to schedule the exam. I kept on giving mock tests until I had the confidence and was hitting 75-80% in mock tests. This triggered me to schedule an exam, at this time I just wanted it to get over at the earliest; luckily I found a date that was within 10 days and scheduled the exam on that day. I had formulated this strategy of completing 70 questions in an hour so I will be done within 3 hours at the max (200 questions) this I kept on applying while taking the mock tests and this strategy was quiet successful for me. On the Test day, I was faced with a flurry of Mathematical questions (20-25) from Question No#1 with all confusing stuffs and very wordy; I was very stressed, then I remember reading somewhere that even if you are stressed and if you manage to keep a smile on your face you can beat the stress. I applied the same and was able to get over the initial surprises in the exam. There were lots of situational questions, I was confused in lots of places; I marked them and kept on moving forward without worrying about the lengthy or wordy questions and kept on answering whichever I could. Finally, by the time I was done with 200 questions, it was like 2:30 hours; so I went back and selected all the unanswered and marked ones and slowly went through each one of them, now ‘smile’ factor worked and was able to easily and clearly read the questions and answer them. I completed all left outs within 45 minutes. Now I started reviewing again from beginning and just kept on speed reading questions and selected answers just to make sure that I did them correctly. The PMP really puts a toll on you with all sorts of Mathematical, Situational, and Tricky Questions, the initial impact of the questions is really intended to create stress, if you overcome that then you would be able to score very easily. During the exam I read the answers from D to A instead of A to D, I found this to be very helpful against panic answering due to stress. Suggestions for PMP Aspirants: – Dos Please read PMBOK at the least twice, it is very helpful and answer to PMBOK and not to your personal experiences. Please take any book like Rita or Andy Crowe or Head First and complete them once before kick starting the mock tests. Please keep a smile on your face, even though you are stressed, this will help relieve stress and get back to your senses while taking test, if you are in panic answering mode read the answers from D to A than from A to D this will improve your hit rate, these helped me. Please do take 10-15 mock tests before attempting the exam, this really helped me understand where I stand and what my weakness is and helped to motivate and improve. Real life PM experience helps a lot while answering these questions during the exam. – Don’ts Don’t waste time prolonging the exam, use your time wisely and complete it at the earliest. Having too many materials won’t help as you will be confused when to complete them, don’t get overburdened. Conclusion: After earning PMP I am much relived, I can see the fruits of hard work getting paid off. Whenever you say that you are PMP, there is a peer respect, because all of them know how much committed you need to be to earn this prestigious qualification. I now see what things at work do work and what not and how they are interrelated. PMP is not just a one-time process, you can apply this leanings in each every aspect of your life which you are doing unconsciously. Finally If I CAN DO IT ANY ONE CAN. You just need to remove the mental block and open up and think more in terms with best practices put forward by PMBOK, and your personal commitment. Brief Profile:  I am Aswin Krishnan H and am a Project Manager with Hewlett-Packard, India. I have 9 years of experience in Telecom, Retail and Security Domain with .NET Platform.                                                               ******************************   Aswin’s online PMP credential is available at PMI’s online credential registry. I am thankful to Aswin for sharing his journey in achieving the PMP certification. I believe it will help you – the PMP aspirant – to have your own. This article was originally published on managementyogi.blogspot.in
Remove Your Mental Block, Open Up and Think in Ter...

Excerpt from the personal blog of KnowledgeHut Fac... Read More

Identifying Project Stakeholders in the “Project Management Professional” Way

Project Management Professional (PMP) certification is an industry recognized qualification for the Project Managers. PMP is the market indicator of experience, knowledge and enhancement of skills, which are required to lead and direct the project. PMPs are the crucial part of every organization. PMP qualified Project Managers reach the potential to handle multiple projects and turn them into tangible outputs, minimizing the various project constraints. At the onset of the project, it is important to identify the formal authority for the project, in the form of Project Charter. That means, we need to identify the Project Stakeholders. Identifying project stakeholders at the very beginning of the project is critical to project success. This process is carried out before the end-to-end planning stage of the project. It is a two stage process which is carried out when the stakeholders are not content. If a step intended to satisfy the stakeholders is actually not serving its purpose, we can call it anything but project success. The following steps are mandatory to keep a project running successfully- Identifying the stakeholders Inspecting the relationship of each stakeholder with the project to establish their level of interest in the project. Anyone and everyone can be the stakeholder. It includes the people whose business interests are impacted by the project, who can dominate or steer the project, or have more expectations from the project. A stakeholder is not necessarily a sponsor or board member. He or she can also be a team member or the project manager. Every single member associated with the project can be a stakeholder. So you can identify the stakeholders by the source of information on the Stakeholders (Input), working on that information (using the tools) and on outcome. Input:  Project Charter– It not only refers to the documents specifying the rights of the Project Manager, but also provides a list of the key Stakeholders (comprises of the Sponsor, Senior Management, or Consulting Management). Procurement Documents: In addition to Charter, the Procurement Document is a great source to the third party stakeholders falling lower in hierarchy. Enterprise Environmental Factors– EEF indicates how the rules and regulations, human resources and structure of the Organization etc. affect the project. One of the factors can be input, to identify the key stakeholders which gives us insight on who has the power to influence the project. Organizational Process Assets– OPA is the repository which keeps information about the past project, improvement from past projects, procedures, policies and standards in an assembled manner, so as to act as a reference for future projects. Tools and Techniques:  Stakeholder Analysis– It consists of analyzing the information from the input of identifying Stakeholders, which will assist us to select the stakeholder who can influence the project positively. So we can start recording the role of an individual, their point of interest, their influence level against the list of all stakeholders. You should examine the expectations and interests of all the listed stakeholders in details. This may help identify more stakeholders. In addition to that, we can handle all the stakeholders’ concern and make plans to address them. That is one good way we can convert negative stakeholders to positive ones. Once we have the relevant details, we can use those to classify the stakeholders depending on their interests, influence, support and power. We can use tools like Resistor, Neutral and Advocate to categorize Stakeholders: Resistor is a negative stakeholder who is not supporting the project. Neutral stakeholder does not support the project. In this case, the project manager tries to convert their interests positively. Advocate is a stakeholder who completely supports the project and also provides ideas to overcome the barriers if any. Output:  Stakeholder Register- All the information accumulated in stakeholder analysis helps us in creating a Stakeholder Register. A register comprises of all  the information in tabular form, whose size depends on the project size. It is the duty of the project manager to identify the potential stakeholders and note them down in the table, so as to ensure project success. Project Stakeholder Register is depicted below: Stakeholder Management Strategy– Stakeholder management strategy is formulated to plan the actions for the entire course of the project management. This strategy is made to minimize the negative influences on the project.          As per PMBOK 5th Edition, the Stakeholder management strategy document includes the following: Key Stakeholder’s impact on the project Stakeholders’ level of participation as per stakeholder analysis Groups designated to each stakeholder Assessment of Impact Potential strategy for gathering Support Collecting source of information on the stakeholder as an input, and working on that data using tools can help us in finding the positive stakeholder to enhance the level for project success.
1763
Identifying Project Stakeholders in the “Pro...

Project Management Professional (PMP) certificatio... Read More

How to make the transition from an Engineering Position to a Project Management Professional in 10 Steps?

When it comes to career advancement, getting pigeonholed could have serious repercussions. Moreover, if you have spent your last 6 to 10 years in the ranks of a technical position and thinking of attaining a managerial position, then obtaining a certificate in a Project Management Course is the way to go forward. On the other hand, you would be interested to know that only 20% of significant organizations actively operate leadership development programs and a meager 5% emphasize bringing out the managerial skills of their technical staff. The above data highlights the importance of a PMP certificate course in case you are designated as an engineer. As per an engineer who has pursued a project management certificate, his decision to pursue Project Management Professional certification was based on the fact that it helped him codify his work. Moreover, it was useful for him in future transitions. Another belief lied in the fact that it forced him to learn formalized project management strategies and techniques. Since obtaining his certificate in 2011, it has achieved the goal of solidifying his project management skills. On the other hand, it has also given him a formalized manner of viewing project management. According to him, it was well beyond the benefits of on-job training that he picked up in his engineering work.         As an engineer, it is quite probable that you would always be involved in some projects, either as team members or project leaders. The primary objective to pursue the Project Management Professional stands on two notions. The first is with the help of a PMP certificate; an engineer could codify the work and can make prosperous career transitions in the future. It would also help an engineer to learn formalized strategies related to Project Management. Here is the list of ten ways with the help of which you can facilitate your transition.  1. Enrolling yourself in a PMP Certification Course Obtaining a certificate in a PMP course is an industry standard for the aspiring managers as it depicts to the employers that you have achieved a high level of managerial education in successfully supervising a project. During the PMP course, you would come across the following learning objectives.  Conducting interviews and extracting valuable information Planning projects in a detailed manner and afterward establishing an optimal solution. Assigning and planning your resources most efficiently and cost-effectively. 2. Lay more emphasis on Emotional Intelligence (EI) You are an engineer, and you are well versed with the notion of Intelligence Quotient. In fact IQ got you where you are today. However, if you want to make a successful career transition, then EI is the best bet.   Emotional Intelligence usually encompasses your skills related to monitoring, managing and regulating the emotions in a healthy and balanced manner in a bid to achieve various business aims. In other words, as a project manager, you would have to rely 10% on your IQ and 90% on EI.  3. Improve your interpersonal skills It is a widely accepted fact that no company or organization would recognize you as a project manager if you sit at your desk all day. It is vital to develop your interaction skills with your fellow employees who would further boost your relationship with others. On the other hand, it would also profit your relationship with the senior managerial staff. Moreover, it would also assist you to convince them you are the right person for the job. 4. Emphasize on your dealing skills It is crucial for you to note that managers are required to negotiate deals on a daily basis. These dealing can encompass both minor negotiations and large contracts. However, it is also vital for you to note that the proper development of negotiation skills takes time and you can improve your negotiation skills with the help of an online course. Excellent negotiation skills would always help you to showcase your talents to the top administrators of the company.  5. Grow your determination  As a project manager, sometimes would truly test your patience. However, the best way to test the limits of your tolerance level is to stay affixed to your goals during a project. You have to keep the bigger picture in your mind while achieving the goals of Project Management. The duty of a project manager requires a thick skin to emerge victoriously. 6. Leading from the front The main aim of a Project Manager is to motivate those who are working on your instructions. On the other hand, the goal of a project is of utmost importance to you, but your workforce would have different priorities than the goal of your project. Hence, you need to gain adequate motivational skills to make sure that the purpose of your particular project gets fulfilled. 7. Always possess an attitude to learn and grow while working Besides maintaining an all-around knowledge of your organization's various departments, it is also vital on your part to have an opinion that would reap you with luxurious benefits. Standing still and learning nothing should never be your ideology while you are a manager of a project. 8. Get a mentor In case you are appointed as a Project Manager, you should always consult the professionals out there who possess the same kind of skills. Hence, make sure that you approach people with the desired skills so that he or she can guide you through the process of successfully managing a project in real industrial situations. However, the selection of a specific mentor is a personal matter. You should always be on the lookout for that kind of a mentor who can inspire, encourage, maintain high standards and interpret body language. You can also opt to attend team meetings with your mentor to make sure that you gain skills as per your mentor. 9. Emphasizing the use of project management tools Your knowledge and experience are of utmost importance to you and your organization. However, you also need to make sure that you utilize the tools that are available to project managers. To give you a crystal clear idea, some of the standard tools are Gantt Charts and Earned Value Analysis.    10. Opt for gaining experience of various stages of project management You would be well-aware of the fact that projects are usually split into multiple steps, and each one of these scenes comes with its own set of challenges. Hence, it can be said that if you are looking to progress from a technical position to a manager, you need to comprehend the importance of all these stages. You should always take care to pro-actively seek out new projects at various stages of their existence.   It is also vital to ensure on your part that you are involved in various stages of project management as your new organization would value your experience of being involved in all the steps.    11. You would be in an advantageous position if you come from a technical background If you have a technical background, then you can easily opt for the Technical project manager role. It is a situation where the technical background can be beneficial to your position. It would also be advantageous for your project and organization. 
1060
How to make the transition from an Engineering Pos...

When it comes to career advancement, getting pigeo... Read More

Useful links