Many people misunderstand that Agile and Scrum are the same. However, Scrum is one of the frameworks of Agile. Scrum is an agile framework that helps teams work together and tackle complicated issues, whilst they can ensure delivery schedule and productivity of product development with the highest possible value.
Basically, Scrum is popular because it is a simple framework that generates effective collaboration between team members when working on complicated projects. In general, the product of the project is usually divided into different parts or stages. It is called Sprint and similar to Agile. The sprint takes place regularly and its benefit is to facilitate the teams to change and adjust the most suitable solutions and results.
A Scrum development team will have slightly different components from the traditional Waterfall model, with the following three roles:
- Product owner
- Scrum Master
- Development Team
As the Scrum team is required to have a multi-functional team, the development team will include Testers, Designers, and Ops Engineers.
- Sprint Goal is unchangeable;
- The Development Team is consistent;
- Quality objectives are not reduced;
- Product Owner and the Development Team can renegotiate the scope
Sprint Planning: is the planning session for the next Sprint. This is the time the whole teamwork and discusses goals, potential risks, solutions, and detailed planning for the next step.
Sprint Planning answers the following:
- What is the purpose of this Sprint?
- What will we deliver?
- How to achieve the expected result?
In this event, the Scrum Master has responsibility for guaranteeing to take place the event. In addition, Scrum Master has to clarify the purpose and goals of the Sprint so that the development team can clearly understand them.
The main attendees include the Development Team, the Scrum Master, the Product Owner, and the stakeholders. In this review meeting, the team can share demos or let users experience the product to accumulate feedback. After that, Scrum team and stakeholders will decide together what has been done and what is not done. Then, all team collaborates about what to do next to maximize the value of the product based on changes and issues during the Sprint. In some businesses, the review meeting also includes many aspects that can impact the value of the product. In particular, they will review the marketplace and its potential to define what they should change or enhance features.
- What went well?
- What needs to be enhanced?
- What we commit to enhance the next process?
At the end of the Sprint Retrospective, the Scrum Master has to ensure to evaluate and identify what they should enhance and implement in the next Sprint.
Why Scrum is popular?
Scrum is well known for its flexibility in the process. All processes give the development team a chance to make innovation and changes based on client requirements and marketplace consecutively. Also, the duration of the project can be shortened. Particularly, Scrum allows the team to be creative and innovative to deploy their product but keep them in line. Scrum is easy for a team to learn and implement it in real cases as fast as possible. In addition to minimizing risks and issues, the development team can work with high efficiency and productivity for consecutive enhancement.