Scrum is an agile framework for developing software but can be used in many other industries as well. Scrum was created by Jeff Sutherland and Ken Schwaber in early 1990s and has since been the most popular agile method.

Scrum is a lightweight, simple to understand and difficult to master. Almost like chess, the rules are simple but it takes a lifetime to master.

Scrum framework has roles, artifacts, events and other things connected to the Scrum team. Scrum uses an iterative and incremental way of developing software in a complex environment. At its core Scrum framework delivers flexibility, handles unforeseeable events and focus on team effort.

Roles in Scrum

Scrum Team consist of development team, product owner and Scrum master. The Scrum team is self-organized, cross-functional and decides how the work should be done.

Product Owner is responsible for managing the product backlog and maximizing the value of the product.

Scrum Master is responsible to make sure the Scrum process is understood and works. The Scrum Master is a servant to the team and Product Owner and make sure to help them and everyone outside the team to understand the Scrum Framework, theory, rules and practices.

Events in Scrum

Sprint in Scrum is time-boxed intervals. Sprints are usually around one month or shorter. After each sprint the outcome should be functional software. A Sprint consist of Sprint Planning, Daily Scrum, development work, Sprint Review and Sprint Retrospective.

Sprint Planning is where the Scrum Team sits and plan for the sprint. The meeting should be time-boxed to maximum of 8 hours for one month sprint, can be shorter if the sprint is shorter.

Daily Scrum is a daily 15 min meeting for the development team to synchronize daily activities and plan for next 24 hours.

Sprint Review is where the Scrum Team and stakeholders review the latest sprint and product backlog. This is not a status meeting but a way of adapt the backlog or next sprint together with Product Manager and Stakeholders.

Sprint Retrospective is the event where the Scrum Team can learn from previous sprint and create a plan to improve for the next sprint period.

Scrum Artifacts

Product Backlog is an ordered list of everything that might needs to be done in a product. Product Owner owns the backlog and make sure that it is up to date all the time. This backlog list all features, functions, stories, fixes etc that’s need to be developed by the Scrum Team.

Sprint Backlog is a smaller set of the product backlog. It contains all the items that are planned to be worked on in upcoming sprint by the development team. The sprint backlog is locked under a sprint and only the development team can changes the sprint backlog under ongoing sprint.

Read More: 


Thanks to Jimmy Janlén for letting me use his pictures from Agile Topics Cards.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s