What is Scrum?
Scrum is a framework that helps teams work together. Much like a rugby team (where it gets its name) training for the big game, scrum encourages teams to learn through experiences, self-organize while working on a problem, and reflect on their wins and losses to continuously improve.
While the scrum I’m talking about is most frequently used by software development teams, its principles and lessons can be applied to all kinds of teamwork. This is one of the reasons scrum is so popular. Often thought of as an agile project management framework, scrum describes a set of meetings, tools, and roles that work in concert to help teams structure and manage their work.
How does scrum project management work?
The scrum approach to project management enables software development organizations to prioritize the work that matters most and break it down into manageable chunks. Scrum is about collaborating and communicating both with the people who are doing the work and the people who need the work done. It’s about delivering often and responding to feedback, increasing business value by ensuring that customers get what they actually want.
Shifting from traditional project management approaches to scrum project management requires an adjustment in terms of the activities that are carried out, the artifacts that are created, and the roles within the project team:
Activities in scrum project management
The main activity in scrum project management is the sprint, a time-boxed iteration that usually lasts between 1-4 weeks, with the most common sprint length being two weeks.
Sprint planning meeting: at the start of each sprint, a planning meeting is held to discuss the work that is to be done. The product owner and the team meet to discuss the highest-priority items on the product backlog. Team members figure out how many items they can commit to and then create a sprint backlog, which is a list of the tasks to complete during the sprint.
Daily scrum or daily standup: each day during the sprint team members share what they worked on the prior day, will work on today, and identify any impediments. Daily scrums serve to synchronize the work of team members as they discuss the work of the sprint. These meetings are time-boxed to no more than 15 minutes.
Sprint review: at the end of a sprint, the team demonstrates the functionality added during the sprint. The goal of this meeting is to get feedback from the product owner and any users or other stakeholders who have been invited to the review.
Sprint retrospective: at the end of each sprint, the team participates in a retrospective meeting to reflect on the sprint that is ending and identify opportunities to improve in the new sprint.
Sprint Demo: at the end of each sprint, the team will have a demo to the clients to show what exactly to do during the sprint and they will show the output product to the clients.
Then with the scrum team and clients have all the control over the project and the changes could implement fast and clients will be completely aware of the work progress.