Project Management Methodology

Resources to prepare certifications in project management
Project management methodology A very simple definition of a project manager would be one who performs the project management, so it is basic to know some methodology of project management to be able to dedicate to this profession. If we rely on the PMI definition (go to the PMI page), project management would be the application of tools, knowledge, skills, and techniques to achieve project objectives, which has generated multiple project management methodologies According to different approaches. Among these we can highlight:


Methodologies with a traditional approach

The traditional project management methodologies are quite common in the industrial or construction sector, and consists of dividing the project into different processes that are executed in a sequential manner until achieving the objectives of the project or phase. These processes are:

Initialization: initial definition of the project and phase, together with the approval of its start.
Planning: development of different management plans
Execution: accomplishment of the tasks planned in the previous phase in order to complete the deliverables
Monitoring and control: monitoring of the tasks performed, comparison with planning (baselines), and definition and implementation of countermeasures in case of deviations.

Closing: completion of the phase or project, either by having obtained the approval of the set of deliverables, because it is not possible to obtain these, or because the project is no longer necessary. This formal finalization entails the release of the resources that participated in the project and the realization of the process feedback with the lessons learned. Methodologies project management – traditional approach Note that we are talking about phase or project interchange, this is due to the concept of project life cycle. This is the division of the project in phases, so that it runs sequentially, progressively approaching the final goal through the achievement of the partial objectives of each phase. There are different associations that develop, form, and certify in this methodology such as the PMI (go to the PMI page) or the IPMA (go to the IPMA page), being the most known certification the PMP

PRINCE 2 Methodology

Unlike the traditional approach, this project management methodology is based on the product, so its processes are focused on obtaining concrete results rather than planning activities. Similar to the previous methodology, it is also divided into different processes:

Start-up: description of the project, equipment, approach, and objectives of the project or phase.
Initiation: preparation and agreement of the business case of the project or phase

Planning: planning of the different aspects of the project or phase
Direction: determination of how the project will be controlled or phase, authorizations, and planning of the following phases
Control of phases or stages: as in the previous methodology the project can be divided into phases, so that the results of each of these phases must be monitored and presented.
Management of the next phases: definition of what should be done at the end of each phase and planning of the following phases. It also defines how to act and updates the plan in case of exceeding the tolerance levels of the phase.
Delivery management: agreement and definition of acceptance requirements for deliverables, including content, cost, resources, and dates.
Closure: closing activities of the project and formal assignment of this to those responsible for their last details. Includes formal evaluation.
Project management methodologies

AGILE Methodology

The project management methodologies based on AGILE are widely used in the IT sector and business organization projects, whose main virtue is the flexibility and ability to modify the product throughout the project, since these are used at the same time That are developed. This methodology is promoted by the Agile Leadership Network (Visit the Agile Leadership Network page).

This methodology is based on dividing the project into phases (sprints), the result of which is a product with a series of functionalities that already allow it to be used. These phases take place until the total of the S functionalities defined for the product. In a schematic way these phases are composed of the following: Start: the total of objectives of the product is chosen those that will be implemented in the sprint, being able to generate a functional product.

Based on these objectives, the duration of the sprint (between a week and a month), and the tasks that compose it are defined. Sprint development: the project team plans and executes the tasks, which are supervised in daily meetings where The tasks executed, current and pending, as well as possible impediments and restrictions are observed. Closing: at the end of the sprint it is checked that the tasks and objectives defined at the beginning have been completed by the presentation of a functional product. The test of this product by the client can vary the objectives of the project or its priority. The possibility of having a functional and usable product at the end of each sprint allows adjusting the objectives of the project, and therefore better ensure that the product End will meet user expectations.

In addition, the commercialization of these sprints allows to advance the income generated by the project, improving its profitability.Info free of courses in AGILEVisita our compilation of books of AGILED of these methodologies is the Extrem Manufacturing that combines Scrum with Kanban and Kaizen.Las Project management methodologies presented so far are those applied to projects within the more industrial or traditional scope (perhaps less so in the case of AGILE that is widely used in software development), but we find many other methodologies in the field of informatics Which are in continuous development.

Among them we could highlight: ITIL (Information Technology Infrastructure Library) Extrem Programing (application of the AGILE concept to programming) Rational Unified Process (RUP) Microsoft Solution Framework (MSF) In practice the project management methodology to be used will To be determined by the organization where we execute the project, although always convenient to use the one that best suits the typology of the project. We will not gain anything using AGILE in the construction of a bridge, because until it is not complete it will not be functional.

Critical Chain Methodology

It is a methodology of project management based on the theory of restrictions (TOC), designed for Maximize the progress of the project, taking into consideration that projects are subject to uncertainty and a number of limitations. This methodology is based on applying these three principles: Identification of the constraints that affect the project: this restriction is usually shown as the set of Tasks, which either due to temporal limitations or resources, define the minimum duration of the project.

This is called the critical chain, or critical path when the constraint introduced by resources is not taken into account. Give priority to tasks within the critical chain: the efforts of the project manager should focus on the execution of those tasks that form Part of the critical chain, and these will determine the completion of the project.

Subordinar the rest of tasks to the tasks in the critical chain Critical Chain Methodology applied to project management Although it is defined as a methodology different from the rest, personally the encounter is fully compatible with The traditional approach within the planning and monitoring processes. It has as great advantage to focus the direction of the project in those points that really are important, allowing to reduce and manage conflicts better, and increase the efficiency of the project manager. As a disadvantage to point out that it requires much more sophisticated planning, especially in multiproject situations, which is not always possible to apply in companies with little project management culture.

Project Management Methodology

Uso de cookies

Este sitio web utiliza cookies para que usted tenga la mejor experiencia de usuario. Si continúa navegando está dando su consentimiento para la aceptación de las mencionadas cookies y la aceptación de nuestra política de cookies, pinche el enlace para mayor información.

Aviso de cookies