Projects are different, teams have different goals and objectives, they may develop and maintain specific products. Based on these facts, different management or project management methodologies are applied in teams.
A methodology in project management is a set of rules and conditions, general principles and final procedures applied for better and more efficient management of one or more projects. It is a kind of attempt to standardise the approach to working on typical tasks.
For example, a methodology can define how the team interacts, how decisions are made, what stages the work goes through, and other processes.
Let’s list the most popular project methodologies for small and medium-sized teams.
Top 10 methodologies: the best on the market
Agile family — flexible (agile) methodologies:
- SCRUM (‘scrum’) — working with sprints
- XPM — extreme project management
- Kanban approach
Methodologies for simple and small projects:
- Waterfall — cascade model
- PMBOK — a cool framework for any project
- Critical Path Method (CPM)
Change Management Methodologies:
- ECM — event chain methodology
Process-oriented methodologies:
- Lean Six Sigma
- Process-based management
Other models
- PRINCE2 — working in controlled environment.
For a brief introduction to each of these, let’s go into a little more detail.
Agile is the most flexible methodology available
The word Agile accurately describes the approach to work on projects in the development methodology of the same name.
In fact, Agile is not an independent methodology, but a whole family of them, based on maximum flexibility and a set of special principles (they are described in the Agile Manifesto).
Below are some of the most prominent representatives of agile principles.
1. SCRUM (‘scrum’) — working with sprints
Scrum is very often used when working on software products (development and support). It is only suitable for knowledgeable and understanding customers. For example, when a customer assigns a team to implement a required feature, the team arranges a week-long «race» (sprint) and at the end creates what is needed.
Tasks are recorded on the SCRUM board, which is very similar to Kanban in its principles. However, the cards in SCRUM are a bit more informative.
With the SCRUM approach it is possible to confidently estimate the productivity of the team after several iterations (sprints) and use it when calculating new tasks.
2. XPM — extreme project management
This method is effective for project teams. It is based on the ideas of Extreme Programming (XP). The customer’s representative is always close and actively participates in the work on the project. Implementation of tasks is often carried out in pairs, where one specialist performs the task and the second controls it in parallel.
The XPM approach has a short feedback loop and processes are not interrupted by iterations. Work is tied to a standardised schedule, and task planning is based on simplicity and clarity. Testing is usually automated, which in turn speeds up project delivery and simplifies monitoring.
3. Kanban
Kanban is one of the variants of Lean Management. Tasks can have several typical statuses and are easily distributed among the executors who perform them in parallel. The manager and the whole team track the progress on a special Kanban board, where a card or sticker with a task progresses in stages, from the first to the last.
We also wrote about Kanban here.
This methodology allows you to focus on a certain pool of tasks. Cards with unnecessary tasks simply stay in the initial (first) column and wait for their turn.
4. Waterfall — cascade model
This is one of the most striking examples of how sequential methodologies work. In order to move on to the next tasks, it is imperative that the previous tasks be completed. It’s like a conveyor belt or a deterministic Turing algorithm. One moment in time — one task.
This is probably why the waterfall approach works best when producing something tangible (equipment, buildings, etc.). The main advantage of cascades lies in detailed planning. After all, a specific task should lead to a specific result. Flexibility suffers, of course, but sometimes it is simply not needed.
5. PMBOK is a cool framework for any project
The PMBOK is an example of how far you can go in planning projects. Prior to version 4, a strictly deterministic approach was used (sequential tasking and implementation); the effects of agile methodologies appeared in the framework from version 4 onwards.
In other words, PMBOK versions 1, 2 and 3 are representatives of traditional cascade (sequential) planning. At the same time, the PMBOK can be conveniently used even for very large projects in any field of application; all stages of product planning are already written in the «Body of Knowledge», you only need to adapt the PMBOK to your needs.
6. Critical Path Method (CPM)
All tasks and subtasks are taken into account and the approximate time of their fulfilment is estimated. It is necessary to take into account the links between tasks, i.e. the influence of some tasks on others. If you can not perform critical work, all this will significantly increase the deadline for the final project.
The most efficient network schedule is chosen in such a way that less time is spent on the implementation of all tasks with known resources. As a rule, the most important tasks are the critical ones. Hence the name of the method.
CPM planning is done using a Gantt chart.
CPM is not a completely linear model. Some tasks can be performed in parallel, but within the framework of work processes with reference to performers, the model still turns out to be cascading.
Change Management Methodologies:
This is a very interesting management paradigm. Everything around us is not static, it is constantly changing dynamically, moving from one state to another. What else is there to manage but states?
The cost of such a concise and comprehensive approach is high complexity and applicability mainly to large organisations or their associations.
7. ECM — event chain methodology
ECM approach is usually used in project teams when working on the most responsible tasks. The methodology involves creating a matrix of all possible events — project states depending on internal and external factors and their impact on the result of work: increase or decrease of time, additional unplanned expenses, etc.
The best way of development of events is chosen, but the probability of occurrence of unfavourable states is not excluded. It means that the ECM approach does not dwell on problems, but assumes their adequate solution when they occur. Quantitative analysis can be performed using certain methods, such as the Monte Carlo method. In addition, sensitivity analysis can be used to find the most vulnerable areas of the project and develop plans to avoid or work around likely problems.
Process-oriented methodologies:
If you have heard the term ‘business processes’, then you are already indirectly familiar with process-oriented project management methodologies.
8. Lean Six Sigma
We have already mentioned one of the «lean» models — Kanban. But the Six Sigma model has a slightly different approach. For example, it includes KPIs (Key Performance Indicators), quality management, statistical analysis and more. Business processes are continuously optimised and improved.
Sigma is the standard deviation from the norm, from the mean. Alternative names for the method are DMAIC and DMADV.
9. Process-based management
It is assumed that managers continuously optimise the business processes of the company. To do this, they define a business process, analyse it, implement changes that should contribute to positive dynamics, control the process and thus optimise it.
The cycle is then repeated. The approach is in many ways similar to the Six Sigma approach mentioned above.
Other models
When we talk about Agile and sequential methodologies, at first glance they seem to be incompatible, but no one forbids you from adopting only the best principles and approaches. Such methodologies are also called combined methodologies. In addition to these market leaders, other project management models can also be used.
10. PRINCE2 — working in controlled environment.
The approach is effectively applied to project management in the social sector and in the IT industry. It was developed and implemented as a standard by the British government.
It is somewhat similar to PMBOK, as it also assumes a division into phases and documents the individual procedures and processes well.
PRINCE2 can be perfectly combined with agile methods.
Which methodology to choose
It all depends on the goals and objectives of the project, the preferences of the team, and the customers or clients. It cannot be said that the agile approach or sequential methodologies are the clear leaders.
- For large teams that do not have problems with sharing information among themselves, cascading (linear) methodologies are fine.
- If there are problems with communication, it is better to choose Kanban or other agile approaches.
- If the team is small and projects change frequently, it is better to use SCRUM.
- If there are self-management skills in the team, extreme project management may be appropriate.
- For large and responsible projects there is the PMBOK.
This is only a small part of the specifics of choosing a methodology. To find the ideal model for you, you need to analyse your team and the basic principles of different project methods.
The environment for running the project
Whichever methodology you choose, you will need to record tasks and visualise the process of working on them. Even if this functionality is not necessary for ordinary performers, a specialised tool will definitely come in handy for managers.
We develop and implement just such a system — Projecto.
Our system runs in the cloud and does not require any additional software to be installed on workstations other than a standard browser.
Projecto is compatible with many of the methodologies mentioned above. Tasks can be presented in the form of standard lists, cards, Kanban board, network diagram (Gantt chart) or as a calendar.
You can try the system in demo mode, no registration or personal data is required.
