What are the core IT project processes?
Probably everyone at some point in their career has been the witness of an IT project that didn’t deliver all that was promised.
According to a 2019 survey by the global consultancy firm McKinsey, only 14% of corporates have managed to achieve and sustain the desired performance improvement through their digital transformation projects. And only 3% report a complete success!
While following a proven IT project management methodology is certainly not a guarantee for success as the McKinsey survey clearly demonstrates; not following the basic IT project management processes on the other hand is a good recipe for failure.
This article covers the core IT project processes and techniques for robust IT project management.
The key IT project processes are:
- Phase management
- Control (change, risk & issues and progress)
- Team management and leadership
- Procurement and supplier management
- Integration with other projects and systems
Reading time: 8 minutes
Process #1 - phase management
- They provide a set list of activities the project must go through before it can move onto the next phase.
- The set activities provide structure and clarity. This means everyone involved knows what to expect and understands what needs to be done and why decisions are made. If you have adopted an agile methodology, the importance of phases still apply as structure and clarity is just as important with Agile, if not more, when deliverables are separated into bite-sized chunks.
- Moving from one phase to another when complete ensures that the deliverables have met their purpose and milestones have been achieved.
- Phases help to prepare the Project Manager and Project Team for the next phase as they understand the activities that next take place.
Whether your project is small and simple or large and complex, the lifecycle provides the basic foundation of the actions that have to be performed. The number of phases and activities within them may differ depending on your organisation, project manager, type of project or methodology employed. But they must be defined and must be followed throughout the project. A clear project lifecycle facilitates communication and change management.Issues will quickly arise if stakeholders and team members cannot see a clear structure to the project. This will cause a headache for the Project Manager and confusion for everyone else.
Process #2 - planning
In the Project Management world, planning is arguably the most important component. Planning can seem like an excessive amount of time to spend before the project has even really begun, but if you plan well in the beginning, you will reap the rewards later down the line.
A project plan allows the Project Manager to design all aspects of the project:
- Phases of a project (as mentioned above)
- Activities or tasks in each phase
- Task start and end dates
- Interdependencies between tasks
- Resources i.e. who is needed to do which tasks
Following a robust plan throughout the project not only helps to define the activities and deliverables that have been achieved so far, but also acts as a baseline to regularly refer to. If the project veers significantly from the estimated plan, it’s a sign that something is wrong and adjustments need to be made.
Frequently revisiting the plan and making these adjustments can maximise the Project Manager’s effectiveness and allows them to consistently set and meet expectations.
Project plans can vary in style, and so can the tools used to create them, ranging from MS Excel and MS Project to purpose built Project Management software. Whichever tool you decide to use, make it central to the management of the team’s tasks and make sure everyone uses it to manage their time.
A successful project is one that satisfies the objectives, on time and on budget. The plan is a key tool to making that happen.
Process #3 - control
The project has been scoped, planned and the project team is in place ready to go; but how can the Project Sponsor or even the Project Manager be confident the project will run according to plan?
A Project Manager must have the tools and techniques in place to successfully control all aspects of the project throughout. It’s important to understand the difference between controlling and micromanaging, however. Project controls aren’t about directly controlling the work or the people who do it. It’s about maintaining control over the risks, structure and flow of the project itself.
The key is to monitor closely enough and often enough to spot problems before they get out of control. Tools and techniques to achieve control:
Changes are inevitable. Whether it’s changes to what users need or changes to the original scope of the project, you need a way to manage them or the budget and timeline will quickly get out of control.
How this is done is closely linked to the chosen methodology but at a high level, changes need to be tracked, prioritised, and adjustments made to the plan.
All changes will have an effect on the time, budget and/or functionality so must be approved by the person or group with the right authority.
Hold daily/weekly meetings for the team to discuss their progress, issues, risks and reconcile with the project plan. Perhaps more importantly, don’t let discrepancies unaddressed.
Risks and issues are also inevitable. It isn’t possible to plan for every eventuality. Therefore risk management and issue management when a risk turns into a problem are a key part of controlling a project.
How risks & issues are tracked and managed exactly is dependent on the chosen methodology. But regardless of the chosen approach, the most important aspect of risk and issues management is updating and following through with the relevant stakeholders, and making sure difficult topics are not buried or sidetracked.
Again how progress is reported is closely linked to the chosen methodology, the size of the project and the complexity of the overall programme (see the section on integration below). Maintaining a weekly status report to offer high-level information about the project status is common practice. The report should answer the questions everyone seems to be asking (before they actually ask them). In some project management software, the weekly status report is “live” and gives real-time information, so there’s no need for the project manager to actually produce the report. If there is something urgent to report, act immediately rather than waiting to submit the weekly report.
Process #4 - communication
A Project Manager can be incredibly organised, produce a first-rate plan, understand the deliverables etc, but if they are unable to communicate well, the project will fail anyway. A successful project manager must be a great communicator! It’s a skill that is pivotal in being able to initiate and mobilise a project effectively.
It’s important to communicate the right information to the right people, and the methods used to do this are equally as important. Remember that communication is a two-way thing. Discuss these communication methods with the team and other stakeholders to ensure everyone agrees on the best way to communicate throughout the project:
Some project management software have communication features which can help. It’s worth reviewing what you’re using now and investigating what’s on the market if communication is one of your issues.
Process #5 - team management and leadership
A Project Manager needs a strong team around them, so it’s crucial to lead and manage that team well to bring the best out in them, and the project.
Process #6 - procurement and supplier management
Most projects will require collaboration with a source outside of the organisation. Whether this is a third party providing hardware or software, a one-off service or regularly, it’s important to define how the relationship will work. This usually involves, planning, selecting, contract writing, and monitoring.
Process #7 - integration
Many projects do not operate in isolation – they often have links to other projects or affect other departments, which means more stakeholders and more processes to account for.
This is especially common in IT projects. New and replacement systems or processes that are put into place will need to integrate with existing systems i.e. a new HR system is being implemented into an organisation that already has an independent payroll system, therefore those systems will need to be integrated to ensure processes function properly.
The Project Manager must be aware of any integrations from the start. Running ahead with the project without properly scoping the integration requirements at the beginning will land the project in hot water.
It’s not easy to integrate processes or subsystems once the design and build is already underway. When dealing with bought software, it’s a good idea to ask some “pointed questions” to the 3rd party about how their product can integrate – give specific examples of the types of processes that will need to be linked to gauge whether the product(s) can satisfy the needs.