Agile

Agile methodologies are great to use in dynamic environments where there is potential
for changing requirements, such as software and game development.
An agile project management process requires project teams to go through a process of
planning, executing, and evaluating as they go.

Scrum
The goal of Scrum is to improve communication, teamwork, and speed of development. If
you hear people talk about iterations, meetings, backlogs, and charts, they're probably
talking about Scrum, or one of its derivatives.
Scrum is about empowering a self-managed team to fulfill and define roles and
responsibilities to create a healthy tension between delivering the right thing, in the right
way, as quickly as possible.

Kanban
Kanban is light on process, it's flexible, it has no prescribed roles, and it simply tries to
improve performance by increasing the team's focus on the really important things. The
core practices are visualizing workflow, limiting work in progress, measuring lead time,
making process policies explicit, and continually evaluating opportunities for
improvement.
Kanban's focus is on work being released continuously, faster and with better quality. It is
ideal for operational or maintenance environments where priorities may change
frequently. Kanban focuses on measuring lead time: how long it takes, after being
informed, to deliver.
With Kanban, project managers often use sticky notes on a 'Kanban board' or in an online
tool like Trello via a Gantt chart, to represent the team's workflow, with categories as
simple as “To Do's”.“In process” and “Done”.

Lean
Lean is about doing more with less. It starts by identifying value and then maximizes it
through continual improvement by optimizing the value stream and eliminating waste.
Lean focuses on changing the way we operate to focus on delivering value. It is about
shifting the focus from optimizing separate technologies, assets, and vertical departments
to optimizing flow projects through complete value streams flowing horizontally across
technologies, assets, and departments to customers.
Waterfall
is a project management methodology with a very simple approach that values strong
planning, doing things once and doing them well, rather than the agile approach of
incremental and iterative delivery. It's easy to understand, because you just make a good
plan and execute it.

Waterfall is generally viewed with some disdain within agencies as a traditional, inefficient
and outdated project management approach. But Waterfall can be a useful and
predictable approach depending on the nature of the project: if the requirements are
fixed, well documented and clear, the technology is understood and mature, the project is
short and no additional value is gained by “ be nimble." A waterfall approach can actually
provide a more predictable bottom line for budget, schedule, and scope.

Six Sigma
Six Sigma is a quality management model that is also known as DMAIC, an acronym for the
words in English: define, measure, analyze, improve and control. In Spanish: define,
measure, analyze, improve and control. These are the five phases that must be applied in
each process.

 Define: the process or processes are defined, which will be evaluated by the
company's management. The work team that will carry out the project is also
defined. Finally, the improvement objectives are defined.
 Measure: it is important to understand the current state of the problem or defect
that the process being improved is going through. Each part of the process is
classified and evaluated, identifying the variables related to it and proceeding to
measure them.
 Analyze: the measurement results are analyzed and interpreted, contrasting the
current situation with the history of the process. This is where we can find out the
causes of the problem.
 Improve: the actions considered necessary to improve the process are carried out.
 Control: the necessary measures are applied to guarantee the efficiency and
continuity of the process, which will be adapted to the new objectives.
PMI/PMBOK
The project management methodology of the PMI (Project Management Institute) is not
really a methodology, but a set of standards that refer to the five steps to carry out a
project, which describe its Project Management Body of Knowledge (PMBOK). These are
start, plan, execute, control, and close.

This is not so much a project methodology as it is a framework of standards, conventions,

processes, best practices, terminologies, and guidelines that are accepted as standards
within the project management industry. It contains many project management processes
and techniques to evaluate or complete the way you execute your projects or the
methodology you use.