Skip to main content

PMI-RMP Examination - A few pointers

I was one of the first takers for the exam, though I did not qualify for the fifty percent discount by a day. Took the exam in early November and it was quite an experience considering the fact there is very little information available as to the content and nature of the exam.

With the experience of having taken the PMP exam, comes in handy as the jargon used in the exam is very much in line with the PMI-PMP speak. It is imperative to note that though the exam was very much in line with the draft documentation on the Risk Management Process thats been published, it had a few elements of surprise as well.

As a risk manager, having been accustomed to taking risk in the negative connotation, it needs to be noted that RISK is considered positive as well as negative. This being the rule of the thumb, it facilitates in understanding the questions properly and to subsequently answer them.

The approach that I took to address the examination was to ensure that I run through the glossary from the PMBOK again. The PMBOK contains material that speak in PMInese and it helps a lot to understand the same language that is used in the RMP exam. Having run through it as well as the material in the PMBOK, the draft publication comes in handy. Even though still in draft stage, it provides the major inputs as to the thinking in vogue at PMI and their perception of risk and therefore its management. The draft is work in progress and we would see more eloboration as the time moves ahead.

It is to laud PMI for taking the initiative to bring into the mainstream the need for risk managers , who are a different set of people with specific skill sets to handle risks in a project. Large projects tend to fail as a consequence of not understanding the risks or underplaying risks. This leads to scheduling conflicts, errors in estimation and resource misallocation. The need to manage risk and its components both positive and negative helps in identification of the set of variables that affect the outcome of the project as well as the overall health of the project as various milestones are met.

Risk Management as a tool is very effective in many other ways not apparent. For example safety that is often overlooked would very much be represented when a full fledged management principle to include risk is incorporated into project management. Well, looks like I have digressed from the examination point of view to that about risk management in projects. However, as I was answering the questions, it became so obvious as to how much you learn at work, the questions were real life scenarios and if you have handled a few projects, you would be in a position to answer many of the questions. This is something that you do not find often in many examinations, but certainly the PMI-RMP makes the difference in this area.

Do drop me a mail, if you need some more information, I would be more than willing to help

Comments

Popular posts from this blog

Malware Damage - It is real and you need to be ready ...

  Malware, short for "malicious software," is any software intentionally designed to cause harm to computer systems, networks, or devices. Malware can take many forms, including viruses, trojan horses, worms, ransomware, spyware, and adware, among others. The dangers of malware are numerous, and it is crucial to protect yourself from malware to avoid serious consequences, such as: Data theft: Malware can be designed to steal personal information, such as bank account details, social security numbers, and login credentials. Once this information is stolen, it can be used for identity theft, financial fraud, and other malicious activities. System damage: Some malware can damage your computer system, causing it to crash or malfunction. This can result in lost data, system downtime, and costly repairs. Financial loss: Malware can also be used to extort money from victims. For example, ransomware can lock down a victim's computer and demand payment in exchange for the decrypti...

CIO Questions answered - Your comments welcome - The reflections of the inner self

Briefly describe the typical size and organization of an IT team that you have managed. Include the division of responsibilities, how you track progress, etc. My experience ranges from me working independently, mainly to maintain my independence when I perform audits to managing a team of more than 25 - 100 consultants in various roles. I have handled multiple projects simultaneously where we have multiple consultants (typically from five to ten) working on multiple projects. We have used a set of tools to specifically monitor progress as well as the milestones. The projects involved were simple roll out of products (Microsoft Active Directory Domain Builds, Log Consolidation, Vulnerability Management) in line with product specifications to complex integration of systems that involves building multiple SoA interfaces for healthcare applications. For a successful project there needs to be proper delegation, personally I believe a person can deliver if he is not micromanaged, identifyi...

A Roadmap to move from Cloud to In premise - The reverse migration -- Is Cloudflation at myth?

 Cloudflation as a term is being used and talks on the spiralling cost of cloud bills for an organization. The easily available and provisioning options leads to workloads that run for no reasons, orphaned accounts and a gamut of costs that are accrued by multiple departments without much of an oversight. There is a trend to reduce the workloads and have a semblance of order. It is imperative that we have plans that helps to reverse the migration to cloud and bring back some of the workloads that might work cheaper to run local. Is there a roadmap to achieve this goal? A few pointers in this direction A roadmap for moving from the cloud to in-premise computing should include the following steps: Assess current workloads: Assess the current workloads that are running on the cloud and determine which workloads would be most suitable for in-premise computing. Identify in-premise infrastructure: Identify the in-premise infrastructure that will be needed to run the identified workloads....