Archive for September, 2008

The Change Curve

Organizational changes are natural part of projects. By definition, projects are changing the state of things and almost always, this includes processes and procedures and consequently how people do things in their day-to-day business.

There are many theories an models but Kübler-Ross model applied to change management is fundamental one.

In its original form, Elisabeth Kübler-Ross wrote in her 1969 book “On Death and Dying” about the “Five Stages of Grief”:

 

  • Denial: Example – “I feel fine.”; “This can’t be happening.”‘Not to me!”
  • Anger: Example – “Why me? It’s not fair!” “NO! NO! How can you accept this!”
  • Bargaining: Example – “Just let me live to see my children graduate.”; “I’ll do anything, can’t you stretch it out? A few more years.”
  • Depression: Example – “I’m so sad, why bother with anything?”; “I’m going to die . . . What’s the point?”
  • Acceptance: Example – “It’s going to be OK.”; “I can’t fight it, I may as well prepare for it.”
Translated into change management world, these stages might be written as:
  • Denial: Example – “This isn’t relevant to my work.”
  • Resistance: Example – “I’m not having this.”
  • Exploration: Example – “Could this work for me?”
  • Hope: Example – “I can see how I make this work for me.”
  • Commitment: Example – “This works for me and my colleagues.”

This happens to all of us. It is important to understand, that this is a natural reaction and should never be taken personally. Project manager should avoid at all costs bringing this conflict to a personal level as it makes it difficult or impossible to recover from it later.

It is important that project manager keep the team involved during denial and resistance phases, especially trying to understand their current position. Translated into project management, this is the time to do requirements analysis. This can open the vents of piled up unresolved issues and problems.

Tipping point is where negotiation starts and scope crepe occurs. Project manager really needs to be tough in following the goals and objectives.

Exploration is where training can occur. People in exploration phase accepted that the change is imminent and are gaining interest in it. It is futile to do any training before this stage.

When in hope stage are empowered to accept the change. They’re comfortable doing user testing and self exploration.

During commitment phase, they’re believers. They know why this is good for them and the team. Now is the time to write new processes and procedures.


By Sašo in Uncategorized  .::. Read Comments (2)

Serenity, Courage and Wisdom

I saw a movie Changing Lanes (2002) the other day and these words kind of resonated with me:

God grant me the serenity to accept the things I cannot change,  courage to change the things I can, and wisdom to know the difference!

Think about it.



Value of Project Management

PMI has recently conducted a research (Researching the Value of Project Management) on whether what they’re doing is of any use and surprisingly found out that there is an added value in project management.

I think this conclusively proves I need a raise.



Project Prioritization Methodology

I found this interesting criteria list on PM Hut to consider when deciding about project priorities:

  • Urgency - When must this initiative be complete?
  • Alignment – How well does this initiative supports the Organization’s Goals and Objectives?
  • Productivity – How much will this initiative increase productivity?
  • Cost Savings – How much cost will this initiative save over the next 3 years?
  • Income Increases – How much with this initiative increase income?
  • Morale – What is this initiatives morale improvement potential?
  • Time To Complete – How long will it take to complete this initiative once started?
  • Competitive Position – How will this initiative improve competitive position?
  • Customer Service Levels – How will this initiative improve customer service levels?
This seems like a good set of criteria to pipe into Analytic Hierarchy Process as part of your Project Portfolio Management. It would be interesting to get a common management board agreement on weights.


Analytic Hierarchy Process in Project Portfolio Management

When running tens of projects in parallel, you’re sure to face colissions. It is usually about resources, of course. How to resolve them? Man in charge might feel what needs to be done in such cases, but it’s not easy to communicate the decision without a proper explanation as every project manager, resource manager and business manager has his or her own view. This is where decision support systems come into play and Analytic Hierarchy Process (AHP) as defined by Thomas L. Saaty in the 1970s is one them.

AHP is a typical divide and conquer solution to tackling complexity. The idea is to divide a complex decision into smaller, manageable evaluations, which are then recombined into the final metric, which helps you make a decision.

This is not a one way process. AHP might propose a different solution than you expect and it enables you to backtrack the calculation to help you understand the model by which the solution was proposed. You can then either agree with the model or correct it, to better reflect the real situation.

As written on Wikipedia, AHP provides a comprehensive and rational framework for structuring a problem, for representing and quantifying its elements, for relating those elements to overall goals, and for evaluating alternative solutions.

There’s an excellent explanation with a step-by-step example on Wikipedia. Another one can be found on Microsoft site.

An interesting article appears on Robust Decission: Why pairwise comparisons are a waste of time for finding criteria importance. David G. Ullman presents a faster approach, especially usefull with more criteria.



Time for Project Portfolio Management?

Following our constant resource issues I’ve been Googling around for best practices in this area and stumbled across Michael Greer’s article What’s Project Portfolio Management (PPM) & Why Should Project Managers Care About It?.

He proposes a self assessment check list, to see whether you’re ripe for establishing Project Portfolio Management process in your company. It goes like this:

  • Frequent difficulty finding enough people to put together a solid project team.
  • Excessive project delays due to “not enough resources”.
  • High turnover due to “burn out” of key project contributors because they are working on too many projects and spending too many overtime hours.
  • Frequent change of status of projects (i.e., moving from “active” to “on hold” to “top priority” and back).
  • Completion of projects that, when all is said and done, don’t really meet a strategic need.
  • Intense competition, rather than cooperation, among departments and sub-organizations when staffing and funding projects.

It’s all more or less true for our organization. It’s not extreme yet, but something needs to be done before we get into a gridlock.

Solution? Start with documentation, says Michael Greer:

  • Create “high resolution” project plans that accurately spell out, in vivid detail, the resources required to complete each task and activity.
  • Capture the actual hours spent by all project players in completing project tasks and activities.
  • Create summary tables showing planned and actual time spent by each person in your organization on every project to which he or she is assigned in order to demonstrate who’s overloaded.
  • Document all incidents of resources that are “stolen” across projects, excessive overtime, large-effort-but-ultimately-useless projects, and so on.
  • By conducting project “post mortem” evaluations, gather information about how systematic PPM might have prevented problems and encouraged successes.
Will do what he says and then move on.


Random Numbers Out of Triangular Distribution

As description on Brighton-Webs beautifully explains:

The Triangular Distribution is typically used as a subjective description of a population for which there is only limited sample data.  It is based on a knowledge of the minimum and maximum and an inspired guess as to what the modal value might be.  Despite being a simplistic description of a population, it is a very useful distribution for modeling processes where the relationship between variables is known, but data is scarce (possibly because of the high cost of collection).

Data about task durations is scarce and usually difficult to collect. Tasks are rarely the same as projects are by definition never the same. So why complicate with difficult distributions like Beta, when Triangular is just as good. Most of the error will come from distribution parameters and not its shape.

Probability density function of Triangular Distribution (source: Wikipedia)

Triangular distribution is completely described by minimum (a), maximum (b) and most likley (c) value (mode). Get all the formulas on Brighton-Webs or Wikipedia.

How do we get these three points? Is minimum equal to optimistic or best case? Is maximum really pessimistic enough? Is worst case really the worst? Are we really so good, that we can provide best case and worst case estimates for ALL tasks? I haven’t seen this yet.

Steve McConnell asks the reader of his book Software Estimation: Demystifying the Black Art: How Good an Estimator Are You? He presents the reader with ten quiz like questions:

  • Surface temperature of the Sun,
  • Latitude of Shanghai,
  • Area of the Asian continent,
  • The year of Alexander the Great’s birth,
  • Total value of U.S. currency in circulation in 2004,
  • Total volume of the Great Lakes,
  • Wordwide box office receipts for the movie Titanic,
  • Total length of the coastline of the Pacific Ocean,
  • Number of book titles published in the U.S. since 1776 and
  • Heaviest blue whale ever recorded.

Then he asks the reader to provide lower and upper bounds for each question, so that there is a 90% chance of including the correct value. Looking at this from other direction this means that out of these 10 questions exactly one answer will fall outside of estimated range.

According to Steve McConnell, most of quiz takers are able to guess 1 to 3 answers (average 2.8), which tells us that there’s no way we can provide 100% accurate bounds of the estimates. This is really worrying.

The good thing is that we can measure this. Just check your last project where you used 3-point estimates and count how many of them hit the bounds. If you didn’t use 3-point estimates, provide them afterwards prefferably for the project you didn’t manage, but without looking at original estimates.

So in the real world, we cannot provide usefull bounds with 100% accuracy, but if we try hard, we may be able to provide 10th and 90th percentiles, which gives us more down to earth 80% accuracy. McConnell claims that if you’re good and try hard enough, you can only go up to 70%, which then leaves you with 15th and 85th percentiles. As said in the prevous paragraph, go and measure your accuracy and use the result in estimating distribution parameteres as described below.

Glen Alleman says that best case – worst case estimates are biased by personal risk avoidance factor and is also proposing 10th and 90th percentile.

Getting triangular distribution out of mode, lower/upper percentiles requires some number crunching. Luckily, Samuel Kotz & Johan René van Dorp have done this for us in BEYOND BETA: Other Continuous Families of Distributions with Bounded Support and Applications (2004).

You can find implementation of algorithm as part of my Monte Carlo Simulation for MS Project package on SourceForge, or browse the source of TriDist.bas directly.


By Sašo in Risk Analysis  .::. Read Comments (3)


You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.