Scrum is an iterative method that belongs in the agile camp of how to manage and run projects. It can be used to manage almost any type of project, software, websites, hardware, marketing, event planning, etc.
This Article is available as a Presentation and can be found at the bottom of the page.
Scrum enables self-organizing groups by promoting strong communication between the team members along with a few disciplines inside the project. The Scrum model suggests that each and every sprint begins with a short planning meeting and ends with a review. These are the fundamentals of the Scrum idea for project management.
If this is already familiar to you, here's a fast hack for Implementation of Agile with Scrum.
The most appropriate projects for agile are ones with aggressive deadlines, a high degree of complexity, and a high degree of novelty (uniqueness) to them. We want to use agile when we are doing something that is new, or at least new to the team building it. If it's something the team has done before over and over then the team probably doesn't need an agile approach.
Scrum can be condensed into the following list:
So, agile is most appropriate on any urgent project with significant complexity and novelty – which includes software development and weddings.
Scrum can be thought of as a framework for managing a process from beginning to end.
There are three distinct roles defined in Scrum:
Some of the key points of Scrum that many teams find attractive:
An example of a Story board
The following list will walk you through some of the main processes of Agile with Scrum.
The Sprint Planning meeting is the preliminary point of Scrum. It's the meeting where the entire Scrum team assembles; in collaboration with the Product Owner and the Scrum Master the team selects a user story from the backlog and the group brainstorms on it. Based on the conversation, the Scrum group decides the complexity of the story and decides if it should go into the sprint.
A typical backlog on the left, and the planned sprints on the right.
As the title suggests, it's necessary for the team to complete work to progress on the project. The people on the team works on stories until they are done and then they move on to the next. Typically, the stories are arranged on a board with discrete steps, so it's easy to get a feel for how the sprint is progressing.
An example of a card or user story
Through the sprint cycle, each day the scrum team meets for maximum fifteen minutes (typically in the morning). This is also known as the daily standup meeting.
Each team member answers 3 things:
After each sprint, the team holds a Sprint Review Meeting to demonstrate a working product increment to the Product Owner and everyone else who is interested. The meeting should feature a live demonstration, not a report. The Product Owner may verify the stories according to their acceptance criteria.
Retrospective meeting occurs after the review meeting.
The Scrum group meets and talks about the following points:
Here, we went through the main points of Agile with Scrum. If the description has aroused your interest, you can continue with our step-by-step guide on how to implement and get started with Scrum.
On the other hand, if Scrum doesn't feel right for your team, we also have a more general look into the space of project management methodologies, Agile vs. Waterfall, and all the major methods under each category. No method is the best, it all comes down to your combination of projects and team.