Other Voices: In Portfolio Management, Apps Alone Won't Bring Order To Chaos
Tools deal in quantifiable information; they don't possess the human virtues of discipline, creative thinking, or, most important, decision-making.
One of the most difficult tasks for IT departments is project portfolio management--and, of course, it's also one of the tasks they most need to get right. The challenge can become particularly acute for companies that have experienced dramatic growth. CIOs can find themselves in the dizzying position of assessing the merits of dozens of projects and services, encompassing hundreds of employees.
Not unexpectedly, many business-technology executives trying to make sense of all the projects buy portfolio-management software, which can be very useful. They can aggregate project information into a portfolio-level picture, for example, and highlight where budgets or timeframes are being strained. But execs can't forget that these tools are just that. They aren't strategic thinkers or decision makers. IT departments have to lay the groundwork for a thoughtful, organized approach to their portfolio of projects before buying tools. Critical first steps include: instituting fundamental processes related to project decision-making, and paying close attention to the people involved in the projects themselves.
Take, for instance, the case of a Fortune 500 insurance company which had grown beyond its capacity to manage projects on an ad-hoc basis. Projects were increasingly running over budget and deadline, and weren't producing anticipated benefits often enough. Alarmingly, the company was becoming less discriminating in its project selection. The portfolio was no longer clearly linked to corporate and business-unit strategy. While the company had a wealth of talented people able to develop projects, it had no processes to effectively manage and sort its ever-growing portfolio.
So, the company bought off-the-shelf portfolio-management software. Nine months and hundreds of thousands of dollars later, the CIO found that budgets and deadlines were only marginally better hit, and the strategic focus of the portfolio was no more clearly defined.
Ways To Avoid Wasting Effort
How does one avoid pouring time and effort down the drain? While there's no perfect-world prescription, there are some common moves to take.
Assess a portfolio first by rationally evaluating individual projects and services in place. Subject each project to four probing factors in the following order: strategy fit, financial analysis, risk analysis, and inter-project dependencies.
Then get to know project life cycles, and institute regular evaluations at each interval of that life cycle. Typically, the intervals are: idea generation, idea analysis, business-case development, prototype development, project launch, and post-project analysis. The first two stages will provide the assumptions and hypotheses for all subsequent analyses.
In developing the business case, analyze the market and competitors, then test the initial hypotheses and assumptions. Prototype development too often is given short shrift, yet it provides essential insights and tests assumptions prior to the launch. Mistakes can be ironed out, and internal or external customer feedback can be gathered.
After the launch, analyze the efficacy of the product or service to identify the causes of any discrepancies between predicted and actual results. This feedback loop will even spotlight areas of improvement for comparable future projects.
Building A Mobile Business MindsetAmong 688 respondents, 46% have deployed mobile apps, with an additional 24% planning to in the next year. Soon all apps will look like mobile apps – and it's past time for those with no plans to get cracking.
InformationWeek Must Reads Oct. 21, 2014InformationWeek's new Must Reads is a compendium of our best recent coverage of digital strategy. Learn why you should learn to embrace DevOps, how to avoid roadblocks for digital projects, what the five steps to API management are, and more.