SCRUM METHODOLOGY

Knowing the Scrum methodology's stages is as simple as understanding that every process is driven by
inputs.

Then there is the development phase, which culminates in a finished product.

Each Scrum stage serves a common goal: to meet the Project Managers' demands and needs while also
meeting the project's delivery dates.

The 5 phases of Scrum

The phases of the Scrum methodology are divided into 16 processes or tasks, which in turn are
summarized in 5 steps or implementation stages:

1. Start
2. Planning and estimating
3. Implementation
4. Review and retrospective
5. Launch

Confused?

We will gladly explain it to you:

START

The first phase oversees studying and analyzing the project, identifying the basic needs of the sprint.

In the context of agile methodologies, a sprint is a mini-project with a duration of no more than one month
that is interconnected with other mini-projects to address the general and specific objectives of the
general project.

The questions to ask in the initiation phase are:

What do I want?

How I want it?

When do I want it?

The Scrum methodology gives preference to the formation of small teams of a minimum of 3 and a
maximum of 5 people, since it facilitates the fluidity of ideas and brings creativity to the group.

Among the first steps of Scrum, we have 6 processes:

1. Create the project vision

2. Identify the Scrum Master or ScrumMaster and the stakeholders.
3. Form Scrum teams
4. Develop Epics
5. Create backlogs or lists of requirements prioritizing the product
6. Plan the launch

PLANNING AND ESTIMATING

The second phase of Scrum typically includes the following steps:

1. Create, estimate, and engage user stories.

2. Identify and estimate tasks.
3. Create the sprint backlog or iteration of tasks.

The key to good project management is to plan and estimate the sprint, which will help you set fixed goals
and meet deadlines.

Perhaps this is the most important phase of the project, because if you are the Scrum Master you will
have to delegate the corresponding tasks to each group and make estimates of delivery times, as well as
create an ordered list to classify the work according to its priority.

Therefore, it is necessary that you use a Scrum Software that facilitates the assignment of tasks and
"makes the teamwork roll."

IMPLEMENTATION

Upon reaching the third of the 5 Scrum phases, we stumbled upon the implementation of the project.

That is, the meeting room where the sprint is discussed and how to optimize the work of each Scrum
group is explored to give the project a definitive shape.
The implementation complies with the following processes:

1. Create deliverables.
2. Perform daily stand-up.
3. Refinancing of the prioritized product backlog.

In the implementation or development phase, unnecessary last-minute changes should not be made (it is
assumed that there is a planning phase to avoid this).

Still, if you need to make a move that will be key to the success of the sprint, feel free to proceed.

Of course: first discuss it with the group and stakeholders, so that there are no confusion or
misunderstandings.

REVIEW AND RETROSPECTIVE

Once everything is laid out and implemented, you will have to review the process, which is nothing more
than self-criticism or internal evaluation of the group regarding their own work.

It is important to add constructive opinions and provide viable solutions.

Among the most important steps to carry out in this phase we have:

1. Demonstrate and validate the sprint.

2. Sprint retrospective.
3. Launch

The last of the phases of the Scrum method is the launch.

With this we refer to the outcome of the project and delivery of the product, where you should fulfill 2
unique tasks that are:

1. Send deliverables.
2. Submit project retrospective.

CONCLUSIONS

The Scrum Methodology phases are especially useful during software development, but the method is
also applicable to any type of company and project where teamwork is paramount.