First Experience with Using Scrum

This article written for completing PPL 2021 Individual Review competencies

Rafif Elfazri
5 min readMay 16, 2021


In PPL 2021, we implemented Scrum framework as to help in building software that we have been assign in this semester. Although I have work in building software before, this is my first time using scrum. Before we dive any further, let us have a quick introduction with scrum framework.

Scrum Framework

Scrum is a framework utilizing an agile mindset for developing, delivering, and sustaining complex products. The set of people who work in Scrum framework called Scrum Team that consist of Scrum Master, Product Owner, and Developers.

  • Scrum Master have responsibilities to manage the development process of the project and keep good implementation of scrum principle in the Scrum team.
  • Product Owner have responsibilities for maximizing the value of the product resulting from the work of the Scrum Team and creating effective Product Backlog (list of prioritized works from the product requirements) management.
  • Developer have responsibilities for creating the project deliverables, together with the rest of the Scrum team.

Scrum iteration is Called Sprint that have three phases, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. In the second sprint, i was appointed as Scrum Master and Developers (Usually in Scrum development, there are no overlapping role, but for learning purpose overlapping role is allowed). I will explain my experience in every phases in Scrum Sprint.

Sprint Planning

In Sprint planning, we receive user stories on what should be done in this sprint from the teaching assistant in form of sets PBI (Product Backlog Item). In this sprint, we analyze the sets of PBI that we receive and we divide it to smaller task. We are using GitLab issues feature to divide the PBI into smaller task as an Issue.

Example of Gitlab Issues

The Gitlab Issues are given Milestone according to what sprint that issues belongs and giving it Epic label in according to what PBI that issues belongs. Then we assigned each issues to each member of the scrum team that want to do the task.

After we dividing the PBI, we create Branch for each PBI that we received. Each member of the team will create branches / update their own branches from the PBI branches. This PBI branches serve a purpose as the repository for the PBI works progress.

Daily Scrum

In daily scrum, we works on the issue we have received from the sprint planning. I’m tracking the works of other members of the team by seeing Gitlab pipeline, commits and merge request. In my opinion, the most important thing that I track was the merge request because the merge request is sign of a member have done a significant progress on their issue and the merge request needs minimum of two approval from other members to approve the request.

The GitLab notification on merge request with email os not effective enough for our team to receive the notification because of out team not often enough to check their email. The solution of this problem is to intergrate Discord (a chat room app) server webhook into GitLab notification.

Example of Discord WebHook integration with GitLab notification.

This integration is good solution for the merge request problem and the discord server also brings another benefits for being a place to discuss problem in the sprint and host a video call for solving the problem.

Another ways to track the progress of team member is through Daily Standup Meeting (DSM) twice a week. The meeting was lead by Scrum Master and observed by teaching assistant. In DSM, Scrum masters ask every member of the team what they have done, what they will be doing after this meeting, and blocker from their progress. In this meeting, every member also could ask any problem with their works and discuss it with other members of the team that might have the solution of the problem. The medium we used for this meeting is Google Meets, but we’ve changed it to Discord video call that has more features that Google Meets.

Sprint Review

In Sprint Review, we present our works to the stakeholder with explaining Feature that we have worked on. The Presentation is lead by Product Owner the Scrum Master works as moderators. The stakeholders could give us feedback on our works and what should be done next iteration or what should be fix or optimized in our works.

Sprint Retrospective

This is the last phase of the Sprint, The teaching assistant lead a meeting and create boards for the meeting using web application.

Every member of the team put their thoughts about the sprint through this board. There are three sections in this boards, Start (What should be done in next sprint), Stop (What thing that should be stop in next sprint), and continue (What should be continued in the next sprint). Then we will discuss of every thoughts that have put on the boards through sticky notes.


Even though this is my first experience on using Scrum framework, I like the workflow of the Scrum Framework. It give me a clear directions on how the team should works and how a project should be manage. The Scrum Framework give me new insight on team management.