Scrum is a process that is designed to try and maximize the amount of scope that can be produced with a fixed amount of time and budget. This means that scrum is only appropriate in cases where the scope doesn't need to be fixed. Some good examples of this would be software development, maintenance, and updates. An example of something you would not use scrum for is manufacturing a physical product. I cannot build a third of a chair and expect to sell it. Scrum uses an iterative process called “Sprints” in order to produce some functional piece of the project.
This is typically referred to as an increment or deliverable. To use Scrum on a project, you need to put together a Scrum team. This typically consists of 3 parts: The product owner, the scrum master, and the development team. The product owner is responsible for interfacing with the client. Their purpose is to understand the vision, direction, and bring that focus to the scrum team. The scrum master is responsible for overseeing the completion of deliverables, acts as a coach for the development team, and acts as an advocate for that team.
The development team is responsible for creating the deliverables. Once you have your team together, you need to adopt a work rhythm. This rhythm is called a “Sprint”. Sprints are a repeatable process that you perform over and over until you run out of budget and time. When that happens, all the deliverables that have been created from this process will constitute the end scope. Whatever was produced amounts to what was possible with the allotted time and budget for the project. Moreover, using the Scrum process ensures that the things produced were the most valuable deliverables.
A sprint is an interval of time composed of:
1. Prioritizing the Backlog
2. Planning Meeting
3. Execution
4. Review
5. Retrospective
Sprint Duration
The length of your sprint should match your team’s rhythm and the pace at which you need to deliver updates and gather feedback. Common sprint durations are one to four weeks. Shorter sprints allow for quick adjustments based on feedback, while longer sprints may enable more complex features to be developed. Choose a duration that allows your team to produce functional, testable deliverables, keeping in mind the need for a sustainable pace and consistent progress.
Prioritizing the Backlog
If it's the first sprint, the process starts with the client's wish list, which includes all the features they want in the software. The product owner, through discussions with the client, organizes these items into a prioritized list known as the backlog. For later sprints, the product owner updates the backlog based on feedback received during the review sessions. These updates are arranged in order of importance, aligning with the client’s vision to ensure that critical enhancements are prioritized for upcoming sprints.
Planning Meeting
The planning meeting is a crucial time when the product owner, scrum master, and development team come together to prepare for the next sprint. During this meeting, there’s a dynamic discussion: the product owner pushes for high-priority features from the backlog, while the development team and scrum master focus on what’s achievable, given the time and resources. This dialogue helps balance ambition with realism, ensuring the team commits to deliverables that are both valuable and feasible. Through this conversation, the team decides what the deliverables should be for the upcoming sprint.
Execution
During the execution of the sprint cycle, the scrum master and the development team gather daily for a "stand-up" or "daily scrum." This meeting serves to check in with the team by answering key questions: How is it going? Are we still on schedule? Does anyone need support or additional resources? Is the team working well together? Typically, if all is progressing well, this meeting will only take a few minutes. However, any issues should be brought up immediately. The daily frequency of these meetings is crucial for catching and addressing problems as they arise. The scrum master’s role is crucial here, acting as an advocate for the development team by removing obstacles, securing necessary resources, and fostering team cohesion.
Review
At the end of each sprint, the team holds a review meeting, where the product owner presents the sprint's deliverables to the client. This session is crucial as it allows the client to directly interact with the new features. Not only does this interaction provide valuable feedback, but it often sparks new ideas for additional features that had not been considered before. All insights from the session are added to the product backlog, ensuring that the project continuously adapts and improves. This is how Scrum ensures the most valuable deliverables are produced.
Retrospective
The retrospective meeting is a crucial discussion held between the scrum master and the development team at the end of each sprint. Its purpose is to reflect on the past sprint to identify what worked well and what didn't. This is the time to fine-tune the process based on real experiences. Recognizing that each team member brings their own strengths and challenges is vital. The nuances of each sprint can vary significantly from team to team. During this meeting, the team discusses how to make improvements and implement them for the next sprint.
Final Thoughts
Scrum is all about flexibility and continuous improvement. Each part of the Scrum process, from planning sprints to conducting reviews and retrospectives, is designed to make both the team and the product better. The key to success with Scrum is knowing when to use Scrum and knowing how to adapt to changes. By welcoming feedback and making adjustments, teams can not only achieve their goals but also improve with every project.
You can find more related content on our website by clicking HERE