Friday, July 5, 2024

Activities, Results, Methdology



Back in yesteryear, I recall the first time I had a management job big enough that my team was too large for line-of-sight from my desk and location.

Momentary panic: "What are they doing? How will I know if they are doing anything? What if I get asked what are they doing? How will I answer any of these questions?"

Epiphany: What I thought were important metrics now become less important; outcomes rise to the top
  • Activity becomes not too important. Where and when they worked could be delegated locally
  • Methods are still somewhat important because Quality (in the large sense) is buried in Methods. So, can't let methods be delegated willy nilly
  • Outcomes now become the biggie: are we getting results according to expectations?
There's that word: "Expectations"
In any enterprise large enough to not have line-of-sight to everyone, there are going to be lots of 'distant' managers, executives, investors, and customers who have 'expectations'. And, they have the money! So, you don't get a free ride on making up your own expectations (if you ever did)

At the End of the Day
  • I had 800 on my team
  • 400 of them were in overseas locations
  • 400 of them were in multiple US locations
  • I had multiple offices
  • It all worked out: we made money!





Like this blog? You'll like my books also! Buy them at any online book retailer!

Monday, July 1, 2024

"Against the Gods"... a risk perspective



If you are in the project management (read: risk management) business, one of the best books that describes the philosophy and foundation for modern risk management is Peter L. Bernstein's "Against the Gods: the remarkable story of risk".

Against the Gods is historical, somewhat philosophical, and void of math!
It's a book for "thinkers"

Between the covers of this "must read" we learn this bit:
The essence of risk management lies in maximizing the areas where we have some control over the outcome while minimizing the areas where we have absolutely no control over the outcome and the linkage between effect and cause is hidden from us.

Peter Bernstein
"Against the Gods: The Remarkable Story of Risk"

Knowledge and control
Dealing with risk necessarily breaks down into that in which more knowledge will help us understand deal with risk (climate change), and that in which effects are truly random and no amount of additional knowledge is going to help (rolling dice).

Bernstein goes on to develop one of the key themes of the book which is the idea that probability theory and statistical analysis have revolutionized our ability to understand and manage risk.

Picking apart Bernstein's "essence" separates matters into control and knowledge:
  • We know about it, and can fashion controls for it
  • We know about it, and we can't do much about it, even if we understand cause and effect
  • We know about it, but we don't understand the elements of cause and effect, and so we're pretty much at a loss.
  • We don't know about it, or we don't know enough about it, and more knowledge would help.
Of course, Donald Rumsfeld, in 2002, may have put it more famously:
" ....... because as we know, there are known knowns; there are things we know we know. We also know there are known unknowns; that is to say we know there are some things we do not know. But there are also unknown unknowns—the ones we don't know we don't know."
No luck
So there is an ah-hah moment here: if all things have a cause and effect, even if they are hidden, there is no such thing as luck. (Newtonian physics to the rescue once again)

Thus, as a risk management regimen, we don't have to be concerned with managing luck! That's probably a good thing (Ooops, as luck may have it, if our project is about the subatomic level, then the randomness of quantum physics is in charge. Thus: luck?)

Indeed, our good friend Laplace, a French mathematician of some renown, said this:
Present events are connected with preceding ones by a tie based upon the evident principle that a thing cannot occur without a cause that produces it. . . .
All events, even those which on account of their insignificance do not seem to follow the great laws of nature, are a result of it just as necessarily as the revolutions of the sun.
Bernstein or Bayes' (with help from ChatGPT)

Following up on the idea of the knowledge-control linkage to risk management, Bayes' Theorem comes to mind. Bayes' is all about forming a hypothesis, testing it with real observations, and using those outcomes to refine the hypothesis, eventually arriving at a probabilistic description of the risk.

LaPlace, mentioned above, is one of the architects of the probability theory that underlay Bayes'.  Thus, one of the most interesting discussions in the book centers on Bayes' theorem, which Bernstein describes as "one of the most powerful tools of statistical analysis ever invented."

Bayes' theorem is a manner of reasoning about random and unknown effects and a mathematical formula that allows us to update our beliefs about the probability of an event occurring based on new evidence. It is a powerful tool for making predictions and decisions based on incomplete information, and it has applications in fields ranging from medicine to finance to engineering.

Bernstein's discussion of Bayes' theorem in "Against the Gods" is particularly interesting because he highlights the fact that Bayesian reasoning is often at odds with our intuition. Humans have a tendency to overestimate the likelihood of rare events and underestimate the probability of more common events. Bayes' theorem provides a framework for overcoming these biases and making more accurate predictions.

Cognitive Bias in risk management
Bernstein talks a lot about cognitive biases and their impact on decision-making under uncertainty.

According to Bernstein, cognitive biases are mental shortcuts that people use to simplify complex decisions. These shortcuts can lead to errors in judgment and decision-making. Cognitive biases can be influenced by a number of factors, including emotions, personal experience, and cultural values.

Some examples of cognitive biases that Bernstein discusses in the book include the availability bias, which is the tendency to overestimate the likelihood of events that are more easily recalled from memory; and the confirmation bias, which is the tendency to look for information that confirms our existing beliefs and to ignore information that contradicts them.

One key point Bernstein makes is that humans have a natural tendency to be overconfident in their abilities to predict and control events. This is known as the "illusion of control" bias. People often believe they have more control over events than they actually do, leading them to take on more risk than is rational.

Another common cognitive bias is the "confirmation bias," in which people seek out information that confirms their preexisting beliefs, while ignoring or dismissing information that contradicts those beliefs. This can lead to a lack of objectivity in decision-making.

Bernstein also discusses the "hindsight bias," in which people tend to believe that an event was more predictable after it has already occurred. This bias can lead to overconfidence in future predictions, as people may believe that they could have predicted the outcome of an event that has already occurred.

Overall, Bernstein suggests that understanding and being aware of cognitive biases is essential to making better decisions and managing risk effectively. By recognizing these biases, individuals can take steps to mitigate their impact on their decision-making processes.


Like this blog? You'll like my books also! Buy them at any online book retailer!

Thursday, June 27, 2024

RaaS .. It's about results


It's been around a few years, but RaaS ... Results as a Service ... is getting more play in projects. RaaS is a play on the more familiar and older SaaS, Software as a Service. So the difference is, among other things, that RaaS is end-item focused; tools and processes are in the black box; and the customer is buying a result they can use.

Wait!
Have we just relabeled the firm fixed-price (FFP) contract?
  • FFP has been around since the beginning of time it seems.
  • The customer contracts for an outcome, a result, and end-item, at a fixed price.
  • The customer does not weigh in on process, methods, and tools
  • The customer does not weigh in on staffing or schedule details. Major milestones, perhaps only one milestone at the end are all that count.
If Agile Methods are part of the FFP contract, then the customer may be in the loop for partial product evaluation and course corrections, but such has to be within the envelope of the original scope, or the dreaded change order comes out. And if that happens, there goes the "fixed price".

In any event, beware of old wine in new bottles, unless the wine is really different, along with the bottle!



Like this blog? You'll like my books also! Buy them at any online book retailer!

Tuesday, June 25, 2024

The ideal number of workers


Wow! Is this true?
The ideal number of human workers in any business is zero. The purpose of companies is to make as much money as possible with the lowest possible expenses. So AI and other types of automation are not disruptions to a human-based Capitalism—instead, they’re revealing that today’s Capitalism is not fundamentally human in the first place.  Daniel Miessler

"... in ANY business ... "? Emphasis added by me. 

I have no idea how you could do projects with such a situation. So, I'm hopeful Miessler's idea is not an end-game for the PMO.



Like this blog? You'll like my books also! Buy them at any online book retailer!

Saturday, June 22, 2024

Best-and-Final-Offer Strategices


You're in a competitive bidding situation for a new project contract.
The buyer-customer calls for BAFO submission (Best and Final Offer)
What's you game plan and BAFO strategy to be?

Game Theory
You could fall back to game theory ideas:
  • You can't cooperate with your competition, so you are adversaries
  • You and your competitor both view the situation as zero-sum; there's not a win-win compromise solution
  • Everyone has about the same tools to manipulate (Cost, Schedule, Scope)
  • You may have some intelligence regarding customer's expectation of what is a winning BAFO strategy re cost, schedule, and scope.
  • You may have some intelligence about the bidding history at BAFO of your competitors.
  • Everyone has the same timeframe-- there is only one due date for the BAFO.
  • The game is fundamentally unstable: You're seeking maximum optimization, not some sub-optimum stability point with your competitor (assuming the customer is only going to make one winning award, which is not always the case) 
Making it to BAFO in the first place
If you've made to the BAFO, then you've made the cut on minimally acceptable cost, schedule, and scope. 
If you're bidding to a government agency, you've also made the cut on past performance, financial strength, and regulatory compliance. 
If you've got subcontractors and specialty SMEs then that cast has made the cut with you.

Do's and Don'ts
  • Do read carefully the invitation to submit a BAFO. The bias of the customer may well be exposed in the wording of the invitation.
  • Don't bait and switch at BAFO key personnel, labor mix, or technical approach unless you can point to specifics from the customer's feedback to you that suggests that such cuts would be welcomed.
  • Do offer a bottom line discount to price if you're bidding fixed price, but 
  • Don't jiggle labor rates, labor mix, and labor participation unless you can point to customer comments that justify such. You should anticipate there will be change orders and you will not want rates, mix, and participation to be compromised for the future opportunity.
  • Do wiggle the schedule if there are productivity improvements you can point to down the line
  • Do rearchitect the schedule to remove constraints and improve probability of success on the critical path. Justify this with analysis you've done since the initial submission.
  • Do take advantage of any independent R&D that will feed into the project.
  • Don't do anything unilaterally that will damage your credibility in the eyes of the customer. Unsupported changes are often viewed as unworthy business practices and new risk.



Like this blog? You'll like my books also! Buy them at any online book retailer!

Wednesday, June 19, 2024

NSA on deep fake detection of video conferencing



As I previously posted, there is a growing threat that the person to whom you are video conferencing is really a deep fake. For projects, this threat arises in recruiting strangers remotely by video call, but also in other situations when the 'familiar face' is really fake. (But I know that person! How could the image I'm seeing be fake?)

Here is a report of new research by NSA and UC Berkley about a tool -- 'monitor illumination' -- that can 'fake the fakes' in a way that gives better assurance that the fake is detected.

Of course, now that this has been widely published, the counter-counter-measures are probably already on the drawing board, so to speak.



Like this blog? You'll like my books also! Buy them at any online book retailer!

Sunday, June 16, 2024

Classified projects ... claiming credit



Most of my career has been working in the black and grey world of classified projects. 
If that is your domain, heed these words:
It is the nature of classified projects that "successes are unheralded and .... failures are trumpeted"

JFK

So, if you have an idea of putting your successes on your resume, looking for your next job, gig, or career move, beware!

 



Like this blog? You'll like my books also! Buy them at any online book retailer!