Application of the Scrum methodology in different scenarios
Have you ever thought that the Scrum method is not unique and exclusive to projects? Although it is a commonly used practice for projects, it is possible to apply Scrum in other contexts, such as day-to-day tasks.Neste artigo vamos trazer o Scrum sendo aplicado em algo que muitos amam: restaurantes!
Let’s call our study an agile restaurant, where the customer assembles his dish according to the ingredients available on the menu.
For lovers of changes in dishes, it will be possible to make this type of order in the agile restaurant; after all, Scrum is experimentation. This will be an introductory and different article.
The roles in Scrum
To understand how it is possible to apply the Scrum method in a restaurant, let’s start with the roles.
The Product Owner, or PO, is responsible for interfacing with the business area, understanding their needs, and prioritizing what will be delivered in each sprint according to the company’s metrics.
It sounds simple, but the PO must convey the information he receives from the business to the development team. The PO would be like the waiter in the restaurant, taking the customer’s order.
It’s also the waiter/PO’s job to explain to his customer the features of that order that may not be clear, whether it’s the sauce’s spiciness or the absence of a test environment that can extend the project’s duration.
Let’s say that the customer chooses to exchange the potatoes on his plate for mashed potatoes. If the PO does not communicate the information clearly to the Chef and Cooks, the customer will receive his plate with potatoes! This will generate rework and discomfort, and it is the role of the PO to understand and explain clearly.
Another important member is the Scrum Master or SM. He is responsible for carrying out the ceremonies defined by the methodology, monitoring the projects, supporting the team in their needs, and being a facilitator.
In the restaurant, he is symbolized by the Chef, who he and the cooks must deliver the customers’ dishes from a table simultaneously.
The development team is responsible for delivering the functionality, just as the cooks will be responsible for the dish. Together with the SM, they measure what is possible to deliver in each sprint.
Well, cooks need to understand the menu items very well so that when the dish is ordered, it is assembled as requested by the customer: shape, quantity, temperature, menu changes. Everything must be well analyzed and understood so that the “delivery” meets what was asked in the initial order, including all changes in a smooth way.
The scrum ceremonies
Through the Scrum ceremonies, we were able to see and understand what each person is doing, the difficulties and continuous improvements in the process, all the information, and their respective deliverables.
How would the ceremonies apply to the restaurant? Keep reading, and you will understand and see their importance, both in Scrum methodology and in everyday life in the restaurant.
What is Sprint?
Let’s start with the Sprint. The Sprint is one of the ceremonies that commonly have a time box where each functionality is delivered to the business area.
Consider the sprint as the time the customer will wait to receive their main dish; the PO defines the prioritization of the order of deliveries. If the waiter has booked a table before yours, it’s no secret you’ll receive your plate after they deliver the previous sprint.
Sprint Planning in Scrum
How do we know what will be delivered in the Sprint? At this point, Sprint Planning comes in, which is where the PO writes down the features (dishes) requested by the business area (client).
A meeting explains what was requested, and the development team and the SM say what is possible or not to deliver in that Sprint.
Understanding how this applies to the restaurant, it is impossible to deliver a dish that requests the beans to be white and rice to be black within a Sprint if the items are not already on the menu.
Another example is the Sprint delivery order were, applied to the restaurant situation; the waiter can bring the juice first, then the starter, followed by the main course, and, finally, the dessert. But depending on the performance of the team/cooks, he manages to bring it all together.
Daily in Scrum
One of the most traditional ceremonies is the daily meeting, where the development team and the SM report what was done, what will be delivered on the day, and the impediments or problems encountered to complete the delivery.
Think that, inside the restaurant kitchen, a “daily” happens. The SM/chef is always asking about the status of deliveries to be able to report to the PO/waiter, and the development team/cooks are always informing the progress of everything; if they encounter any difficulties, they are addressed.
Sprint Review in Scrum
Continuing with this brief description of the Scrum methodology ceremonies, we have the Sprint Review, where everyone gets together to talk about what was delivered during the Sprint and, if necessary, adapt the product to be delivered.
This happens with each table delivered in the restaurant, indicating that the delivery has been completed and reporting the success or any problem found.
It can also occur at the end of the meal when customers provide their praise or criticism, suggestions, or final considerations before paying, ordering dessert, or simply leaving. After these opinions, what needs adaptation or improvement for the next Sprint/meal is analyzed.
Retrospective in Scrum
And finally, the retrospective! The retrospective in Scrum would be like the end of the day, in which everyone gets together to talk about what was done, what they should continue doing or stop doing, and suggest improvements for the next project or the next restaurant day.
Very similar to meetings with chefs, waiters, and cooks at the beginning and end of the workday.
Refinement in Scrum
Then you ask me, but what about refinement? In the Scrum methodology, we have the refinement of what will be delivered to estimate each Sprint.
The restaurant’s menu is the ceremony of refinement, where all the dishes are broken into small parts to understand better those involved. Thus, the PO knows precisely what will be delivered to the business area, the developers know what to do, and the SM knows what he has to coordinate.
Continuing with the restaurant example, the result of some Reviews/Retrospectives can change the menu, just as the refinement ceremony can change the team’s modus operandi.
Now that we have exemplified how the Scrum methodology works in outside IT scenarios, we understand that it does not apply only to projects but also to other day-to-day situations.
So why don’t you try applying this to your business or your home? Remembering that methodologies are not dictatorial, you can use their best practices.
Next time you go to a restaurant, a cafe, a store, or a bar, remember this article and think about how the Scrum methodology works in the context found.
Fontes das imagens:
Fontes dos gifs: