What the Scrum Guide Say?
Agile is an iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches. Scrum is, undoubtedly, the most used of the many frameworks underpinning Agile methodology.
How much do we apply scrum in our business processes? Let’s talk about scrum events and scrum teams.
Scrum Events:
Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts. These events are specifically designed to enable the transparency required. We practice the rituals that the scrum says and revise some meetings according to our own business processes.(ex:sprint review) Between retro and planning meetings, we additionally organize grooming meetings.
Daily Scrum:
These are 15-minute meetings held at the same place at the same time every day. With the pandemic process and the introduction of the remote business form into our lives, we are doing daily activities online, via messaging and digital distribution platforms. I can say that we have seen a lot of benefits from applications such as discord and slack in this process. Each member of the team answers the questions of what I did yesterday, what I will do today, and if there are any problems that hinder my work. If there is a problem, the team members contact the person who will help with this problem at the end of the meeting.
Sprint Planning:
Sprint planning meetings are the activity that starts the Sprint, where the work to be done in that sprint is planned, as stated in the scrum guide. We are making some preparations before the planning meeting. I tried to explain them in items.
We make sprint review meetings with the stakeholder and present the outputs of the works done in the previous sprint(sprint review meeting), and we talk about the works that are requested for the next sprint.
Before the planning meeting, we hold Grooming Meetings with the team, evaluate the business requests from Stakeholders in this meeting and discuss the details. If there is a blocky situation, information or access problem that may prevent the progress of the tasks in the sprint, we complete them until the planning meeting. The Product Owner is mostly responsible for obtaining this information.
We decided on the tasks to be sprinted at the grooming meetings, now my favorite part is to determine the effort of the tasks. In the planning meeting, the SP (story points) of the items that will be sprinted are determined by the team. That is the hourly effort required to complete a task. Fibonacci numbers are usually used when giving Story Points. We vote for 1–3–5 tasks over 3 values, if an effort above 5sp is required, we need to divide that task into sub-breakdowns.
While the Story Point is awarded, the entire team participates in voting. We do this anonymously through a tool. If different points are given as a result of voting, it is asked why they gave different points and it is ensured that everyone in the team is at the same point.
Afterwards, the tasks are assigned, and it is determined who will advance which tasks within the sprint. After sprint planning Product Owner share Devops Reports with stakeholders. If Every task are okey, now we are ready to run the sprint.
Sprint Retrospective:
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. We evaluate the process in general under three headings: mad-sad-glad. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved. The Scrum Team identifies the most helpful changes to improve its effectiveness. Actions taken in the Retro Meeting are implemented as soon as possible. Before starting the next retro meeting, the action items are discussed and the situation is evaluated by the team.
Sprint Review:
The purpose of the Sprint Review is to review the outcome of the Sprint and identify future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress towards the Product Objective is discussed. We are following a process similar to the statement stated in Scrum, but since we work with independent stakeholder, we hold review meetings with each stakeholder separately.
Scrum Team:
Product Owner:
As stated in the Scrum guide, the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.
Responsible for creating and openly communicating Product Backlog items based on business requests received in sprint review meetings with Stakeholders. And it determines the order of priority of the items
Scrum Master:
The Scrum Master is responsible for the adoption of Scrum as defined in the Scrum Guide. What are the duties of the scrum master in our business processes, let’s talk about them.
Making sure the whole team attends in the morning daily
Assisting Product Owner in determining DoDs of sprint tasks
Assisting the Product Owner in transferring the tasks scored in the activity to Trello
Ensuring that all Scrum events take place and that they are positive, productive and kept within time limits.
Development Team:
As stated in the Scrum guide, they are people who aim to create a usable Increment value in each Sprint. It can be development team; developer, tester, solution designer, devops etc. In our processes, the developer team consists of the devops team and each sprint aims to complete the work requests from the stakeholders. It is responsible for determining the DoD of the product and sprint backlog and the quality completion of the sprint tasks.
I tried to tell about scrum events and scrum teams in our process. I plan to tell Scrum artifacts in our business process as second series. For everything you are curious about, you can easily contact me via social networks.
I hope you like and enjoy reading :)
