Planning

Cutting Your Project Portfolio Down to Size

By |July 10th, 2014|Categories: Planning|Tags: , , , , , , |Comments Off on Cutting Your Project Portfolio Down to Size

That big project portfolio of yours is your biggest headache. It’s true. If you are like most companies, your portfolio has grown to an unwieldy size, which means you have way too many projects competing for the same resources. Here’s what to do.

First, inventory ALL projects and activities that require any kind of IT resources, making sure to include non-obvious ones like SMEs and user training time. According to Gartner, 60% of IT’s budget is spent on operational, “keep the light on” activities, so it is important that these are included to ensure correct allocation of project resources. Projects that pull resources from core operations can create business risk.

Second, decide who will comprise a governance committee, i.e., who will make decisions concerning the portfolio. This should be a mix of IT and business leaders with the authority to make decisions for the organization. The governance committee will determine which projects should continue, which should be delayed, and which should be terminated. These decisions will be made based on determining which projects have the potential to create the most value for the company. Each project in the portfolio should align with business goals and be ranked on the strength of its business case outlining benefits, costs and risk. Keep this simple, but also be on the lookout for project interdependencies. You certainly don’t want a critical project bungled because it relied on deliverables from another project that was killed or delayed.

The importance of strong governance in the portfolio process cannot be overstated. Projects that are nice but not essential drain away resources that could be used more productively. Focus on cutting unnecessary demand and don’t start new projects until you know for certain that
[ Read More ]

Mark that project APPROVED…

By |October 17th, 2011|Categories: Planning|Tags: , , , , , , , , |Comments Off on Mark that project APPROVED…

Today, every company is pursuing more projects than it can successfully handle, and that puts your project at risk of not getting the approval it needs to move forward. So, what can you do to make sure that a governance committee review doesn’t leave you and your project on the outside looking-in? Follow these steps to give your project an advantage over other projects in the queue for review.

 

Understand and communicate the business case for your project.
This starts with understanding the business strategy and business drivers that prompted your project in the first place. If you don’t understand what the business is trying to accomplish, you have very little chance of your project hitting the mark.Once the business strategy and drivers are clear, identify very specifically—and quantitatively where possible—exactly how your project will provide benefit relative to the business drivers and business strategy.

Work with key people in the business area to develop and review the business case to ensure that it is sound and strong.

Creating a solid, strong business case is the most important factor in not only getting the project approved, but also in ensuring that the project team clearly understands what is to be accomplished, why, and how it will help the business.
Identify resourcing needs by role.
Resources, especially people, are always in high demand, and you need to be very clear about the resources that your project will require (people, facilities, equipment, etc.). Clearly identify your resource needs by being specific. Assuming that your request for two technical analysts you will get you what you actually need might be a mistake. Having the right skills, expertise and individuals detailed on a project can greatly improve the probability of project success.
Identify project interdependencies.
As
[ Read More ]

October: Conscious Planning

By |October 4th, 2011|Categories: Planning|Tags: , , , , , , , , , |Comments Off on October: Conscious Planning

October is probably the most grueling month of the IT planning cycle, given the exorbitant amount of time expended in meetings. Each department—Sales, Marketing, R&D and Manufacturing—will meet with its IT counterpart to plan next year’s projects. These meetings should be dialogue-driven events that result in a shared understanding of anticipated business drivers over the next 12-18 months, current market conditions, emerging trends, and specific strategies to capitalize on opportunities. In preparation for these meetings, it would also be helpful for IT to conduct a SWOT analysis (strengths/weaknesses/opportunities/threats) comparing your company to 3 or 4 competitors. Not only will this assessment point out technical strengths and weaknesses, but it is always wise to know what the competition is up to.

Unfortunately, October is also a time of enormous pressure, as both IT and the Business push hard to achieve MBO deliverables before the end of the year. Too often, the competing time constraints of completing existing projects while planning new ones causes Business to default on the planning side, leaving IT to design new projects on its own. This lack of input from Business leads to “silo” thinking: “We know what they [the Business] really want or need.”

Now, in a perfect world, Business would remain engaged with the IT Account Manager—the one who not only has the best vantage point from which to understand and articulate Business’s needs, but is also well-equipped to offer ideas and solutions to address those needs holistically (end-to-end) rather than piecemeal. But, if Business opts out and IT can’t get it back to the table, or IT believes it actually can do the planning on its own, the next step needs to be the creation of a business case, or
[ Read More ]

September: Conscious Planning… IT Planning Season Has Begun

By |September 1st, 2011|Categories: Planning|Tags: , , |Comments Off on September: Conscious Planning… IT Planning Season Has Begun

Although strategy determines IT’s focus and direction, it’s planning that drives execution. And, despite the obvious importance of planning, very few IT organizations do it, other than to create a list of projects they hope to focus on. That’s not planning—that’s a wish list. We could argue for hours about the myriad reasons IT organizations lack a robust annual planning process, but it all comes down to needing to know how to do it, and having the discipline to do it once you know how.

In an effort to make planning less overwhelming, every month I am going to provide in this space a guide for the upcoming month. This guide will include a checklist and a set of questions that every IT leader should contemplate to be successful in 2012.

The first step to IT planning is aligning the IT calendar to the corporate calendar. If you are like most of our clients, the corporate financial calendar is based on the yearly calendar. This makes September the most critical time of the year in terms of planning for the following year’s success. Therefore, from a corporate calendar perspective (January through December), the first month in an annual planning calendar should be September.

September has begun, and, with the Labor Day holiday, we’re all probably behind schedule already. It’s time to get back to work—there is little time to be wasted. Here is where I recommend you begin:

September Theme: Alignment

To do:

Determine what 2011 projects are slipping
Ascertain what needs to happen to complete 2011 projects
Focus resources on completing those projects
Arrange for face-to-face meetings with divisional leadership. The objective is to hear and engage with each business unit regarding its objectives for 2012.
Immediately following these meetings, the IT business
[ Read More ]