Musings on personal and enterprise technology (of potential interest to professional technoids and others)

Showing posts with label ppm. Show all posts
Showing posts with label ppm. Show all posts

Wednesday, July 22, 2009

Gartner's 6/09 Magic Quadrant for IT Project & Portfolio Management

Source: Gartner (June 2009) .

Gartner have recently updated their "Magic Quadrant for IT Project and Portfolio Management".


As Gartner explains, "Project and portfolio management (PPM) applications can provide visibility into the current state of organizational initiatives, resources, and spending through the centralized collection of data from multiple sources and perspectives. Integration across multiple business and IT process domains through PPM system functions provides multidimensional views of this data for better visibility and understanding of resource supply versus project (and other work) demand in IT and other project environments.."

There seems to be some healthy competition among a group of strong leaders, visionaries, and challengers (including SAP, Innotas, and BMC), as detailed in this Gartner report. A related May, 2009 Gartner report (which unlike the aforementioned Magic Quadrant is not available to browse online for free) at http://www.gartner.com/DisplayDocument?ref=g_search&id=986223 , entitled "Market Share: Project and Portfolio Management Software, Worldwide, 2008", summarizes as follows: "After a banner year in 2007 with 24% growth, the worldwide project and portfolio management software market growth slowed to 7.4% in 2008 for a total of $1.2 billion. Among PPM vendors, Primavera, Microsoft, CA, Oracle and Agresso hold the largest market share."

As per my recent post regarding the US Federal CIO office, it is nice to see that PPM and related tools can be used in the real world with significant impact - e.g. to decide which projects should be permitted to proceed, vs. which should be halted in case they are significantly overrunning costs without yielding expected business benefits.

However, it is probably worth noting that even the best PPM tools do not add any meaningful value, unless the key business stakeholders contribute to its success by keeping relevant information and metrics up to date. Which is just another way of saying that even though the expected value / ROI may be large for a PPM undertaking, one should consider the full investment / TCO required: Not just the hard costs for licensing the software and related deployment requirements, but the full organizational commitment, training, and change required to make effective use of the PPM system and methodology.

Friday, July 17, 2009

Project Portfolio Management in action: US temporarily halts 45 IT projects (budgeted @$200 million)

As per Demian Entrekin's excellent blog on http://it.toolbox.com/blogs/ppmtoday , the US National CIO Vivek Kundra has embarked on an impressive and BIG IT project portfolio management and reporting initiative ( accessible via http://www.usaspending.gov/ ).

Today (Friday July 17th), a formal announcement on the related blog http://it.usaspending.gov/?q=content/blog confirms that 45 major federal IT projects are actually being temporarily halted. So the major USA federal PPM initiative is not merely a reporting tool, it is actually being used for taking meaningful and consistent action when project overruns are detected:

"Friday, July 17, 2009

Evidence-based decisionsVivek Kundra, Federal CIO

Today, the Department of Veterans Affairs (VA), under the leadership of Secretary Shinseki and VA CIO Roger Baker, announced that it will temporarily halt 45 IT projects which are either behind schedule or over budget and work to determine whether these programs should be continued. We’re not talking about a trivial sum here—the Fiscal Year 2009 combined budget for the 45 projects is approximately $200 million. The worst offender of the bunch was 110% over budget and 17 months behind schedule.

We were able to catch these contracts, in part, thanks to our new tool, the "IT Dashboard” which helped shed light on the performance of projects across the federal government.

During the next few weeks, the VA will audit these 45 projects to determine whether additional resources or new management teams can get them back on schedule.

If they can’t be fixed, the projects will be canceled.If you are just hearing about the IT Dashboard for the first time, it allows you to see which IT projects are working and on-schedule (and which are not), offer alternative approaches, and provide direct feedback to the chief information officers at federal agencies.

Given the size and complexity of the federal IT portfolio, the challenges we face are substantial and persistent. The dashboard is not a substitute for good management. Its value comes from leaders who use the information to make tough, evidence-based decisions on the future of IT investments.

The VA’s announcement is part of a broader effort by the Administration to make the federal government more transparent and to boost accountability and drive better performance. From IT accountability to personnel and contracting reforms, the administration is committed to providing better value, efficiency, and effectiveness for taxpayers’ dollars."

Hat tip: http://twitter.com/nytimesbits/statuses/2690095160

Tuesday, November 27, 2007

Who owns your "IT projects"? [Hint: That is a Misnomer] - The Content Economy

Nice grain of salt to keep in mind when planning the next perceived "IT-only" project, e.g. anything related to the unavoidable Upgrade Treadmill that appears not to be a Business Project:

The Content Economy: Who owns your "IT projects"?: "...there are no IT projects, only business projects involving more or less IT. Every IT initiative should be owned and driven by the business. Some might object to this way of seeing things. I would expect IT people that want to keep their influence and power and business people not interested in IT to belong to this category. Upgrading the mail server software to the latest version since the current version will no longer be supported by the vendor might be used as examples of a 'pure' IT project that should be owned by the IT department. But it should not. It would only be a pure IT project if the mail server was not used in the business at all, which then would question its existence and cause it to be terminated. The main point is that someone in the business should always have the ownership of initiatives involving IT, even those needs and initiatives that have been identified and requested by the IT department (such as upgrading a mail server software due to that the current version will no longer be supported by the vendor)...."

Wednesday, August 22, 2007

Nice PPM Summary by D. Entrekin: "Operations or Alterations?"

I especially like the acknowledgment of a "grey area", this is what I have heard called "stratactical" [combo of strategy and tactics, not purely 1 or the other]:

Operations or Alterations?:

"Some organizations have begun to split their portfolio into some fundamental dualistic categories. One such breakdown might be described as Operations versus Alterations. By Operations, we mean "keep the lights on" type work. By Alterations, we mean "change the business" type work. The notion here is that a two-pronged fork can inform the leadership team about how they are spending their resources in "stay the course" work versus "change the course" work.

I'd like to spend a minute on some implications of this split. First of all, from a very simple set theory standpoint, this split assumes that all work can be covered by those two categories. Let's take an IT department for example. Does all the work that IT performs fall into those two categories? How do we break down the work that needs to get done? If we break it down into change-the-course versus continue-the-course, then the first question to ask is, Does that leave anything out?

The easy answer is that we don't allow anything to be left out. We decide in advance that everything we are doing falls into one of those two buckets, and we force work into either one or the other. This forcing action in and of itself may prove to be useful.

A quick thought experiment might help. Some requests for work are clearly requests that alter the course, such as replacing our ERP. Some are clearly operational, such as a request to add new recipients to an existing report. But some requests are a bit more gray. Let's say that there is a request for new functionality in an existing system. You might call it an enhancement. You might call it a change request. Some folks might call it a system defect. And now we are already in a gray zone.

This small dilemma brings up one of the central issues in a portfolio approach to managing a project-driven organization. How do we evaluate requests for work in terms of their value? How do we compare their value to other work requests in the queue? How do we compare their value to work that is already being worked on? And finally, how do we make the tradeoffs?

In fact, once we have created the categories of stay-the-course and change-the-course, we have already created the decision-making framework for prioritizing and tradeoffs..."

Tuesday, July 31, 2007

Gartner Magic Quadrant for IT Project and Portfolio Management, 2007 - June 2007

Update 2009/08/19: Apparently the newly redesigned http://www.itanalystreports.com/ no longer provides the link to the 6/07 Gartner update mentioned below.
However, an excellent post entitled Project Management Online for Small Teams does provide a link. That article is well worth reading in any case and highly recommended :)



31July2007: Thanks to itanalystreports.com , an update from similar Gartner Magic Quadrant last year regarding the PPM vendor space:

"Gartner Magic Quadrant for IT Project and Portfolio Management, 2007 - June 2007, 11 pages"

Wednesday, July 11, 2007

Formula for Success in New product Development

QUOTED VIA:

Project Portfolio Management Today:
Product v. Project Portfolio
Demian Entrekin (Founder & CTO, Innotas) Posted 7/10/2007

"...As an example of some of the best practices they have surfaced, they urge what they call an "idea-to-launch process" which is driven by clear, meaningful gates from stage to stage.

Their use of research quantifies how these kinds of gate-driven processes pay off. Using studies by American Productivity & Quality Center (APQC), they have extrapolated how top performing organizations follow these kinds of portfolio techniques. In the words of the authors, these organizations "make the gates work."

In a primer called "Ten ways to make better portfolio and project selection decisions," the authors lay out concrete steps that can be taken to drive greater value from their project investments. In one example, they describe an effective approach called "incremental commitment." ....

PRIMARY SOURCE:

Stage Gate Articles, Research, Knowledge and Working Papers: "Formula for Success in New Product Development
Dr. Robert G. Cooper

Many businesses use the Stage-Gate® process to conceive, develop, and launch new products. As proficient companies have implemented, modified, adapted, and improved methodology, it has morphed into a faster, leaner, and more effective tool. The next generation process, or NexGen Stage-Gate® builds in seven principles of lean, rapid, and profitable new-product development to maximize productivity in product innovation."