Project management: everything you need to know
We explain everything you need to know about project management...
Project management happens across all industries. Usually used to complete projects rather than business as usual (BAU) work, it comprises a number of stages, from developing the initial idea, to planning, implementing and analysing success of a project.
However, it is a pretty complicated process and here are lots of different ways of completing a project. Although most organisations use formal methodologies' to complete projects, some have their own way of working, which can further complicate matters.
We'll talk through the different methodologies common in the IT industry, stages and some tools to help manage projects without formal qualifications.
Types of project management
As the name would suggest, the waterfall method is a sequential project management technique, with stages that flow downwards, just like a waterfall. Stages include conception, initiation, analysis, design, construction, testing, production/implementation and maintenance, with each stage being fully completed before the next starts. It originated in manufacturing, but has since moved on to cover software development, although because it wasn't specifically designed for software development, it's not really the most effective.
Projects IN Controlled Environments (PRINCE2) is a qualification-led project management methodology, which takes a project and organises it into manageable chunks and controllable stages. It was developed by the government for IT systems projects and because it's been designed specifically for that, it's more effective than Waterfall project management techniques for software and app design. It's led by principles and processes, making it an extremely structured way of managing a project. Processes are Starting up a Project, Initiating a Project, Directing a Project, Controlling a Stage, Managing Product Delivery, Managing a Stage Boundary, Closing a Project.
Agile is a much more team-based project management methodology, with collaboration and communication forming the basis of everything. Processes and tools are replaced by individuals and interactions, working software is more important than the documentation issued alongside it and everything is built around responding to change rather than following a plan. It's a much more evolutionary way of working, making it more flexible for projects that are likely to adapt over time.
Lean is a way of developing products fast. It's very responsive to change like Agile and, as its name suggests, aims to be the most efficient way of developing as possible, eliminating waste, sharing learning with flexibility built in its core. Although it goes as far against one of the formal project management principles as it possibly can, by ruling decisions should be made as late as possible, this makes it super-adaptable, although does put some organisations off using it.
DevOps combines elements of Agile project management and lean methodologies and is increasingly the most favoured on technical, such as application development and digital transformation projects, because it's so flexible. It dictates that software and developers should work collaboratively with IT departments, through streamlined communications - the Agile element, but concentrates on getting products and services to market fast - the lean project management philosophy. It's a relatively new practice in comparison with the older methodologies, but is rapidly being adopted in cloud-forward organisations because of its flexibility and room for scale.
The process of a project
What's clear from breaking down the main project management methodologies is that they all comprise similar elements, which is the key to successfully managing a project.
Breaking it down into identifying the goal or problem (initiation), planning the steps to carry out the objective (planning stage), executing the project to meet the deliverables set in the initiation stage (while all the time monitoring and controlling the scope of the project) and finally, closing the project to ensure it's met its objectives, is crucial.
This last stage will also include handing over the project to the operations team, so it can be integrated into the BAU environment, so t can continually evolve if it needs to, making it fit for purpose. Obviously if there is a major update needed that doesn't fit into BAU, it will then need to be handed back to the project management team for the process to start again.
Best tools to help with project management
Although onboarding a project manager is the most effective way of ensuring projects get off on the right foot and are managed successfully throughout, if you're not ready to commit to a formal project management methodology to help plan and execute projects, there are lots of project management tools to help you management one-off projects.
Many of these are free and take the drag and drop approach, enabling you to assign and set tasks, moving them across columns as they progress. Others allow you to track progress to share with the board, if they're all about numbers, data visualisations and ROI.
Although project management requires investment to make it run smoothly, it's worth the outlay, speeding up the time it takes to get products and services to market, while also dramatically improving the productivity of your employees, across departments.
Unlocking collaboration: Making software work better together
How to improve collaboration and agility with the right techDownload now
Four steps to field service excellence
How to thrive in the experience economyDownload now
Six things a developer should know about Postgres
Why enterprises are choosing PostgreSQLDownload now
The path to CX excellence for B2B services
The four stages to thrive in the experience economyDownload now