Some Nice Questions - Part 3

31: How do you know your Quality Benchmarks before you start building?

That’s what your Organizational Process Assets are for. Since your company keeps a record of all of the projects that have been done over the years, those projects’ quality measurements can help you get a gauge on how your project will perform too. If your company knows that all of the
projects in your division had a cost of quality that was 40% of the cost of the overall cost of development, you might set 40% cost of quality as a benchmark for your project as well. Your company might have stated a goal of having a schedule variance of plus or minus 10% on all projects for this calendar year. In that case, the schedule variance is a benchmark for your project

32: I don’t really have good requirements for my projects because everyone on the team starts out with just a good idea of what we’re building. How do I handle quality?

You should never do that. Remember how you spent all that time collecting requrements in the Collect Requirements process? Well, this is why you needed them. And it’s why it’s your responsibility to make sure that the project starts out with good, well-defined, and correct requirements. If you don’t have them, you can’t measure quality—and quality is an important part of Pproject management. Without requirements, you have no idea what the product is supposed to do, and that means you can’t judge its quality. You can learn a lot about a product by testing it, but without knowing its requirements, a product could pass all of its tests and still not do what the customer expects it to do. So having good requirements really is the only way to know whether or not your product is high quality.

33: If I am trying to prevent quality problems, why can’t I just test more?

You can find a lot of problems by testing. If you find them during testing, then you have to go back and fix them. The later you find them, the more expensive they are to fix. It’s much better for everybody if you never put the bugs in the product in the first place. It’s much easier to fix a problem in a specification document than it is to fix it in a finished product. That’s why most of the Plan Quality process group is centered around setting standards and doing reviews to be sure that bugs are never put into your product and, if they are, they’re caught as early as possible.

34: Is the RACI chart really necessary?

Yes, definitely! Sometimes people split up responsibilities in ways that aren’t immediately obvious just from people’s titles or the names of their roles on the project—that’s one of the big advantages of a matrixed organization. RACI charts help everyone figure out their assignments.

35: Can the “halo effect” really affect my projects?

The halo effect is something that happens when you’ve got a team member who’s very good at a job—especially a technical job, like computer programmer or engineer. It’s easy to forget that just because someone is very good at one job, it doesn’t mean he or she has the skills to do another,equally hard job. This happens a lot with functional managers: the top programmer will often get promoted to a management position… but if she doesn’t have management or leadership skills, then the company just lost their best programmer and gained a lousy manager.


36: Per the PMBOK, it sounds like compromise is a bad thing. But I’ve been told that when people are fighting, I should always look for a middle ground!?

Yes, as little kids a lot of us were told that we should always look for a compromise. And that probably is the right thing to do on the playground. But when you’re managing a project, you’re judged by the success of your final product, not by how happy your team is. When you forge a compromise instead of really figuring out what’s causing the problem, you’re usually taking the easy way out.

37: What do I do with lessons learned after I write them?

The great thing about lessons learned is that you get to help other project managers with them. You add them to your company’s process asset library, and other project managers then use them for planning their projects.

38: Do I have to know everything that will be communicated to build a plan?

No. As you learn more about the project you can always update the plan to include new information as you learn it. Pretty much all of the planning processes allow for progressive elaboration. You plan as much as you can up front, and then put all changes through change control from then on. So, if you find something new, put in a change request and update the plan when it’s approved.

39: What’s the difference between active and effective listening?

Some of the communications ideas do have names that are a little confusing. But don’t worry, they’re really easy concepts for you to understand.

Active listening just means when you’re listening to something, you keep alert and take specific actions that help make sure you understand. It includes both effective listening and feedback.
Effective listening is a way that you do active listening—it means paying attention to both verbal and nonverbal communication. Feedback means doing things like repeating back the words that you were told in order to make sure you understood them, and giving your own nonverbal cues to show the speaker that you got the message.

40: Are nonverbal and paralingual communication the same thing?

They are very similar, but they’re not exactly the same. Nonverbal communication is any kind of communication that doesn’t use words. That includes things like changing your body language, making eye contact, and using gestures. Paralingual communication is a kind of nonverbal communication—it’s changing your tone of voice or intonation, finding ways to communicate things above and beyond just the words that you’re saying. For example, the same words mean very different things if you say them sarcastically than if you say them in a normal tone of voice.

41: What if people disagree on how to rank risks?

There are a lot of ways to think about risks. If a risk has a large impact on your part of the project or your goals, you can bet that it will seem more important to you than the stuff that affects other people in the group. The best way to keep the right perspective is to keep everybody on the team evaluating risks based on how they affect the overall project goals. If everyone focuses on the effect each risk will have on your project’s constraints, risks will get ranked in the order that is best for everybody.

42: How do I know if I’ve got all the risks?

Unfortunately, you never know the answer to that one. That’s why it’s important to keep monitoring your risk register throughout the project. It’s important that you are constantly updating it and that you never let it sit and collect dust. You should be looking for risks throughout all phases of your project, not just when you’re starting out.

43: What’s the point in even tracking low-priority risks? Why do we need the Watchlist in the first place when the risks are low priority?

Actually, watchlists are just a list of all of the risks that you want to monitor as the project goes on. You might be watching them to see if conditions change and make them more likely to happen. By keeping a watchlist, you make sure that all of the risks that seem low priority when you are doing your analysis get caught before they cause serious damage if they become more likely later in the project. The conditions that cause a risk are called triggers. So, say you have a plan set up to deal with storms, and you know that you might track a trigger for lightning damage, such as a thunderstorm. If there’s no thunderstorm, it’s really unlikely that you will see lightning damage, but once the storm has started, the chance for the risk to occur skyrockets.

44: I can figure out how much the risk costs using EMV, or I can do it with Decision Tree Analysis. Why do I need two ways to do this?

That’s a good question. If you take a really careful look at how you do Decision Tree Analysis, you might notice something... it’s actually doing exactly the same thing as EMV. It turns out that those two techniques are really similar, except that EMV does it using numbers and Decision Tree Analysis spells out the same calculation using a picture.

It turns out that there are a lot of EMV techniques, and decision tree analysis is just one of them. But it’s the one you need to know for the test, because it’s the one that helps you make decisions by figuring out the EMV for each option. You can bet that you’ll see a question or two that asks you to calculate the EMV for a project based on decision tree like the one on the facing page. As long as you remember that risks are negative numbers and that opportunities are positive ones, you should do fine.

45: Why do we do risk audits?

Risk audits are when you have someone from outside your project come in and review your risk register—your risks and your risk responses—to make sure you got it right. The reason we do it is because risks are so important that getting a new set of eyes on them is worth the time.

46: Do I always need to hold a bidder conference whenever I do procurement?

No, you don’t always need a bidder conference. Sometimes your company has a preferred supplier who you always deal with, so you don’t have to advertise for sellers. And sometimes there’s a sole source for a particular service or part—there may only be one company that provides it. In that case, advertising and bidder conferences would be pointless.

The bidder conference has two goals. The first is to make sure that you answer all of the questions from potential sellers. But the other is to make sure that all potential sellers are treated equally and have access to the same information.

47: Once a contract is signed, does that mean it’s never allowed to change?

No. This confuses some people, because when you sign a contract, it’s legally binding—which means you must abide by the terms of the contract. But that doesn’t mean those terms can’t change. If both the buyer and the seller agree to make a change to the contract, then they have every right to do so. That’s why you have a contract change control system—so you can Pmake sure these changes are made properly. But you can’t always assume that you have the ability to change a contract that you’re not happy with. Once your company has agreed to a contract, then you’re absolutely required to meet its terms and complete your side of it. If you want to make a change to it, you need to negotiate that change, and it’s possible that the seller won’t agree to it—just like you have every right to refuse an unreasonable change that the seller requests.

48: What is the difference between a performance review and an audit?

The difference is that performance reviews are about the work, while inspections and audits are about the deliverables and products. You’ll use a performance review when you want to make sure that the team at the seller is doing every activity that they should. For example, if you have a contract that requires the seller to perform certain quality control or project management tasks, you might conduct a performance review where you observe the team and verify that they do those tasks. On the other hand, if you want to make sure that the products that the team is producing meet your requirements and standards, you’ll send out an auditor to inspect the products that the seller is making to verify that they meet the requirements.

49: Do I Really need to follow all these Ethics & Professional Responsibility ideas outlined by the PMI?

Yes, absolutely. Being a PMP means you are a cut above the rest of the people who may do project management and one of the key distinctions is the expectation that a PMP Certified individual will be fair in his practices and work with honesty and integrity. Though accepting/giving a bribe or taking a short cut may not mean much harm, the point here is that, are you doing the right thing? When you ask yourself this question "Is this correct and legal?" and the answer is "NO" then you are not supposed to do it. I do agree that in real life situations there may be more than one reason to make a decision, but the most important should always be "Is this Ethical & Legal" irrespective of the situation and that is what PMI encourages.

If you have any more questions, dont hesitate to leave it as a comment and I shall try to answer them!!!

Some More Questions:

More Questions - Part 1
More Questions - Part 2

Some Nice Questions - Part 2

16: Is product analysis the same as requirements gathering?

Not exactly. When people gather requirements, they’re trying to understand what needs the product should fill. Requirements are the contents of the
product. When you use product analysis to define the scope of the work to be done, you’re figuring out what deliverables the team needs to work on in order to build your scope statement. So product analysis is concerned with how the work will be done, not what’s in it.

17: What if a stakeholder can’t tell me how to measure his needs?

That can get kind of tricky. Sometimes stakeholders know that they want things to get better, but they don’t know how to tell when they’ve
succeeded. You need to work with them to find something that can be measured in their ideas about project success. Without a way to measure your success, you won’t know whether or not you are accomplishing your goals.

18: What if I don’t know enough to estimate the cost of a work package? What do I add to the WBS Dictionary?

The WBS Dictionary should only contain information that you can fill in when you create it. A lot of the time, you’ll know all of the information that needs to go into it. If you have an estimate and know the resources that should be used, then put it in. But if all you have is a statement of work and an account code, then that’s all the information you’ll be able to add to the entry.

19: What happens if I need to change the scope?

You need to put it through change control – just like a change to the product scope. As you’re building the product, it’s always possible that some work will pop up in an P unexpected place. It could be that the initial technical design is inadequate or buggy. Or maybe you just think of a better way to do things while you’re working. In either case, you have to determine the impact to the schedule, the budget, the scope, and the quality of the product and put the proposed change through change control. That’s what it means to look at the project constraints every time there’s a change.

Once everyone understands the impact and approves the change, you need to go back and adjust your scope baseline to include the new work. If your budget or schedule are affected, you’ll need to change those baselines too and integrate all of them into the project management plan

20: How do I know when I have decomposed the work to a small enough work package?

The short answer is that you should decompose that work until it is manageable. You need to be careful when you come up with the work packages for
your WBS. If you decompose to the most granular level, you could end up wasting everybody’s time trying to figure out exactly how much effort goes into, say, “writing up meeting minutes” for each and Pevery meeting in your project. So, you should break down the work to small enough packages that everybody can understand what’s being done and describe it in the dictionary… and no further.

21: Can you explain the difference between the Scope Management Plan and the Project Management Plan?
Remember how the Project Management Plan was divided into subsidiary plans? The Project Management Plan tells you how to manage all of the different knowledge areas, and it has baselines for the scope, schedule and budget.

The Scope Management Plan is one of those subsidiary plans. It has really specific procedures for managing scope. For example, it tells us which stakeholders we need to talk to when gathering requirements. It lists what tools and techniques we are planning to use when we use the Scope Definition to define the scope. And when there’s an inevitable change because even the best project manager can’t prevent every change, it gives him procedures for doing Scope Management. So even though the Scope Management Plan is created in the Develop Project Management Plan process, it’s used throughout all of the Scope Management processes.

22: Is Control Scope always about work and project scope? Can it ever be about deliverables and product scope?

No. The Control Scope process is always about the work that the team does, because the whole Scope Management knowledge area is about the project scope, not the product scope. In other words, as a project manager, you manage the work that the team is doing, not the things that they’re making. Now, that doesn’t mean you should never pay attention to deliverables. You still need to pay attention to the scope of the product, too, since the two are pretty closely related. Any time you make changes to the project scope, it affects the product scope, and vice versa.

23: What if a change is really small? Do I still have to go through all of this Change Control Process?

Yes. Sometimes what seems like a really small change to the scope—like just adding one tiny work package—turns out to be really complex when you take a closer look at it. It could have a whole lot of dependencies, or cause a lot of trouble in other work packages. If you don’t give it careful consideration, you could find yourself watching your scope creep out of control. Each and every change needs to be evaluated in terms of impact. If there is any impact to the project constraints—time, cost, scope, quality, resources, or risk, you have to put it through change control. No Exceptions here.

24: What if I need a resource that isn’t available when my project needs it?

This is one of the reasons that project management is a tough job! When you need a resource that isn’t available, you need to negotiate for it. Your project depends on getting this resource, and without it your project won’t get done. You need it, or you’ll face delays! You have to do whatever you can to get that resource for your project. You can look in the other departments of your company or hire a contractor or hire a person from another company. At the end of the day, your job is to staff resources for your project and how you do it, is entirely upto your discretion. (Of course, dont forget management & budgetary approvals before hiring contractors or people from other company's)

25: Since reserve analysis lets me use buffers, why can’t I just put everything I don’t know about into the reserve?

The idea behind reserve analysis is that there are always unknowns on any project, but you can account for these unknowns by taking your best guess at what’s going to go wrong and inserting a buffer. But you can’t just make an enormous reserve, because then there’s no reason to ever do any estimation! The entire project becomes one big unknown, and that’s not particularly useful to anyone.

26: What if there’s a path that’s not critical, but where even a small slip in one activity would delay the project?

This is exactly why it’s important to know the float for each of your activities. When you’re managing your project, it’s not enough to just pay attention to the activities on the critical path. You need to look for any activity with a low float. And don’t forget that there may be some activities that aren’t on the critical path but still have a float of zero! These are the ones where you really want to pay attention and watch out for potential resource problems.

27: Would I really use this critical path stuff in real life, or is it just something I need to memorize for the PMP exam?

Yes, critical path analysis really is important in real life! Sure, for a small project with a dozen or so activities, it’s pretty easy to figure out which activities are critical and which can slip by a little bit. But what happens if you’ve got a project with dozens of team members and hundreds of activities?

That’s where critical path analysis can come in very handy. For a project like that, you’d probably be using project management software rather than calculating the critical path yourself, and the software will be able to highlight that path for you. Pay special attention to all of the activities that are on the critical path—those are the ones that could potentially delay the project.

28: Don’t we need to go through change control before we update the resource requirements or the activity attributes?

No. You need to go through change control if you are requesting changes to, say, your cost management plan. But while you are working on creating your schedule, everything you have created as part of the Time Management knowledge P area is fair game.

As you work your way through your network diagram and figure out new dependencies, you are going to find that you need more resources for some items or that the activity itself has changed. That’s why this process gives you the freedom to refine your earlier idea and make all of the time management documents in sync with your new understanding. The Develop Schedule process is about taking all of the information you are able to think of up front and putting it into a schedule that is realistic. When you are done with this process, you should have a really good idea of what you are going to do, who will do it, and how long it will take.

29: We always want to do our projects as quickly as we can. Why don’t we always fast-track and crash our schedules?

Because crashing is expensive and fast-tracking is risky. While it may look good on paper to add a lot of resources to a project that is running late, it often adds so much management overhead and training issues that Pthe project just comes in later.

Even though it might seem like some predecessors are really unnecessary, you usually planned them for a reason. So when you break your dependencies to fasttrack your project, you can significantly compromise the quality of the work that gets done. That means you might have to redo it altogether—which would probably take a Plot of time. While fast-tracking and crashing might work sometimes, they always add both risk and cost to your project.

30: In my job I am just handed a budget. How does estimating help me?

In the course of estimating, you might find that the budget you have been given is not realistic. Better to know that while you’re planning, before you get too far into the project work than later. You can present your findings to the sponsor and take corrective action right away if your estimate comes in pretty far off target. Your sponsor and your project team will thank you for it.

Some More Questions:

More Questions - Part 1
More Questions - Part 3

Some Nice Questions - Part 1

1: What are the differences between a project coordinator and a project expediter?

They’re actually pretty similar. A project expediter is somebody who keeps track of status but has no decision-making authority on a project at all. A project coordinator is someone who does pretty much the same thing, but does get to make some of the minor decisions on the project without having to run them by the functional manager. Coordinators usually report to somebody who is pretty high up in the organization, while expediters are more like assistants to the functional manager. Both of them usually exist in weak-matrix or functional organizations.

2: Does the PMP exam favor any kind of organization?

When you’re taking the PMP exam, if you see a question that mentions a PM, then you should assume that the question is asking about a matrix organization if it doesn’t say up front which kind of organization is being described. Functional organizations are usually painted in a negative light because they tend to give less authority to project managers.

3: what’s the difference between process groups and knowledge areas?

The process groups divide up the processes by function. The knowledge areas divide the same processes up by subject matter. Think of the process groups as being about the actions you take on your project, and the knowledge areas as the things you P need to understand. In other words, the knowledge areas are more about helping you understand the PMBOK® Guide material than about running your project. But that doesn’t mean that every knowledge area has a process in every process group! For example, the Initiating process group only has two processes, and they both show up in the Integration Management knowledge area. The Risk Management knowledge area only has Planning and Monitoring & Controlling processes. So the process groups and the knowledge areas are two different ways to think about all of the processes, but they don’t really overlap.

4: Can a process be part of more than one process group?

No, each of the processes belongs to only one process group. The best way to figure out which group a process belongs to is to remember what that process does. If the process is about defining high-level goals of the project, it’s in Initiating. If it’s about planning the work, it’s in Planning. If you are actually doing the work, it’s in Executing. If you’re tracking the work and finding problems, it’s in Monitoring & Controlling. And if you’re finishing stuff off after you’ve delivered the product, that’s Closing.

5: Do you do all of the processes in every project?

Not always. Some of the processes only apply to projectized organizations or subcontracted work, so if your company doesn’t do that kind of thing, then you won’t need those processes. But if you want to make your projects come out well, then it really does make sense to use the processes. Even a small project can benefit from taking the time to plan out the way you’ll handle all of the knowledge areas. If you do your homework and pay attention to all of the processes, you can avoid most of the big problems that cause projects to run into trouble!


6: At a high level, the initiating & planning process groups look very similar. Are they really different?

Initiating is everything you do when you first start a project. You start by writing down (at a very high level) what the project is going to produce, who’s in charge of it, and what tools they need to do the work. In a lot of companies, the
project manager isn’t even involved in a lot of this. Planning just means going into more detail about all of that as you learn

more about it, and writing down specifically how you’re going to do the work. The Planning processes are where the project
manager is really in control and does most of the work.

7: What are Enterprise Environmental Factors?

Enterprise Environmental Factors tell you about how your company does business. There’s a lot of information about your company that will be really useful to you when you’re planning your project. You need to know how each of the different departments operates, the market conditions you’re working in, the company’s overall strategy, any policies you need to work with, your company’s culture, and all about the people who work at the company.

8: What are Organizational Process Assets?

Organizational Process Assets tell you about how your company normally runs its projects. Every company has standards for how to run their projects. There are guidelines and instructions for managing projects, procedures you need to follow, categories for various things you need to keep track of, and templates for all of the various documents that you need to create. These things are usually stored in some sort of library. One of the most important organizational process assets is called lessons learned, which is how you keep track of valuable historical information about your project. At the end of every project, you sit down with the project team and write down everything you learned about the project. This includes both positive and negative things. That way, when you or another project manager in your company plans the next project, you can take advantage of the lessons you learned on this one.

9: How is the Business Case different from the Project Charter?

The business case is a description of what your company is trying to get out of the project—like how much money you’re planning on making from the project, how it will benefit parts of your organization, and future business you might gain from the project.P PT he project charter is a high-level description of your project. It tells you—and anyone else who needs to know about your project—what you’ll be delivering, including a really high-level description of what it is that you’ll build. A really important difference between them is that the project charter is what authorizes the project manager to do the work, while the business case helps give justification for the project. You can think of the business case as the background research that had to be done in order to make sure the project was worth doing, and the project charter as the thing that formally announces the decision to do it.

10: Do Project Sponsors really type & create the Project charter? Usually Sponsors are people in high positions in a company and do they do such tasks as well?

This is actually a very nice question. Sponsors are important people in an organization and that’s exactly why the project sponsor will often delegate the actual creation of the charter to the project manager. For the exam, though, keep in mind that the sponsor is ultimately responsible for creation of the charter irrespective of whether he types the whole thing or delegates it to someone else.

11: Isn’t a project plan just something I get out of Microsoft Project?

No. The project management plan is not the same thing as a project schedule. You’ll use a tool like Microsoft Project when you’re doing Time Management to build the project schedule. (It’s also useful for other knowledge areas as well.) But you’ll use your project management plan as a guide to help you develop that schedule. It will tell you what tools to use when you develop it, and how changes will be handled.


12: What is a performance baseline and what do I do with it?

A performance baseline is a snapshot of your project’s scope, schedule, and cost. When you plan out the work you’ll do on a project, you write it down all of the activities you’ll need to do and save that understanding as your scope baseline. You’ll do the same with your understanding of the project’s schedule and its cost. That way, you can always compare your actual
performance to your plan. Every time a change is approved, that means the plan has changed. So you have to update your baseline to include the new work (or cost, or schedule).

13: Can you explain Project Integration Management in one line?

Integration Management means making sure that all of the processes work together seamlessly to make your project successful.

14: Does the project manager care only about the project scope? Doesn’t he care about the product scope?

No, you still need to think about your project’s final product. You can never ignore product scope, because most projects have changes to the product scope along the way. You’ll have to change your product scope to include the work that’s caused by
product scope changes. Changes like that will probably have an impact on time and cost, too.

For Ex: Lets saty, you are the project manager who manages a project that is part of the scope of Product X. If somebody asks for a new feature in Product X, the first thing the team needs to do is understand how much work is involved to accommodate it, and what that scope change will do to the cost and schedule. As a project manager, your main concern is understanding that impact, and making sure everyone is OK with it before the change gets made. It’s not your job to decide which is the best feature for the product, just to help everybody involved keep their priorities in mind and do what’s best for the project.


15: How do I know when I am done collecting requirements?

That’s a good question. Your requirements need to be measurable to be complete. So it’s not enough to write down that you want good performance in your product. You need to be able to tell people what measurement counts as good performance for you. You have to be able to confirm that all of your requirements are met when you close out your project, so you can’t leave requirements up to interpretation. You know your requirements are complete when you’ve got a way to verify each of them once they’re built.

Some More Questions:

More Questions - Part 2
More Questions - Part 3

Tips to get PMP Certified

Below are some tips I picked up from various books about taking the PMP Certification Exam.


1. PMI has a very formal way of naming processes, process groups, knowledge areas, and even documents. However, just like in real life, do not expect that the exam will always refer to these names in a formal way. Try to know both the formal and informal representation of each key term. To help you further, I will try to obtain both those terms and use them in this blog.

2. The questions in the PMP exam can be wordy and might include unnecessary information to distract you from the real question/information related to the real question. So, you need to read the questions carefully and patiently and figure out what is relevant and what is nonsense.

3. Get comfortable with the idea that there will be some questions that you will not be able to answer correctly. In such a situation, just believe in yourself and your experience, and select the answer you feel would be the nearest match. If you are still not sure, just leave it for now and proceed to the next one. you can always come back to review them if you have time in the end.

Remember - Dont get frustrated.

4. There will be tricky questions to weed out candidates who might have project management experience, but who do not have an in-depth understanding of the discipline of project management from the perspective of PMI. Make sure you are cautious and catch hold of such questions and answer them appropriately.

5. There will be questions for which you will need to choose between an innocent way of skipping the formal process to save time and following the formal project management process. In almost all cases, the correct answer will be to follow the process.

Remember - Never ignore the process, atleast from the certification point of view.

6. There will be questions for which you will need to choose between facing the problem head on or taking an easy way out, such as dodging a thorny issue, ignoring a challenging problem, or postponing a difficult decision. Almost always, the correct answer is to meet the problem head on in a professional manner.

Remember - Ignoring a problem today might cause the same one to magnify and it will for sure come back to haunt you at a later date. So it is always better to handle problems then and there

7. To answer some questions correctly, understand that in the world of project management as seen from the perspective of PMI, project managers communicate directly and clearly and do not say things between the lines. For example, if you have a problem with a team member, you talk to the team member face to face rather than going to the member’s manager, which you might need to do eventually if you can’t solve the problem by directly dealing with the team member.

8. Understand clearly the roles of the key stakeholders of any project, such as the project manager, project sponsor, and customer. Especially understand your responsibilities as a project manager. You need to be proactive to make decisions and manage the project, influence the factors that contribute to changes rather than waiting for the changes to occur, and have up-to-date information about the project.

All the very best for your exam!!!

Previous: About the PMP Exam

Next: Main Parts in Managing a Project

About the PMP Exam

The Project Management Professional Certification is one of the most respected Certifications in the Software Development Industry. Getting PMP Certified is not easy and any individual with this certification is respected by everyone in the industry. This is what makes this a valuable addition to your resume if you are interested in Project Management as a Career.

A person with a PMP Certification represents the fact that, he/she is an established project manager and has the experience and expertise to manage projects effectively and make them a success.

Eligibility Requirements in order to take the PMP Exam:

Minimum Educational Background:

Category 1 – Bachelors Degree Category
Category 2 – High School Diploma

Minimum Project Management Experience:

Category 1 – 4500 Hours
Category 2 – 7500 Hours

Minimum Formal Project Management Education:

35 Contact Hours for both Category 1 and Category 2

Details of the PMP Exam:

The PMP Exam is a Multiple Choice type of Exam which will contain 175 questions and an additional 25 pretest questions.

Remember that the scores for these 25 questions do not affect your final score.

Getting PMP Certified:

Step 1: Register in the PMI Website
Step 2: Register for the 35 hour Project Management Training
Step 3: Read the PMBOK Guide and any other book (And my blog if you like) to prepare for the PMP Certification
Step 4: Decide your Exam Date and prepare properly
Step 5: Crack your exam and get your Certification

About this Blog:

This blog is an attempt to help you get PMP Certified. I am no Project Management expert either. I am currently preparing for my PMP Certification and reading many big books on the topic like the PMBOK Guide and others. The sequence of chapters in this blog are all based on my understanding of the topics learnt during my study.

This blog will be split into 5 sections each of them covering the various topics covered by the PMP Exam. Below are the % of questions that can be expected from the various topics in the PMP Certification.

Initiating the Project – 11%
Planning the Project – 23%
Executing the Project – 27%
Monitoring and Controlling the Project – 21%
Closing the Project – 9%
Professional & Social Responsibility – 9%

Total works out to 100% doesn’t it :)

For the most up-to-date information regarding these examinations, please visit the certification section of PMI’s website at www.pmi.org.

Next - Tips to Get PMP Certified