SCRUM is a complex of operations, actions, artifacts and roles on which the implementation of projects of varying scale and complexity is based. The system is flexible and allows you to make any changes directly during the development of the project without compromising the quality of the final product. Thus, it is possible to make exactly the project that the customer needs with the set of functions that are relevant and necessary for him.
SCRUM principles
Scrum is a team process in which it is important to maintain effective communication between its members, regardless of the roles and hierarchical levels. Previously, teamwork in our company was presented in the form of a waterfall development method (waterfall). We did not completely abandon this approach, but on many projects we switched to SCRUM
In order to increase the effectiveness of work on projects in our company, we have introduced the principles and tools of SCRAM, namely:
- The interaction of people and the correct interpersonal attitude determines the effectiveness of our actions and the quality of the final product;
- Tasks are performed by small teams, as they are convenient to monitor and build normal working relationships;
- We evaluate the results of the work of the whole team, not an individual performer;
- We continuously develop and improve the team as a whole and its individual members;
- Our actions are carried out in iterations (small sprints).
The artifacts we use
SCRUM is about continuous learning and adaptation to changing factors. At Asabix, the system is structured in such a way that project teams can quickly and stress-free adapt to the requirements of the tasks and changes made by the customer. To do this, we use a certain set of artifacts that allow us to achieve good results in all areas.
Product backlog
Together with the customer (or the customer itself) we present the product backlog in the form of a list of general product ideas, which are supplemented over time and become more specific and detailed. The ideas we offer cover product properties, opportunities and methods for improvement, and correction of deficiencies.
Grooming
The backlog arrangement we are doing is necessary in order to be able to add, remove or split individual backlog items for a specific product. So we can give new assessments of factors, change the sequence of elements, as well as clarify the requirements for the task at which we are working.
Jira
Using this tool, we record and evaluate the progress of project development. This allows us to determine the dynamics of efficiency and transparency of communication within the team, improve the organization of work and focus on solving tasks. Jira in our company is based on sprints and supports their interactive development and support.
Sprint management
- Sprint Planning - all team members are involved. Together we decide what and how to do to complete the planned project;
- Story points score- we determine the score for each user story in terms of complexity, time spent and risk.
- Velocity - determine the speed at which the work team completes one sprint;
- Productivity - calculated at the end of the sprint based on the number of completed items;
- Sticky Board - a board divided into three columns with sticky notes: Tasks, In Progress, Completed. Every day, as work is done, we move the sticker to the desired status. This allows us to control the volume sold;
- Presentations at the end of each sprint - the team demonstrates the work, since one of the basic principles of Scrum is that at the end of each sprint, there should be clear and working functionality;
- Retrospective - we review the sprint, identify 2-3 shortcomings, and determine themethods for their solution.
We hold a daily meeting every day. At these Scrum meetings, we discuss tasks and make decisions on how to implement them during the sprint (2 weeks). The daily meeting takes no more than 15 minutes and the main task is to find out at what stage each participant is. We discuss problems on the way to the implementation of this or that functionality.
Results of implementing SCRAM artifacts
The introduction of SCRAM at our enterprise allowed us to effectively plan our activities and determine the best ways to achieve a high-quality result, namely:
- it added predictability to us;
- Increased the speed of the team as a whole and individual members;
- Learned how to properly plan the workload;
- Each member of our team knows exactly his task and is not distracted by others;
- Reduced stress and chaos during project development;
- Improved the quality of the final product;
As a result of SCRUM implementation, teams at Asabix work more smoothly, clearly and quickly.
Articles You May Also Be Interested In
Ready to start? Let us know!
Ukraine, Zhytomyr
Vitruka Street, 9V
M-F, 9am — 7pm
Poland, Warsaw, 00-842
Łucka street 15/204
M - F, 9am - 7pm