This method refers to a collaborative way of working and developing projects. It was originally intended to be used by software design teams, but it has proven to be so versatile that it is now applied in many other areas of work. It is a method that guarantees high efficiency and productivity in long and complex projects.
Even though it is difficult to know how a project will end certainly, Scrum is a supportive tool that allows companies to handle projects and products from a global perspective as well as a particular view. This will vary according to the function being met in the moment.
The Scrum Framework is comprised of a series of values, principles and good practices that are the base for further construction and development. Scrum is based on three elements: roles, artifacts, and events. Each of these has a specific purpose and must be present for the success of the methodology. To fully understand this we have to explain Agile a little bit too. To put it in simple words, Scrum is the practical way of implementing Agile. Scrum, XP or DSDM are all ways of implementing Agile, and they share common values and practices
What are Sprints in Scrum?
Sprints are units of time with a specific purpose and definition. A Sprint usually lasts two weeks, although other longer options can take up to four weeks. It is an effective way of organizing work in a sequential mode. Each Sprint can be perfected in the following phase of the project, so this sequence is flexible enough to dive room to improvement.
Sprints also allow the client to see real progress that is being made while the project is still in construction. This is an important factor to obtain the highest level of client satisfaction. The client can reach the team at any time and see the progress with a burnout or burnup chart.
What are the roles within the Scrum framework?
Three main roles set the whole process going, these are:
- The product owner: this is the bridge between the team and the client, the person performing this role is in charge of checking the project goes according to the requirements the client established before.
- The Scrum Master: this person accompanies the rest of the team and helps them get to their objectives. This person is also in charge of helping the team perfecting their skills to master the task at hand.
- The Scrum team: this is the one that makes the goal come to life. Hard and collaborative work that make projects develop and reach a final product.
Daily Standups
This is a very simple communication technique that allows the team to know where exactly they are at, and where they have to go. A group meeting has to be scheduled at the beginning of each day, and it should not last more than 15 minutes. In this meeting it is necessary to establish clearly:
What did the team accomplish the previous day?
How is each member going to help the team accomplish the daily goal?
What obstacles are there stopping the team from getting to the goal?
Another vital aspect that must be explained about Scrum framework and its methodologies is the time devoted to reflection and perfection. Each sprint has some time for reviewing in two different ways the goals achieved — one from the perspective of the client and the product that he or she is receiving and the second perspective is from the teamwork.
The team presents to the client the complete requirements of the product. The client will review the product and modify or adapt whatever he or she considers. All this taking into account the changes already made; this way the product can be modified from the first sprint to please the client when the project is done finally.
The second part of revision is related to teamwork. The Scrum team has to analyze what have been the obstacles that stopped or deterred the adequate progress of the project. This way the team can work on how to solve those issues to increase productivity and performance in the following sprints or projects.
