A Deep Dive into the Scrum Agile Software Methodology
I have always been fascinated by the concept of agile software development methodologies. I studied (a lot) about agile software development last semester and have wanted to implement this in a future project. Then, I’m so grateful because I had the opportunity to implement one of the most popular agile methodologies — Scrum, in my final project at the University of Indonesia.
While several agile methodologies are in practice, Scrum is one of the most widely used frameworks. It is an iterative and incremental approach to software development that focuses on delivering value to the client in small iterations.
Get ready to take notes because this is an interesting topic. ✍️
✨ 3 Pillars of Scrum framework
Before we jump to all of this, I will introduce you to the three pillars of the scrum framework.
#1: Transparency
Transparency emphasizes the importance of making all aspects of the development process visible and transparent to the entire team. This means all team members should have access to the same information about the project, including progress, issues, and changes. One of many examples we implemented this is with documentation called PRD (Product Requirements Document) containing all the requirements for each feature.
#2: Inspection
This means that the Scrum team must frequently inspect the product, the progress made toward the goal, and the processes used to achieve this progress. In this case, we always check all the feature requirements in sprint planning, and each team gives an opinion on achieving our goal.
#3: Adaptation
The Scrum team must continuously evaluate the effectiveness of their approach and make changes as needed to ensure that they are meeting their goals. We implement this in the sprint retrospective.
Notice that I have mentioned ‘sprint planning’ or ‘sprint retrospective’? These are one of many scrum flows. In the next section, I will explain scrum flows.
✨ Scrum Flow
Scrum workflow is the series of meetings, processes, and tools that teams complete to deliver products in Scrum methodology. (www.wrike.com)
The Scrum flow is divided into several phases, each with a specific purpose and set of activities that must be completed to ensure the success of the project. Below are the key phases of the Scrum flow:
#1: Product Backlog
The first step in the Scrum flow is to identify and prioritize the project requirements or user stories in the product backlog. This is essentially a list of features or functions that need to be developed in the software. The product owner and the team create a prioritized list of requirements, features, and functionality called the product backlog. The product backlog is constantly refined, updated, and reprioritized as the project progresses.
#2: Sprint Planning
After the product backlog has been established, the Scrum team holds a sprint planning session. During this meeting, the team selects a set of requirements from the product backlog that they will develop during the next sprint.
For example, when my team planned for sprint 2, we put specific tasks about what we will work on during sprint 2 in the GitLab Issue. These activities will help my group to know a list of tasks that must be completed during the sprint.
#3: Sprint
During this phase, the team works on the tasks identified in the sprint backlog. The team holds daily stand-up meetings to review progress, identify any obstacles, and make any necessary adjustments to the plan. For this project, we held a sprint for 4 weeks.
#4: Daily Stand-up
To ensure that everyone is on the same page, the Scrum team holds a daily stand-up meeting. Each member of the team shares what they did the previous day, what they plan to do that day, and if there are any obstacles or issues that need to be addressed.
#5: Sprint Review
Once the sprint is complete, the team holds a sprint review meeting. In this phase, the team demonstrates the completed work to stakeholders and receives feedback from stakeholders. Usually, after my team receives feedback, we use to make any necessary changes or updates to the product backlog.
#6: Sprint Retrospective
This phase is a review of the previous sprint, and the team reflects on the process, the collaboration, and the results. In this phase, my team identify any successes, tell about something new, what we can be improved during the next sprint, and question if there are any.
Each phase of the Scrum flow is designed to facilitate communication, collaboration, and feedback among team members and stakeholders. This iterative approach allows the team to continuously refine the project and adjust course as necessary.
Overall, the Scrum flow is a flexible and adaptable approach to project management that is designed to enable teams to deliver high-quality results quickly and efficiently. The iterative approach, combined with regular feedback and collaboration, allows the team to adjust and refine their work as they progress toward their goals.
When implemented effectively, the Scrum framework can help teams improve communication, streamline their workflow, and deliver products that meet or exceed stakeholder expectations.
Conclusion
In conclusion, Scrum is an iterative and incremental approach to software development that focuses on delivering value to the client in small iterations. Its framework consists of three pillars: transparency, inspection, and adaptation. Scrum flow is divided into several phases, including product backlog, sprint planning, sprint, daily stand-up, sprint review, and sprint retrospective. This approach facilitates communication, collaboration, and feedback among team members and stakeholders, allowing the team to continuously refine the project and adjust course as necessary.
And that’s a wrap, Thank you! 💖
I will appreciate your feedback 💬 & clap 👏.
If you want to collaborate, don’t hesitate to contact me at deyunarusmiland@gmail.com or through Linkedin ☕
