What is the agile methodology Scrum?
It is not the first time that I am going to talk about agile methodologies, I have already made an introduction to them and I have talked to you in depth about the Kanban methodology, well, today it is the turn of the most popular other, the agile methodology scrum.
What is the agile methodology scrum?
This agile methodology is based on the continuous application of good collaborative practices, as a team, thus obtaining the best result in the project. It is mainly applied in projects of long duration and with a high complexity, and its popularity is derived from the fact that it allows to approach the projects from two points, one global and the other specific, depending on the point at which it is located.
How is the working method?
The work is based on sprints or short-term deliveries, the general rule is two weeks, and in that period of time a real opinion about that work must already be obtained, to know if it is passed to the next task or there is than to do it again. The great advantage of this work model is that with each stage the work done can be perfected, in addition to the fact that it is not necessary to wait for a team to finish its task for another to start with its own, if not it will be at the end of the project When all projects, mini stages come together and the final result is observed.
The agile methodology scrum is very useful for the client to verify the progress of the project step by step. That is, you will not find a project already done, but you can correct aspects of each of the deliveries, thus avoiding remaking an entire project.
What roles or profiles can we find?
For a project to succeed following this type of work it is essential that the roles are well defined, being able to find three assets in the project:
- Product owner: ee is the mediator between the client and the team, and must ensure that the project goes according to plan..
- Scrum master: he is more involved in the field work, checking that the team reaches its goals on the set dates. It will be in charge of supporting if necessary.
- Scrum team: the base of this pyramid. They are responsible for carrying out the project.
Existing these roles so differentiated meetings are vital, without forgetting that time is a differential value. In each work session you should talk only about the task entrusted, and must have a marked beginning and end.
What are the main differences between the agile Scrum methodology and the Kanban?
These are very different work methods, and then I would like to highlight some of the main ones between the two:
In Scrum you work in stages, sprints, while in Kanban the work is continuous, with no defined cycles during development.
In Scrum the number of tasks is limited in parallel by iterations, while in Kanban it is limited by the state of the workflow,
In Scrum it is essential that the team is made up of multidisciplinary staff, while in Kanban the teams are made up of specialists. This can lead to problems, but with the correct organization, there should be no problems.
In Scrum we cannot modify sprints, while in Kanban you can drag the tasks until they are finished.
Do I have to apply this agile methodology in my project?
The agile methodology scrum is very useful when we talk about long projects, and it will help us to complete small stages. I recommend it when it comes to a homogeneous job, being very common in the ICT or software development sector.
I hope you found the article interesting, and that you compare this working method with the agile methodology Scrum, and implement in your company the one that can give you the most benefits. If you have used this, or any other, I would like to know your opinion.
See you in the next article!
