Search This Blog

Loading...

15 May 2013

How to Memorize PMP Formulas

Four Keys to Memorizing Anything

Memorization is like eating my biscuits. You use a knife and a cutting board to cut them into smaller pieces. Then you bite them into even smaller pieces with your incisor before chewing and chewing with your molars, sometimes on the right side of your mouth, then on the left side of your mouth.

Memorizing a formula, you use a pen and paper to break it into parts. Then you repeatedly work on the pieces. Sometimes you write them and sometimes you say them out loud so you involve more than one sense. Unlike my biscuits, you put the pieces back together in medium-sized pieces and chew on them for a while before putting the whole formula together and chewing on it.

The keys so far are
  • Smaller pieces
  • Repetition
  • Multiple senses
  • Reassembly

The Fifth Key to Memorization

The remaining key is (drum roll, please!)
  • Analysis
If you can understand a formula, you can recreate it without memorizing as much of it.

Example:  Point of Total Assumption in a Cost Reimbursable Contract

  • PTA = ((Ceiling Price - Target Price)/Buyer's Share)) + Target Cost
(I have limited the scope of this post to memorizing the formula, so please don't expect an explanation of Cost Reimbursable Contracts.)

The first step in analysis is to restate the formula in a fashion more visually decipherable.
  • PTA = Target Cost  +  (Ceiling Price - Target Price) / (Buyer's Share)
Notice that I turned the formula around.  I like to write formulas the way you would see it graphed: with the biggest portion first, at the bottom. Look at the inconsistent way most people present the Cost Estimating formulas, and taking this liberty will make even more sense.

The contract is Cost Reimbursable, so the first part of the PTA is what we hope the cost will be, the Target Cost.
  • PTA = Target Cost + some ugly fraction
The two price points above the Target Cost are the Ceiling Price and the Target Price. The Ceiling is higher, so it goes first:
  • (Ceiling Price - Target Price)/something
Something is the Buyer's Share.  Sorry, you'll just have to memorize that.

This is the point where you take total assumption of your own learning and put the formula back together. Remember, the keys to memorizing are
  • Smaller pieces
  • Repetition
  • Multiple senses
  • Reassembly
  • Analysis

14 May 2013

Networking, Patience, and Self-torture

If I am looking out for a job and see that a guy in a senior position may be of help to me, how do I ‘pretend’ that I am of help for him and he should connect with me, when the reality is that in this case, atleast for the time-being the ‘help’ will be going only one way – him to me. For a direct person, who does not like beating around the bush and pretence, this networking bit becomes tricky. I know it is my weakness, but I am finding it hard to overcome it.


I go through the same doubts, especially when connecting to somebody who is many levels above me. But I look at it this way. We must take time to be polite.

The connection

Suppose you come home and, before you even put down your briefcase, your roommate or spouse starts telling you all the things on the repair list and all the things that went wrong today. To-the-point requests make people feel the same way.

People do things for friends that they will not do for strangers. Good manners includes telling a new acquaintance what you admire about them and explaining something you have in common. It establishes a bond. If you don’t have any reasons that you can turn into a compliment, then why are you connecting?

The request

Remember, it’s about your contact, not about you. You don’t want to put him in a position where he has to sound mean. So I ask, “If you think our interests fit, may I join your LinkedIn network?” or “…would you add me to your LinkedIn network?”

The offer

You try to connect with as many people as possible, right? If you, yourself, do not have confidence to offer help, you can still offer to connect them with somebody else who can help them. Sometimes I ask, “As I build my network, what skills or knowledge could I look for in people I might send your way?” (Of course, now, you have to start keeping track of the answers!)

Another way might be, “Does your organization face any challenges where I could watch for resources for you?”

Patience

I’m sure there are much better ways to say such things, and you should always adapt your words to the person you’re connecting with.

Remember, establish a relationship before asking for something. Better yet, don’t ask for anything until
  • they offer to help, or 
  • you have been able to do something for them.
When you’re desperate for work, it’s very hard to be patient, but it will get you much better results.

For further reading, see a great article with excellent comments:

05 May 2013

Differences between Risks and Issues in Projects, Part 1


Part 1 - Issues

People define issue in many ways, but in project management, issue has a special meaning.

In everyday English, one synonym for issue is topic. An issue is a situation that merits discussion.
For example, the issue of what caused the last ice age or the issue of whether man's contribution to climate change is greater than factors such as the variability of our sun.

Everyday issues include past, present, and future situations. Discussions about issued may or may not lead to actions. Often, when we say that something is an issue, we imply that people disagree about it.

In project management, an issue is a situation that merits consideration because it poses a threat or opportunity to the project. For example, the vendor left our parts to rust on the dock and will not ship them until they get paid, but our policy prohibits paying for the shipment until we receive and inspect it.

If the issue is significant, the project team will continue consideration by studying actions that would enhance, remedy, or avoid the situation. This can lead to change requests.

Copyright 2013 Richard M. Wheeler

27 April 2013

Links to Management Resources

General Management Resources

Process Asset Samples and Templates

Project Management Newsletters

Project Management Resources

Project Management Tools

Technical References

This is a work in progress. Add links to your favorites in the comments, below, and I'll add them.

10 April 2013

Understanding the Rule of Seven

Context: Discussion of the Rule of Seven in statistical process control 

Problem: In some industries, one cannot wait for repeatable errors as defects and errors lead to loss of life. I was told that, in pharmaceuticals, a certain % of death is acceptable and almost expected. The waiting process or period of time before halting tests or evaluations is where I am stuck.
First, let's use the terms specified value and control limit rather than errors or defects.
 
Also, we would normally discuss this topic in terms of parameters that have numeric values such as temperature, weight, and speed. In this conversation, we want to deal with measurable characteristics long before they result in catastrophic failures.

Rule 1. Out-of-bound conditions

If you have just one value outside the control limits, such as a severe side effect from a drug, you stop the process and figure out what went wrong. 

Rule 2. Calibrating the results

The Rule of Seven (or Run of Seven) does not apply to parameters that go outside the control limits. The Run of Seven applies when seven consecutive, acceptable values lie on the same side of the specified value. Such a situation indicates that the average has deviated from the desired value and you need to recalibrate the process so that the average is close to the specified value.

Illustrating with a made-up scenario

Suppose the scientists at Schpooky Pharmaceuticals want to test an inoculation against the HG (Heebie Geebie) virus. In order to train the immune system to fight off a full invasion of Heebie Geebies when somebody sneezes on us, the inoculation has to cause a fever of at least 0.5 degree F. They calibrate the variables in making the vaccine and in the dosage to cause a 1.0 degree F fever, or a temperature of 99.6 degrees F.  In this test, they set an upper control limit of 3.0 degrees, or a temperature of 101.6 degrees F.
 
Specifications:
  • T = 99.6 degrees F, average
  • 99.1 degrees F < T < 101.6 degrees F
Using the first rule, just one person develops a temperature of 103.0 degrees F. We stop the tests to see what's gone wrong because 103.0 > 101.6, the upper control limit.
 
Using the second rule, if we have seven consecutive people develop fevers between 99.6 and 101.6, we stop the tests to see what's gone wrong. These temperatures are all acceptable, but they are all greater than the desired value.
 
The Run of Seven indicates a special cause -- that is, one or more variables in the process need to be controlled. Maybe the dose is too large and needs to be reduced. Perhaps the HG virus needs to be baked five minutes longer. So we make the adjustments and then resume the trial.
 
These rules and others like them serve to stop a process long before it reaches catastrophic failure such as the death of a patient.

But catastrophic failures do happen

You might wonder, What about the catastrophic failures? They do happen! What about the one in 10,000 who dies? How can that be acceptable?
 
This takes us to other techniques such as Decision Tree analysis (p. 299 of the Project Management Institutes Project Management Body of Knowledge (PMBOK) Guide, 4th edition).
 
Suppose withholding the vaccine results in 1,000 deaths per 10,000, but giving the vaccine causes one death in 10,000. If you distribute the vaccine to 10,000, you save 999 lives.
 
Unfortunately, many drug companies withhold such drugs because that one in 10,000 will sue them, and the juries will severely punish the companies.
 
This issue, tort reform, is one of the dividing lines between the political parties in the US. A project manager needs to use various decision-making methods and maintain awareness of a wide range of environmental factors.

The Difference between Accuracy and Precision

In technology and science, accuracy and precision are different, although they go together.

For the measured characteristic
  • Precision is described by the range of values.
  • Accuracy is described by the difference between the average value and the specified value.
Lets have a goal of making two batches of cookies and specify that they measure 5" across. Afterwards, we measure the cookies.

Chocolate cookie widths
  • Average = 5.10 "
  • Range = 0.25"
Cinnamon cookie widths
  • Average = 5.01"
  • Range = 0.50"
The chocolate cookies have a smaller range of sizes, so they are more precise. The average size of the Cinnamon cookies comes closer to the specified value, though, so they are more accurate.
 
Does that seem counterintuitive?
 
For a measurement or a measuring tool
  • Precision is described by how many significant figures the tool gives you.
  • Accuracy is described by how closely the measurement matches the value of a standard device and also by how accurate the standard is.
As another example, I have two 18" rulers.
  • One came from a store that sells drafting supplies. It is graduated in 16ths of an inch.
  • The other, I made for myself after I loaned the store-bought ruler to a neighbor kid. I based it on one cubit (18"), the length from my elbow to my finger tips. When I graduated the cubit ruler in 50ths of an inch, I eyeballed the measurements and marked it by hand.
 The cubit ruler is more precise, but the store-bought ruler is more accurate.

24 March 2013

Project Management and Open Communications

Project Managers need to guard against setting up an environment where bad news never reaches them. They need to praise and encourage those who communicate risks before they become issues, issues before they become problems, and problems before they become project failures.

Some managers remind me of the Clinton trial in the Senate, following his impeachment in the House.

The Senate set up a rule requiring Ken Starr to keep all the records and evidence in another building. Bringing it to their offices without an invitation would have violated protocol.

Then the majority of senators refused to go view the evidence. A few who did view it said they came away weeping, and the rest (having refused to view the evidence) said that they lacked evidence sufficient to convict.

Does your comfort zone tempt you to maintain willful ignorance? Does your character allow reliance on plausible deniability? The PM has accountability for project success, which any lack of awareness may bring about; but that accountability extends to achieving success ethically.
 
I wonder:  Do PMs ever include ethical lapses as project risks?