F.C Barcelona
What did we do?
Faced with the need to control the different networks of the club's infrastructure, a dashboard was created that would allow a global view of the different systems and that would allow problems to be detected quickly and efficiently.
How did we do it?
We started the project with a Design Sprint and a DevOps Sprint to define the product and its architecture based on the real needs and expectations of the client. From here we started to develop the product and define the design. We were clear that the project needed two aspects, one of control and one of visualization. That is why we created a multidisciplinary team created by 3 software engineers + a UX profile + a Product Owner. The team made different integrations with Zabbix, REST API's with an AWS infrastructure and DashButtons to control the different systems. At the design level we created a frontend with VueJS that consumed the data and showed it in a clear and understandable way. From this panel not only could all aspects of the Camp Nou be controlled to make the respective checks before a match, but also other systems such as stores, suppliers or open incidents could be controlled.
Conclusion
**Instant communication** Apart from the clear advantages for the club of being able to visualize all the information unified in a single panel, the time of communication of some manual actions that previously took hours to communicate was also eliminated, thanks to the implementation of the DashButtons that communicated new states instantly. **Agile development** Thanks to the creation of a multidisciplinary team and with good planning, we were able to carry out a large-scale project in a very short time, and being able to face changes in requirements during development, offering the client a product that is adapting to their needs and expectations. **Alignment of expectations** With our philosophy of carrying out exercises such as the Design Sprint or DevOps Sprint that sometimes may seem like a waste of time, we were able to align the expectations between us and the client and it allowed us to save many hours of work by avoiding changes in requirements due to misunderstandings and, therefore, saving money for the client and making only changes that the client really needed during development.