Saturday, April 30, 2016

Two doors and the risk manager


A narrative*

Imagine two doors to the same room: One labeled risk manager; the other labeled decision maker.
Though the risk manager's door, entry is for the inductive thinker: facts looking for a generality or integrating narrative
Through the decision maker's door, entry is for the deductive thinker: visionary with a need to connect specifics to the vision

And, consider this:
  • Pessimists with facts enter through the risk manager's door
  • Optimists with business-as-we-want-it enter through the decision maker's door
Then what happens?
Each needs to find the other. In the best of situations, they meet in the middle of the room where this is buffer space and flexibility.

How does the inductive and deductive interact?
Risk management does not set policy for the project office; it only sets the left and right hand boundaries for the vision, or for the project policies.
The space in between is where the decision maker gets to do their envisioning, moving about, perhaps even bouncing off the walls, constrained only by the risk boundaries.


Sound familiar? I hope so. You'll find a similar explanation known as the "project balance sheet" in Chapter 6 of "Maximizing Project Value: A project manager's guide". (Oh -- the book cover is shown below!)

In that balance sheet metaphor, the right side is for the fact-based inductive manager; the left side is for the visionary. And, since those two never agree fully, there is a gap.

And the gap is where the risk is. Risk is the balancing element between the vision and the facts. And who is the risk manager: the project team -- not the visionary. (That's why we pay the PMO the big bucks: to manage the risk!)

*This narrative adapted from "Playing to the Edge", pg 428


Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog

Wednesday, April 27, 2016

Action and effort



"[There is] a critical balance that any organization has to manage -- the balance between freedom of action for the parts and unity of effort for the whole.
Too little autonomy for the parts leads to inaction, inflexibility, hesitation, and lost opportunities.
Too little unity of effort means that individual [organizational] achievement is not synchronized, exploited, or leveraged"
General Michael Hayden
"Playing to the Edge"

Although he didn't say it as such, Hayden was very close to the Principle of Subsidiarity when he spoke of autonomy for the parts, and he was speaking like a system engineer when he spoke of unity of effort of the whole, especially the recognition that sequencing, phasing, and complimentary interaction -- without setting off chaotic responses -- is essential for getting the most out of the parts arranged as a system.



Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog

Sunday, April 24, 2016

Right or wrong; inclusion or exclusion


Sometimes it's about being right or wrong; but often it's about the fear of being excluded.
Thus, right or wrong gives way to the need and desire for inclusion -- having inside influence -- thus to avoid the hell of exclusion.

Paraphrased from the comments of 
David Brooks in an TV interview with Charlie Rose, March 2016

Of course, the unsaid thing is that the principles behind being "right" might be compromised on the altar of "inclusion".

Sometimes, the isolation of being "right" is overwhelming. It takes a special type to handle the outsider's role.

Sometimes, there's really no other choice.



Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog

Thursday, April 21, 2016

The evolution of cost management


  • In the beginning, cost often matters most*: the greatest amount at stake and the most politically sensitive parameter understandable by all, specialists and lay persons alike
  • In the middle, cost often takes a comparable priority to function; function has been promised and people have begun to count on it; there's less cost remaining at stake
  • In the end, cost is set aside as the schedule and function dominate. Success in a functional sense takes on a political priority ... functional failure is easiest to measure and has the longest effect on reputation
* Especially if the project is publically funded with taxpayer dollars.


Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog

Monday, April 18, 2016

"Yes is where the risk is"



General Michael Hayden, now retired, writes in his book* about his years as Director, NSA and Director, CIA that in government -- and likely all of elsewhere:
"Yes is where the risk is"

The meaning is straightforward: the safe thing is to just say No. In fact, it seems that in government particularly that the "staffers" main job is to protect their "principals" by saying No. "No" becomes the default; too easily automatic.

In effect: anyone can say No and gum up the works; few can say Yes, and fewer can Yes and make it stick.

But regarding the risk of "Yes", Hayden's point is well taken: to reach out, to lean forward, to make a difference, to add value .... at some point you are going to have to say "Yes", or insist that your principal say "Yes". At that point, risk arises!

Of course, the theme of Hayden's book is: Use all the space given to you. Play to the edge; just don't cross the chalk line. And, if you do play to maximize your space, then heads up! You'll be challenged by those that want to make your space smaller.


Did I mention: Your performance is on the line! (Don't screw this up)


* "Playing to the Edge", pg 121


Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog

Thursday, April 14, 2016

Political skills



Political skills: "The ability to manage the emotions of others"
David Brooks, political commentator
If your project is political or your organization or customer is political, think of Brooks' assertion: it's about manipulating your emotions.

Thus, if you want to participate as a political contributor, that is a skill you'll need.

But, if you want to be immune to the politics, then you'd better acquire bullet proofing for you emotions.



Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog

Wednesday, April 13, 2016

Procrastination (See: manage slack)


Are you a procrastinator?
Do you manage schedule?
Do you think of yourself as a risk manager? Do you understand the concept of schedule buffers and the critical chain methodology?

Then, you'll understand that handling your tendency to put things off, and managing slack and schedule buffers are not that much different.

In fact, what I see most of the time is managers wasting slack by doing a "latest start". At the other end, they've got no buffer or slack to work with. That is all wrong. In spite of the risk of incomplete information, getting over the inertia of getting started and getting going on addressing the issues that will inevitably arise is paramount.

So, if you need some help on this, this humorous video is for you!
 


Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog

Sunday, April 10, 2016

HMI checklist for system safety


  • Checklists are good
  • System safety is usually a necessary condition, if not a mandatory one
  • HMI is really important, especially in high stress situations where an intuitive understanding of the HMI is critical (See: various airline accidents where cockpit HMI was a contributing factor)
Combining all three of these, Matthew Squair has given us a nicely annotated tool to work with. Check it out here.
https://msquair.files.wordpress.com/2016/03/hmi-requirements-completeness-checklists.pdf


Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog

Friday, April 8, 2016

Failure modes




How do we fail? Let me count the ways
  • In the beginning, say the first Egyptian pyramid project, failure wasn't even talked about. If it happened, you just disappeared, and someone took your place -- properly incentivized not to repeat your experience
  • Advance a few millenniums and we arrive at "Failure is Not an Option". In this model, something -- anything -- that yields a strategically successful outcome is acceptable. It need not look anything like the intended
  • Advance a few decades and we get "You're allowed to fail"  followed closely by "Fail early!". In this model risk is a recognized and accepted partner to innovation, although certain contributors are not acceptable: incompetence, laziness, and recklessness to name three.  However, arrogance and eccentric behaviours are tolerated
  • Now, in present time, we arrive at "Fail early; fail hard" which morphs to "Fail Upward!" which we learn is something of an art. It's even advanced to the point of having a blog stream on Medium and, separately, a conference to learn how fail with success (if that is not an oxymoron)
So, what do we make of "fail upward"?  That's where you advance your career and your fortunes by having demonstrated an ability to "fail early; fail hard", a recognized elixir of the successful -- in the end, anyway -- strategic outcome. But, of course, it takes a second party -- someone with deep pockets -- that recognizes your talent. You can't be a loner and successfully fail -- it's a team sport.

Indeed, we learn from essayist Kate Losse, these insights:
Thanks, in part, to a playlist of TED talks on the productivity of failure, the dictum to “fail harder, fail faster” is now being peddled in fields from scientific research to elementary education.

Consider recently published books like Stuart Firestein’s “Failure: Why Science Is So Successful” and Jessica Lahey’s “The Gift of Failure,” which argues that children today occupy such risk-scrubbed environments that opportunities for failure must be manufactured.

At AltSchool, in Silicon Valley, where pre-K tuition is $27,000 a year, modeling failure is part of the curriculum"
Summary: Failure is an option!!
 


Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog

Tuesday, April 5, 2016

Weight of evidence



If you are into risk assessments, you may find yourself evaluating the data

Evaluating the data usually means testing its applicability with a hypothesis. The process usually cited in project management chapters about risk is this: 
A hypothesis is formed. And then the evidence against the hypothesis—observable data—is evaluated. If the evidence against is scant, the hypothesis is assumed valid; otherwise: false.
Guessing?

Is this guessing? The hypothesis is true because no one seems to object? After all, how much evidence is against? Enough, or have you taken the time to really look?

Most of us would agree: the evidence-against-the-hypothesis does not always fit the circumstances in many project situations.

There are many cases where you've come to the fork in the road; what to do? Famed baseball player Yogi Berra once posited: "When you come to the fork in the road, take it!"


In the PM context, Yogi is telling us that with no data to evaluate, either road is open. In Bayes* terms: it's 50:50 a-priori of there being an advantage of one road over another.

Weight of Evidence
Enter: weight-of-evidence**, a methodology for when there is some data, but yet there is still a fork in the road. In this case, we consider or evaluate each "road"—in project terms, models or suppositions—and look at the ratio of probabilities. 
  • Specifically, the probability of model-1 being the right way to go, given the data, versus the probability of model-2, given the data.
Each such ratio, given the observable data, conditions, or circumstances, is denoted by the letter K: K equals the ratio of probabilities

Philosophers and mathematicians have more or less agreed on these strength ratios:
Strength ratio, aka “K”
Implied strength of evidence favoring one over the other
1 - 3
Not really worth a mention
3 -20
Positive
20 – 150
Strong
> 150
Very strong

Why form a ratio?
It's somewhat like a tug-of-war with a rope:
  • Each team (numerator team and denominator team) pulls for their side.
  • The analogy is that the strength of the pull is the strength or weight of evidence. Obviously, the weight favors the team the pulls the greatest. Equal weight for each team is the case for the rope not moving.
  • K is representative of the strength of the pull; K can be greater than 1 (numerator team wins), less than 1 (denominator team wins), or equal to 1 which is the equal weight case.
More data
The importance and elegance of the methodology is felt when there are several data sets—perhaps from different sources, conditions, or times—and thus there are many unique calculations of "K". 

You might find you have a set of K’s: K1 from one pair of teams, but K2 from another, and so on. What to do with the disparate K’s?

Sum the evidence
The K’s represent the comparative weight of evidence in each case. Intuitively, we know we should sum up the "evidence" somehow. But, since "K" is a ratio, we really can't sum the K’s without handling (carefully) direction.
  • That is: how would you sum the odds of 2:1 (K = 2) and 1:2 (K = 2, but an opposite conclusion)? We know that the weights are equal but pulling in opposite directions. Less obvious, suppose the opposing odds were 2:1 and 1:5?
Add it up
Fortunately, this was all sorted some 70 years ago by mathematician Alan Turing. His insight: 
  • What really needs to happen is that the ratio's be multiplied such that 2:1 * 1:2 = 1. 
  • To wit: evidence in opposite direction cancels out and unity results.
But, hello! I thought we were going to sum the evidence. What's with the multiplying thing?
Ah hah!  One easy way to multiply—70 years ago to be sure—was to actually sum the logarithms of K
It's just like the decibel idea in power: Add 3db to the power is the same as multiplying power by 2
Is it guessing?
You may think of it this way: when you have to guess, and all you have is some data, you can always wow the audience by intoning: "weight of evidence"!

Appendix:
Geeks beyond this point
Does everyone remember the log of 2 is 0.3? If you do, then our example of summing odds of 2:1 and 1:2 becomes: Log(2) + Log(1/2) = 0.3 – 0.3 = 0.
Of course the anti-Log of 0 is 1, so we are back at the same result we had by intuitive reasoning.
On first examination, this might seem an unusual complication, but it's a take-off on the slide rule and the older decibel (dB) measurement of power. They both multiply by summing: a 3db increase in power (or volume) means the power has doubled.
An example
What if we had four sets of evidence: odds of {10:1; 2:1; 1:2; and 1:20}. What’s the weight of evidence?
Using logarithms: log(10) = 1, log(2) = 0.3, log(1/2) = -0.3; log(20) = log(10) + log(2),
{1 + 0.3 – 0.3 – 1.3} = - 0.3 or odds of 1:2
Not all that obvious
_____________________________________________
*Bayes refers to a protocol of evaluating probabilities, given some a-priori conditions, with the idea of discovering a-posterior an underlying probable “truth”. Such discovery depends on an opportunity to gather more data, perhaps with other conditions attached.
**A practical application of the weight of evidence method is cryptanalysis. It was first developed into a practical methodology in WWII by famed mathematician Alan Turing working at storied Bletchley Park. Something of it is explained in the book "Alan Turing: The Enigma"


Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog

Saturday, April 2, 2016

Release by sprint or capability?


One of the Agile paradigm shifts from the "way we've always done it" is to shift release planning to either fixed calendar points -- at the end of one or more sprints, but typically three or more -- or when capability needed by the business is "done"

In an interesting posting, here, the first idea is given the moniker "cadence release"; the latter "capabilities release". The recommendation of one over the other is: Yes!

That is, each has it's place, and it's therefore a matter of context that informs judgment:
  • Domain culture  -- what are the project norms?
  • Importance, urgency, applicability in the near term
  • Expectations of the sponsor (how did you set the value proposition?)
  • Expectations of the user (what's hot, what's not?)
  • Maturity of the product, capability, or update -- before it's time, as it were?
  • Contract parameters if there's a 2nd party contract involved -- some flexibilities re release may be proscribed by the contract


What more on agile? Available now! The second edition .........

Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog