Following are the most frequently used project management methodologies in the project management practice.
1 – Adaptive Project Framework:
In this methodology, the project scope is a variable. Additionally, the time and the cost are constants for the project. Therefore, during the project execution, the project scope is adjusted in order to get the maximum business value from the project.
2 – Agile Software Development:
Agile software development methodology is for a projects that needs extreme agility in requirements. The key features of agile are its short-termed delivery cycles (sprints), agile requirements, dynamic team culture, less restrictive project control, and emphasis on real-time communication.
3 – Crystal Methods:
In crystal method, the project processes are given a low priority. Instead of the processes, this method focuses more on team communication, team member skills, people, and interaction. Crystal methods come under agile category.
4 – Dynamic Systems Development Model (DSDM):
This is the successor of Rapid Application Development (RAD) methodology. This is also a subset of agile software development methodology and boasts about the training and documents support this methodology has. This method emphasizes more on the active user involvement during the project life cycle.
5 – Extreme Programming (XP):
Lowering the cost of requirements changes is the main objective of extreme programming. XP emphasizes on fine scale feedback, continues process, shared understanding, and programmer welfare. In XP, there is no detailed requirements specification or software architecture built.
6 – Feature Driven Development (FDD):
This methodology is more focused on simple and well defined processes, short iterative, and feature driven delivery cycles. All the planning and execution in this project type take place based on the features.
7 – Information Technology Infrastructure Library (ITIL):
This methodology is a collection of best practices in project management. ITIL covers a broad aspect of project management which starts from the organizational management level.
8 – Joint Application Development (JAD):
Involving the client from the early stages with the project tasks is emphasized by this methodology. The project team and the client hold JAD sessions collaboratively in order to get the contribution from the client. These JAD sessions take place during the entire project lifecycle.
9 – Lean Development (LD):
Lean development focuses on developing change-tolerance software. In this method, satisfying the customer comes as the highest priority. The team is motivated to provide the highest value for the money paid by the customer.
10 – PRINCE2:
PRINCE2 takes a process based approach to project management. This methodology is based on eight high-level processes.
11 – Rapid Application Development (RAD):
This methodology focuses on developing products faster with higher quality. When it comes to gathering requirements, it uses the workshop method. Prototyping is used for getting clear requirements and re-use the software components to accelerate the development timelines.
In this method, all types of internal communications are considered informal.
12 – Rational Unified Process (RUP):
RUP tries to capture all the positive aspects of modern software development methodologies and offer them in one package. This is one of the first project management methodologies that suggested an iterative approach to software development.
13 – Scrum:
This is an agile methodology. The main goal of this methodology is to improve team productivity dramatically by removing every possible burden. Scrum projects are managed by a Scrum master.
14 – Spiral:
Spiral methodology is the extended waterfall model with prototyping. This method is used instead of using the waterfall model for large projects.
15 – Systems Development Life Cycle (SDLC):
This is a conceptual model used in software development projects. In this method, there is a possibility of combining two or more project management methodologies for the best outcome. SDLC also heavily emphasizes on the use of documentation and has strict guidelines on it.
16 – Waterfall (Traditional):
This is the legacy model for software development projects. This methodology has been in practice for decades before the new methodologies were introduced. In this model, development lifecycle has fixed phases and linear timelines. This model is not capable of addressing the challenges in the modern software development domain.