Sprint planning
During planning sessions, we selected product backlog tasks to be completed within one sprint and prepared a sprint backlog consisting of the user stories that would be the focus of the given sprint.
01
The Client has an inhouse development team focused on building and maintaining the core of the business — developing software for the management of mobile devices. While the Client’s team was mainly involved in backend work, they engaged external partners to support them with the frontend portion of the project.
The challenges:
During planning sessions, we selected product backlog tasks to be completed within one sprint and prepared a sprint backlog consisting of the user stories that would be the focus of the given sprint.
01
During the sprint, we worked on the items from the sprint backlog and held Daily Scrum meetings to discuss progress and obstacles on a regular basis.
02
At the end of each sprint, we held a sprint review: we summarized what has been done in the past two weeks, and presented a demo of the delivered increments to the Client.
03
During the retrospective, we reflected on the past sprint and identified the areas that went well and those that should be improved. We then listed ideas on how to improve the efficiency of work in the following sprints.
04
To make sure this cooperation goes right and doesn’t waste any more of the Client’s resources, we started off with the right preparation: getting familiarized with the documentation, meeting the team, agreeing on the rules to follow while we work together, communication standards, and methodology of product development.
We took the whole responsibility for building the frontend portion of the project, including project management. The Client’s team provided us with requirements for the project, and we took it from there, getting back to them with ready functionalities.