Mashup Project

IBM discusses example of enterprise mashup project by Boeing that brings data together from multiple sources to support decision making. ...

Project Business Case: Shock and Awe with Value

Enhance your business case with a compelling story and value statements in the language of your business. While the solution is important, keep the technical details to a minimum. ...

... "Decision makers don't want to hear about bits and bytes. IT managers need to talk to them in terms of achieving business value and reducing risk, said John Cash ... " ...

Via IT Business, Canada: Project Approval Process

Return on Data

Traditional financial analyses, such as ROI, NPV, are challenging for IT projects. Better information does lead to more informed decision making and ultimately to a better performing business. ...

... "By and large, these are effective in analysing the hoped-for returns from a project or capital asset and for comparing one project with another. But they have little to say about what is probably the most valuable part of an IT project, namely the data. " ...

Via Computer Weekly: Profiting From Technology

Innovation: Influence of Relationships Survey

Survey delves into influence of relationships on innovation process. ...

... "Some data suggests that the quality of the relationships with decision-makers in a given organization may influence whether ideas are advanced (e.g., funded for the first time). The purpose of this study is to investigate whether this is indeed the case. " ...

Via Univ of Penn Wharton School: Survey on Idea Advancement for Knowledge

Cancel Project: Not At Pain Point

Ten insights on dips, or inflection points, and what to do about them. Don't cancel your project when it gets tough. Use your dips wisely. Thanks Guy and Seth. ...

... "What's the worst time to quit? When the pain is the greatest. Decisions made during great pain are rarely good decisions. " ...

Via How to Change the World: The Big Dip

IT Project EQ Business Project 4 Heineken

Heineken Ireland implement CRM project successfully with business in the lead. Local IT manager grapples with common IT challenges, such as security, vendor consolidation, outsourcing, etc. ...

... "For Heineken Ireland it was the first real acceptance by the business that something like this wasn't an IT project. It was a business project with a strong piece of IT in it, says Manning, careful to make the distinction. " ...

Via SiliconRepublic: Tech Decisions Pay Off

Portfolio Management, Program Management, and Governance: A Rational Approach

There's an informative article by Michael Hanford on IBM's website about "Portfolio Management Governance." While it's aligned with IBM's Rational methodology, it provides useful information in general on the topic.

Many people confuse portfolio management, program management, and the relationship of governance to the both domains.

While there's no "right answer" per se, the generally accepted view is that portfolio management focuses on alignment with organizational strategy; setting priorities vs. resource and/or financial constraints; and insuring the right mix of initiatives to meet organizational goals. This is not unlike the management of a financial portfolio.

Program management on the other hand, deals more with execution of a group of related projects, insuring that the interrelationships are managed across them, and leveraging economies of scale (i.e. shared administration, management of benefits, etc.).

More importantly, portfolio management is ongoing and cyclical, while program management is temporary. Of course, some organizations refer to certain "channels" of work as programs, or even refer to mega-projects as programs, but the PMI Standard for Program Management considers these areas in the domain of functional/operational management or project management, respectively.

As for governance, it can work on multiple levels. There can be portfolio management governance, which makes decisions and sets policies at the portfolio level, or program management governance, which acts at the program level. Ideally the two work hand-in hand. For example, an executive council (and sub-councils if need be) can make decisions at the portfolio level (including authorization or termination of programs and projects), while a program oversight committee can govern a specific program, in alignment with the portfolio needs.

For more, here's the IBM article...

Establishing portfolio management governance: Key components

CIO Pulse Point: IT Governance in Top 10

American Institute of Certified Public Accountants rank IT governance in the top 10 most important technology initiatives for 2007. ...

... "IT Governance: A structure of relationships and processes that direct and control an organization and help it achieve its goals by adding value while balancing risk versus return over IT and its processes. Includes IT ROI, or the decisions around technology investments and how to optimize related returns. " ...

Via American Institute of Certified Public Accountants (AICPA): AICPA 2007 Top Technology Initiatives ... (PDF)

Empathy: Lessons from Iwo Jima

I just saw Clint Eastwood's magnificent film, Letters from Iwo Jima, this weekend. Of course, as usual I end up looking at everything through the lense of leadership and project management lessons, which drives my wife crazy.

The film offered numerous contrasting examples of good leadership and poor leadership. The differences weren't hard to spot. Besides strategic intuition, what separated the effective leaders from the rest of the pack (on both the Japanese and American sides) was an undeniable sense of empathy (much like the film's director, Clint Eastwood, did in making the film from the Japanese perspective).

Empathy, a key component of Daniel Goleman's Emotional Intelligence, is an undervalued trait in leadership. Equally important is the wisdom to know what to do with that empathy. In the film, the leaders who showed empathy and restraint were able to make the right decisions, even in the heat of battle. Their moral compass served them well. Ironically, it was empathy that led them to be able to predict the moves of the enemy as well.

Then there were the less effective leaders who blindly followed rules, thought only of themselves, were obsessed with power, and looked at people as objects to be used. Go see the movie. You'll see leadership styles worthy of emulation, and those to avoid. Ultimately, the film is about human decency and indecency.

Managing the Grey Areas: Lessons from the Leadership Quadrant Seminar

On November 15th and 16th, I conducted a seminar with productivity consultant Jerome Jewell called The Leadership Quadrant: 4 Ps for Organizational Excellence. The 4 Ps are Principles, People, Productivity, and Process. It was held at the National Constitution Center in Philadelphia, and we incorporated the museum’s rousing multi-media show, Freedom Rising, into the seminar.

The seminar participants came from the healthcare, criminal intelligence, and manufacturing sectors, which led to some fascinating discussion and dynamics. With any seminar, the value to all in attendance is magnified by the contributions of the participants, and this was no exception.

In the seminar, which included sections on principles, emotional intelligence, systemic thinking, talent management, innovation, project management, and more, the collective group highlighted a number of “grey areas” that a manager must frequently weigh when making decisions.

Some questions arose, such as:

"What if someone no longer likes a role they excel at and prefers a role they're poor at?"

"Do people always need to see the big picture?"

"Should one person be expected to serve the role of a manager, leader, and administrator? A strategist and tactician? A generalist?"

"How do you strike a balance between effective time management and remaining available to your staff?"

"Are recurring meetings effective or are they time wasters?"

In line with these questions, below are some of the factors that managers must consider:

• People’s individual needs vs. organizational goals
• Big picture inclusiveness vs. security (or the desire to give people narrow focus)
• Using generalists vs. specialists (and where the specialty should focus – on a functional area or on a particular skill)
• Effective time management vs. flexibility and being available to your staff’s needs
• Recurring meetings vs. consideration for people’s time
• Informing vs. influencing (for deciding whether to email or meet; even then, the decision is not always straightforward)
• Innovation vs. execution (knowing when to move from ideation to “getting things done”)
• Systemic (whole view) thinking vs. systematic thinking (routine, repeatable process)
• Vigilance vs. delegation (how much is safe to delegate, and to whom?)
• Firm principles vs. ethical dilemmas (should a firm principle ever be bypassed?)

In all of these cases, the group determined that the answer isn’t always black and white, and that each situation requires weighing these items. The trick is to observe, orient, decide and act quickly (referencing Colonel John Boyd’s OODA principle).

On the item of firm principles vs. ethical dilemmas, the group applied lessons from various cases throughout history where the US Constitution was challenged. It was obvious that there was no “one size fits all” answer.

With more recent events, consider OJ Simpson’s book. If you manage a bookstore with a principle of defending freedom of speech, do you carry O.J. Simpson’s new book, even though it is "ethically challenged," to say the least? Most large-chain bookstores creatively tried to satisfy both sides of the equation by donating all of the proceeds to the victims’ families. Of course, in the end, the book was canceled, but for a while, this was a real challenge to bookstores.

All of this reaffirms that management is abstract, not concrete. Managers cannot have all the answers; but they can and must insure that the right questions are considered, and they must have the courage to make decisions.

Project Risk Management

Oil production company, Venture Production PLC, uses risk management software to model project scenarios to select optimum schedule while balancing risks, costs, and time performance. This seems a worthwhile approach, when large investment is at stake and time to value is critical. ...

... "Using Pertmaster, Venture's project management team was able to add a risk dimension to plans built in its Primavera P3 scheduling solution. Venture then analysed the schedule-risk of multiple scenario options to look at the most probable outcomes of each, in terms of both timescales and costs. This enabled the best options to be highlighted when considered from both likelihood of risk occurrence and degree of impact and enabled management to take well-informed decisions. " ...

Pertmaster Helps Bring Venture's New Oil Field On Stream ...

Venture Operated Goosander Field On Stream: "Goosander has been developed as a sub-sea tieback to the Venture operated Kittiwake platform utilising two subsea flowline bundles totalling 12 kilometres in length. The bundles were manufactured and installed by Subsea7 from their construction site in Wick and have been designed and engineered to accommodate future production and water injection wells and the potential for re-use on future subsea tie-backs. "

The Distributed PMO: Lessons From Strange Places

I've read two pieces of information lately that couldn't be more different, and yet they both got me thinking about the benefits of what I call a "distributed PMO."

First, as I mentioned last week, I had read about Ken Kizer's magnificent transformation of the formerly abysmal Veteran's Health Administration (a poorly run group of hospitals mired in government hierarchy and bureaucracy). He established an network of regional "hubs" (what he called Virtual Integrated Services Networks, or VISNs - pronounced "visions"). Each VISN was itself a network of partnerships, associations, alliances, hospitals, etc. that worked together for the good of the customer.

The VISNs had the benefits of standardized quality with local presence. Decision-making was moved from Washington HQ to the VISNs, who were closer to the action than Washington HQ could ever be.

The role of headquarters became one of support, guiding principles, consulting advise, information services, and change leadership. Headquarters drives behaviors that benefit the overall structure.

Forms and approvals were reduced to a bare minimum. A relentless focus on the customer/patient (one of my battle cries, as most of you know) now guides all decisions and research.

If this isn't a good model for a PMO, I don't know what is. If project managers and functional experts (each who rely on one another for success) operated in various "regions" and/or functions (close to the action), and the PMO's role were to provide (and I repeat from above) support, guiding principles, consulting advise, information services, and change leadership, more PMOs would become a valued and integrated part of their organization.

And if the focus were on reducing forms and bureaucracy, helping project teams be successful, and improving the customer experience (as opposed to an internal focus on merely schedule and budget metrics), PMOs might find themselves more popular as well.

Incidentally, this also happens to mirror the Toyota organizational model.

The idea of a distributed, integrated network isn't unique to business. It even happens in nature (here's where the strange part comes in). I was reading about a giant sea creature, larger than a blue whale, called a Giant Siphonophore (Praya sp.). The creature (yes, this is true, folks) runs 130 feet long and is actually made up of many other life forms, each having its own specialized role that works to service the whole entity, yet is unable to exist on its own. In other words, the Giant Siphonophore is a "colonial life form." As I read this, I was again reminded of the concept of a virtual, yet integrated network.

Yes, I actually make these odd connections, but ideas can come from anywhere. By the way, the creature can be seen in the IMAX film, The Living Sea (available on DVD). Here's more info on the colonial nature of the Giant Siphonophore and it mutually dependent parts. Food for thought.

Off-shelf Governance Is Not Free ...

Even the implementation of open, off-shelf best practice frameworks takes time and committment. Don't let anyone fool you. Structuring an effective governance decision making process, recruiting and staffing governance bodies, and developing the portfolio information to enable governance decisions is an investment. Start now. But, realize that it's a journey. ...

... "CobiT offers no instant panacea for IT governance, and organizations can't expect to implement an effective framework overnight. " ...

Via CIO: CobiT Requires Commitment

IT Governance Meets Server Virtualization ...

Cassatt and NEC combine to deliver portfolio management for virtualization of servers aimed at the financial services industry. ...

... "Cassatt Corp., an innovator in providing enterprise software and services to enable agile IT infrastructures, and NEC Solutions (America), Inc., a premier provider of integrated solutions for the connected enterprise in North America, announced the immediate availability of a fast track IT Portfolio Management solution for server virtualization and consolidation. Express IT Portfolio Management (e-ITPM) is a joint solution from Cassatt and NEC that provides financial services customers with the ability to realize greater costs savings by combining IT governance initiatives with internal IT projects on virtualization and server consolidation. " ...

IT Governance Meets Server Virtualization: Via Cassatt Corporation: Cassatt and NEC Expand Partnership to Target Financial Services Customers: Joint solution combines NEC Solutions America IT Governance Practices with Cassatt's Server Virtualization Management and Consolidation Solution ...

IT Governance: Green Data Center ...

The information technology department can enable a green enterprise through smarter use of energy in the data center and on the desktop. Simple things, like Windows power management and double-sided printing, can make a difference. And, server virtualization ensures higher utilization rates and greater efficiency. ...

... "In today's world of high energy prices and green awareness, doing so should be a key element of IT governance at any organisation. " ...

IT Governance: Green Data Center: Via silicon.com: IT power crisis - what can CIOs do? ...

IT Strategy: Upgrades Align to Long Term ...

End-of-Life upgrades and capacity increase investments should align with the architectural roadmap generated by the IT strategic plan. Article discusses techniques to support upgrade decisions, postponement tactics, and repair/replace choices. ...

... "Any IT investment--whether it's an upgrade, a purchase or a lease--should support your long-term IT strategy. Otherwise, you're not spending your money wisely. " ...

IT Strategy: Upgrades Align to Long Term: Via Entrepreneur: Upgrading Your IT Equipment

IT Governance: Model for Accountability ...

Is the CIO accountable for the decisions in IT governance? Michael Schrage discusses techniques for creating accountability in IT governance --- make governing boards and steering committees accountable to each other and for results. ...

... "That story often comes to mind when I hear the frustrations of IT governance and IT project steering committees designed to better align budgets, schedules, requirements and priorities. " ...

IT Governance: Model for Accountability : Via CIO: The Hammer of Consensus ...

Recovering Troubled Projects; Seven Steps to Turn it Around

I just read a good case study about rescuing a troubled project, written by Jim Stewart on Chief Project Officer (which, incidentally, has a nice selection of articles).

Here are seven tips Stewart suggests:

1) Don't continue down a failed path. It's never too late to add controls.

2) Don't be afraid to cut your losses and terminate a project that's not generating value.

3) Be sure you have experienced, trained project managers. Keep the good, trainable ones. Reassign the others.

4) Be prepared to make tough decisions. Bypass groups that'll slow you down. Remove troublesome spots (or people).

5) Have adequate and appropriate resources. Allow project managers to focus on project management, not day-to-day technical details or deployment.

6) Don't hesistate to reconsider everyone's role. Avoid redundancy and joint-leadership situations.

7) Re-plan the project with team input. Avoid an unrealistic plan set by management. While management input is valid, only the team knows what's wrong with the project and how long everything should take. Getting team input insures a realistic schedule and garners team buy-in.

Here's the full case study with the lessons...

Chief Project Officer: Case Study: Recovering a Troubled High Tech Project

Project Management: Virtual Decision Making

Struggling with enabling and sustaining project decisions? Bill Thomas promotes effective decision-making through a process that considers the level of decision-making participation and measures performance. The decision roles of participants should be understood, documented, and monitored (helpful with compliance, such as SOX). Graphical visualization of key measures is recommended, in combination with the appropriate commentary to provide the color and texture of the business context. ...

... "Effective group decision making within performance management has always been a challenge, but traditional decision-making approaches do not consider the speed and complexity of dynamic virtual work teams regularly employed at this time. They also neglect recent compliance regulations that have a direct impact on defining current business processes. Ten years ago, an organization could employ loose guidelines and/or project management techniques because group decision making was less complicated. " ...

Via Business Intelligence Network: Decision Making and Risk within the Performance Management Process ...

Business Process Governance: Setting Priorities ...

The convergence of benefits realization from ERP implementations and the drive towards operational excellence have placed IT at the epicenter of business process transformation. Good governance can ensure the leadership committment and focus necessary to achieve real change. Andrew Rowsell-Jones, Gartner, extends the approach for IT governance to the enterprise decisions necessary to drive enterprise transformation. ...

... "Process governance can be defined using the same tools for defining IT governance - but extended to include decisions about process priorities. These additions include the principles used to govern decisions about processes, and benefits realization, where C-level executives and at least one other business group, plus the CIO, have to call the shots. " ...

Business Process Governance: Setting Priorities: Via CIO: Change Is the Name of the Game ...

Mining for Talent; Fielding a Good Project Team

Tom Peters has been blogging about a book by Dennis Littky called The Big Picture: Education is Everyone's Business. Now I can see why. I purchased the book and it's revolutionary. Littky is a pioneer in the education industry and has achieved startling results with his focus on students as individuals. But the book isn't just for those in education, it's for anyone in a leadership role.

Much like the theme of How Full is Your Bucket, the subject of my previous post, it focuses on finding the hidden talents in the individual, and not just basing decisions on grades, scores, or averages. I'm still reading it, so I'm sure I'll be posting more on it in the near future, but so far it's a very enlightening book, and makes so much sense it's scary.

I've always subscribed to this philosophy, as I feel that fielding a good team in business is no different than fielding a good team in sports. You need to find people's desires and areas of talent (nearly everyone has some), encourage them to build on that talent, and put them in the right positions to exercise that talent. Combined with positive reinforcement (which elevates their self-confidence), they will shine as individuals, and if well-matched with others (team dynamics), the team will shine as well.

I recently saw yet another source that supports this theme of "mining for talents." I just subscribed to Leadership Excellence magazine (and in fact have been asked to submit an article to them, which will most likely appear in their April issue). On their website, I saw this quote from leadership guru Warren Bennis...

“It became clear to me that to understand Drucker’s philosophy of management, you need to know his philosophy of education. In fact, they are one and the same: Honor individual differences. Take people as they are. Don’t attempt to change or manipulate them to be like or to become somebody else. There is no one right way. Organizations are as much learning environments as they are socially useful institutions established to produce goods. At their best, they make available sufficient roles where individual strengths can contribute to productivity and where individual weaknesses are irrelevant. There is virtually no such thing as an ineffective worker, only a worker whose areas of competence are inappropriate for a particular role.”

—Warren Bennis, consultant,
Leadership Excellence, January 2006

Very inspiring words.

Risk analysis for portfolio management

"CIOs who are serious about portfolio management need to be serious about statistical risk management". This sentence is tucked away soemwhere in the second section of this article, but it summarises the message.
An interesting insight is that many organisations can't or won't quantify project risks. Because there are no risk numbers to be compared with the one hard number that is know - the budget - the tendency is to base portfolio decisions on budget alone.
The articlae discusses a couple of methods for quantifying risk - Decision tree analysis and Monte Carlo.
And the bottom line? It's a question of leadership to ensure that risk is taken into account.
Playing with Fire - Risk Management - importance of quantifying risk; use statistical simulations to map risks and probabilities; Develop risk analysis process - CIO Magazine Jul 1,2003

SOA ServiceOriented Architecture Predicted to Increase in New Year ...

IT governance models must evolve to make the best decisions on a service oriented enterprise architecture. Sean Rhody makes some predictions for the new year, including the acceleration of service oriented architectures, SOA. ...

... "Service orientation offers the possibility of real advances in IT - advances that can be coupled strongly to business value. It also requires organizational change and modification to IT governance that many folks have yet to really tackle. It's a lot easier to change the software than it is to change the people who run the software " ...

SOA ServiceOriented Architecture Predicted to Increase in New Year: Via SysCon: Holiday Wishes ...

Project Work Packages; The Importance of Delegation

I read this story on Stephen Covey's website about his inspiring interview with a well-respected Naval captain. They key success factors for this captain were his ability to delegate, and his trust in his subordinates. This trust and delegation truly inspired passion and accountability in his people (something we've promoted here at PMThink as well).

It reminded me again of the importance of Work Packages in project management, where we assign deliverable (or group of deliverables) to a work package owner, and give them full accountability of managing the details to "make it so" (as Captain Picard of Star Trek: The Next Generation would say).

Here's Stephen Covey's account of this interview:

I was training U.S. Navy officers in leadership during the dot.com era, when someone told me about an exemplary leader named Captain David Marquet, Captain of the U.S.S. Santa Fe, who never lost anyone, in spite of the hellish conditions submarine personnel are required to endure. An opportunity arose, which I jumped at.

I was invited to board Captain Marquet’s sub and interview him. Never before had I observed such empowerment. We stood on the bridge of this multibillion-dollar nuclear submarine with a football field of vessel in front of and behind us. A young officer approached the Captain and said, "Sir, I intend to take this ship down 400 feet." Captain Marquet asked about the sonar and sounding and then instructed this young man to give us another twenty minutes on the bridge before carrying out his intention.

Throughout the day, people approached the captain intending to do this or do that. The Captain would sometimes ask a question or two, but then say, "Very well." He reserved only the top decisions for his own confirmation and empowered others to make the rest. He said he wanted to empower his people as far as he possibly could within the Navy’s confines. He felt if he required them to own the problem and the solution to it, they would begin to view themselves as a vitally important link in the chain of command. He created a culture where those sailors had a real sense of adding value.

Months after my sub ride, Captain Marquet wrote to inform me that the U.S.S. Santa Fe was awarded the Arleigh Burke Trophy for most improved submarine, ship, or aviation squadron in the Pacific.

All in all, a very inspiring reminder to us that we don't need to be managing every last detail of our projects, and instead must have faith in our most valuable asset---our team. This "distributed accountability" approach is a surefire way to encourage and exploit team synergy. Just pick the right people, give them guidelines, and get out of the way.

Results vs. Process - Revisited

The other day, I posted a blog on results vs process. The conclusion I came to was that for projects (which are by nature of limited duration), it was more important to do what it took to assure good results than to blindly follow process.

Of course, the definition of "good results" must be agreed upon. I also added the caveat that this does not apply to processes that must be observed to assure adequate results.

While I still fully believe this approach is true as a guiding principle for project managers, I've come across two good arguments in defense of process in general:

1) Results are often uncontrollable, while processes (if maintained) can at least assure more consistent results over the long haul. Uncertainty is a given, and good processes will allow for that and plan for that.

2) Conflict should always be expected, and should be used to improve processes rather than be seen as an impediment to results. Conflict is a good thing. Unresolved conflict is not.

My clarification of "results over process" is this:

• When defining processes, don't make the processes so heavy and bureaucratic that they impede results.
• Introduce processes slowly. Don't expect overnight results; Follow a maturity model and strive for continuous improvement.
• Relentlessly search for less invasive ways of accomplishing control.
• For each potential new process, use the"Five Why's" (asking "why" five times until you determine if the process in question is really needed). If in doubt, don't add it.
• Allow room for people to make decisions. If a principle will work just fine to help keep people on course, then don't institute an unnecessary process. Not everything can or should be "process-ized." Generally, aim for principles over processes wherever possible.

I do think Toyota has it right. By focusing on long-term results (i.e. continuous improvement) over short term results, continued success is more assured. By we don't want to unnecessarily impede short term results either. We can walk this balance by keeping our processes lean and giving project managers the freedom and confidence to do what is right to successfully deliver a project. People are ultimately our best asset.

VOIP Project: Voice-Over-IP ...

The VOIP transformation project is relatively high-risk: newer technology, questionable scalability, increased cultural change, and impact to a critical business function: communications. J. Nicholas Hoover discusses the pitfalls of a voice-over-IP phone project

... "Anyone thinking a switch to a voice-over-IP phone system will be smooth and easy should remember Ruth Harenchar's ruby-red nail polish. At the Hobart West Group, where Harenchar is CIO, the company's VoIP project required tough decisions, like whether to spend money training existing IT staff or hire expensive consultants. It meant learning to live without certain common telecom features in order to get the savings the company wanted. And it involved helping employees through the culture shock of replacing the familiar ... " ...

Via InformationWeek | Voice-Over-IP | VoIP Gotchas ...



Here are some relevant references on VOIP implementations:

Via NetworkWorld: The ROI of VoIP: "When it comes to VoIP, most network managers are satisfied that the technology works. The challenge is developing cost analyses: What will the new technology cost to roll out and support, and what benefits can companies expect to reap? "

Via NetIQ: VoIP in Action: "OK, you've moved beyond the deployment stage of your VoIP project. Your first group of VoIP phone users are happy and you've got high levels of availability and call quality. Now what? In the management stage, you need to keep those users happy with consistent availability and high call quality. "

Managing VoIP Implementations Effectively: "Voice over IP (VoIP) is the hottest telephony technology. Consumers and corporations are looking to reduce costs by deploying VoIP systems. The challenge, however, is that the technology is so new that few project managers have expertise in managing VoIP implementation. If you are interested in or responsible for implementing VoIP at your organization, this is the course for you. "

IT Governance Process: Drive Business Value ...

IT governance seen as hot trend for 2006. CIO's will leverage business leaders to make investment decisions and increase the business value of the IT project portfolio. Summit Strategies publishes its annual list of seven IT high-impact trends in the information technology space. ...

... "CIOs Get Business Value Religion. Leading-edge CIOs will implement sophisticated, business-focused IT governance processes and tools to increase their credibility with internal business sponsors and free up funding to support strategic business/IT initiatives. " ...

Via Tekrati Research: IT Vendors Face Fundamental Changes in 2006, Says Summit Strategies ...

Project Planning Tip: Facts are More Important Than Theories

When planning your project or solving a problem, always remember that facts are more important than theories. This means that agile approaches, rolling wave planning, prototyping, etc. should be used where appropriate, in order to base decisions on facts. The alternative is to plan all future phases in detail up front, which is tantamount to basing your decisions on pure theory.

Likewise, the project approach itself should be based on a visit to the customer to see how things are currently done, and get a true understanding of what is needed. Often, what's really needed isn't what is stated in the project request.

In A Scandal in Bohemia, Sherlock Holmes (by way of Sir Arthur Conan Doyle) said, "It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts.”

This is sage advice for project managers as well.

Project Estimating; Triple Constraint Must Stay Firm

Here's a great article from TechRepublic about project estimating and forecasting. It cautions that one of the worst things to do is to try to force a project to fit within an arbitrary management deadline. That means project managers must defend the right plan or suffer with poor results.

A properly estimated project must be based on planning, and be managed to the triple constraint of scope, time and cost (and of course, at PMThink we've discussed other potential variables, such as quality, risk, customer satisfaction, and more).

Here's TechRepublic's advice to CIO's:

Project managers talk about a project’s “triple constraints” of scope (work), time (schedule), and cost (budget)... For the team to make decisions that are closely aligned to the way you would like them to be made, you must clearly state the project priorities. There’s no such thing as “all three variables are equally important.”

Read on for more details or proper estimating and forecasting...

How to accurately estimate and forecast in project management

Project Portfolio Management: Business Intelligence Enables Visualization ...

Project Portfolio Management PPM vendors are increasingly bundling business intelligence components in their offerings, such as Business Engine's collaboration with Cognos. ...

Project Portfolio Management: Business Intelligence Enables Visualization: Via Business Engine: Business Engine Teams with Cognos to Deliver Business Intelligence Tailored to IT and Engineering Organizations: Global 2000 Companies Gain Greater Insight into Project-based Portfolios with Advanced Metrics, Dashboards and Reporting ...

... "BEN Business Intelligence embeds industry-leading business intelligence technology from Cognos, including Cognos ReportNet and Cognos PowerPlay, to provide IT and business users with powerful reporting and OLAP analysis through easy access to timely and accurate information. Business Engine recognizes the strategic importance of business intelligence and corporate performance management in helping enterprises gain greater value from their IT investments, align business goals and ultimately deliver solid results, said Ted Jandl, Area Vice President of Strategic Partners at Cognos. Coupling Cognos with Business Engine's leading Project Portfolio Management solution gives savvy corporate leaders the ability to make informed decisions about their business and technology investment portfolio while helping to drive enterprise agility in the face of a shifting economic landscape. " ...