We use our own and third-party cookies to offer our services and collect statistical data. Continuing browsing implies your acceptance. More information
I work on a project for a customer who continuously changes the specifications. We must adapt our way of working to this particularity. For this reason, we use an Agile methodology, such as Scrum, for the firmware development of the product.
Subsequently, and from my point of view as developer of the Development Team, I list the advantages of the Scrum methodology and I will tell you how we follow the Scrum phases every day.
In our project, the Scrum Team consists of the following members:
The development time is set up in 3 weeks (the recommendation of the Scrum reference guide approximately), divided into 2 weeks for the development of the new functionality and 1 week dedicated to applying intensive integration tests and fixing bugs found which are occasionally detected. During the development phase, various static analysis of the source code are performed, using the Klockwork analyser and different dynamic analysis of the source code are performed using the Valgring tool.
When a sprint is launched, we hold a 3-hour Sprint Planning meeting to plan the tasks to be performed during the sprint, observing the priority and duration (in hours) of the tasks. we use the Redmine tool for the Sprint Planning. The Development Team is responsible for updating the task status to ‘Done’ each time a task is completed.
The Development Team holds a short daily meeting of 15 minutes designated as the Daily Scrum. During that meeting, each developer summarizes the work performed during the previous day, he plans his work for the current day and, if necessary, he requests support from another developer. These meetings are coached by the Scrum master.
When the sprint is concluded, we hold a Sprint Review meeting of 2 hours during which the Development Team demonstrates the ‘sprint increment’ to the Product Owner, as well as to the members of the Test department.
Finally, we hold a 2-hour Sprint Retrospective meeting, during which the Scrum Team reflects on the errors occurred during the sprint and develops new concepts to improve the next sprints.
An agile methodology such as Scrum can only be applied when the product can be developed iteratively and incrementally. Unfortunately, this is not the case with every product.
Written by Ángel Gutiérrez