What is Scrum?
How does Scrum work?
Roles in a Scrum Team
Product Owner: The product owner is the person who knows and understands the customer’s requirements. He is responsible for resolving doubts about the product and defining the best way forward for the team. He is also responsible for defending the team and protecting it from external interference, such as sudden changes that are not in line with the team’s objectives. His responsibilities also include:
- Prioritizing the product backlog
- Deciding which backlog items to include in each sprint
- Ensuring that the team clearly understands the sprint objectives and expected deliverables.
Scrum Master: The Scrum Master role is critical to the success of a Scrum team. He is a servant leader who guides the team in adopting the Scrum methodology, including encouraging self-management, inspection, transparency, and collaboration. To this end, the Scrum Master removes obstacles and facilitates effective communication between all team members. They also promote continuous work process improvement and is responsible for creating a safe and trustworthy working environment in which problems can be effectively addressed and resolved. In this sense, the Scrum Master also plays an important role in conflict management, fostering an environment of healthy debate and discussion where difficult issues can be addressed in the pursuit of the project.
Product Backlog
Events in Scrum
Sprint Planning: Sprint planning takes place at the beginning of a sprint. It is an event that defines the work to be done during that sprint. The product owner must ensure that the team understands the project goals and priorities before this event so that the team is prepared to discuss prioritization. During this planning session, the product owner and the development team decide which tasks from the backlog to include in the sprint. The development team knows their skills and capabilities, so they can decide how much work to commit to. Sprint planning becomes more efficient and effective as the team gets to know each other and learns to work together more effectively.
Daily Scrum: This is an event that occurs every day during the sprint, preferably at the same time and place to reduce complications. This meeting should last no longer than 15 minutes. During the daily Scrum, progress toward the sprint goal is discussed. The development team can choose their preferred method of conducting these meetings. A common method is for each team member to answer three key questions: What did I do yesterday? What will I do today, and are any obstacles preventing me from moving forward? This ensures that all team members are aligned on the tasks and any possible obstacles. The Scrum Master is responsible for ensuring that the meeting is effective and does not turn into a long discussion session.
Sprint Review: This event is product-focused. It reviews whether the sprint objectives have been met, whether it is on track to meet the project objectives, and what can be improved. Anyone involved in the project (such as the product owner or other stakeholders) is invited to the review to give feedback. This helps to ensure that everyone is on the same page and that the work is meeting requirements and expectations.
Sprint Retrospective: This event focuses on the work process. During a sprint retrospective, the team comes together to reflect on how the sprint was carried out and how the work process can be improved. The sprint retrospective aims to identify what worked well and what did not and to propose solutions to improve the efficiency and quality of the work. It can also be used to discuss issues related to cooperation and communication within the team, such as the distribution of tasks and responsibilities, the quality of teamwork, etc.
0 Comments