CIOs spend much of their time identifying the right strategies for IT implementations, which invariably morph into projects and programmes, writes Raed Haddad.
A company's ability to implement or execute these efforts, which are often large and quite visible, is what distinguishes success from failure. CIOs too frequently get off track while attempting to keep their fingers on the pulse of these mission-critical projects.
- Failure to connect the dots for project managers. Many CIOs do not communicate the connection of IT projects to the overall business strategy. Furthermore, they forget to articulate the value of an IT project on the company vision.
Tip: Answer the questions: why are we undertaking this initiative? What are the expected changes?
- Improper change management strategies. IT executives need to recognise that projects are change initiatives. It is not about redesigning the screens in a call centre, for instance, but rather the change in individuals' daily work habits that will impact the success or failure of a new initiative. IT managers need to understand why something new has been created, especially if the 'old way' worked fine.
Tip: Get your project managers excited about change by explaining the greater context and recognise that change takes a bit of time.
- Lack of time for planning, but insistence on a comprehensive plan. IT executives often demand a time schedule or a budget that is based on project-irrelevant data points. This is the cat-and-mouse game that project leaders and IT executives play - doubling the number because you know "they" will cut any number you give by 30%.
Tip: Allow planning time and create realistic expectations for your manager... and for yourself!
- Demanding "one number" for time and cost. The savvy IT executive demands a "range" approach for time and cost. A well-planned project allows for the best and worst case scenarios from a realistic viewpoint. Your plan should reflect the top 10 risks and the associated additional cost for each potential risk. In short, risk management is key for decision-making.
Tip: Ask for an estimate that considers the risks first.
- Selective memory. While many CIOs have a risk assessment plan, they are often surprised when they have to pay additional costs.
Tip: Follow through on your commitments. If a project leader presents his or her top risk that has a price tag of an addition $1m, and it occurs, fund it.
- Trying to stay on top of everything. IT executives have moved up the ranks for a reason. They have technological know-how. But a CIO needs other skills, too. He or she needs to know how to delegate and ask the right questions of the right project and programme managers.
Tip: Cultivate your PM talent so you can tap into their knowledge pool as needed.
- Hope is not a strategy. Project managers tend to assume the best case scenario over reality. Ask the next 10 project managers you run into about their projects. You will find that, aside from some issues here or there, "the team will pull together and get it done".
Tip: Demand regular updates and an actionable status report that identifies issues and challenges as early as possible.
Raed Haddad is senior vice-president, global delivery services, ESI International. He has more than 25 years of multi-cultural, project management expertise across a range of industries, including health care, technology, government, telecoms and financial services. A member of ESI's executive management team, Raed is also responsible for many of ESI's global operations. He also is a professorial lecturer at the George Washington University School of Engineering Management and Systems Engineering in Washington.
Sign-up to Computer Weekly to download research reports from ESI on project management, training and agile programming.