The Scrum approach to Agile Software Development marks a dramatic departure from waterfall management.
Scrum is one of the most popular frameworks for implementing Agile. Because of its popularity, many organizations claim to be “using Scrum” but aren’t doing anything close to Scrum’s actual definition.
Scrum emphasizes on empirical feedbacks and self-management team, while striving to build a properly tested product implemented within short iteration.
It was originally created for the software development, which can be used by Project Managers to streamline their development process. But it works well for any complex and innovative scope of work. The possibilities are endless.
Though it's difficult to cover every aspect of Scrum, in this post we are covering its basic vocabulary and how it's implemented in our today's blog.
Without further ado, let's begin with the Scrum terminology.
Before being able to implement Scrum, it is important to be familiar with some keywords of Scrum vocabulary.
Sprint: a 30-day focused effort moving the team toward fixed goals.
Product Backlog: a prioritized feature list containing short descriptions of all functionalities desired in the product.
Sprint Backlog: a list of the highest prioritized items or tasks from the product backlog.
Scrum Master: the facilitator of the product management team who works to ensure the realization of the goals of the sprint.
Product Owner: member of the team responsible for defining and prioritizing the backlog.
Scrum Team: this includes three roles: the product owner, the Scrum Master and the members of the development team. This is a group of 5-9 people who self-organize and have joint responsibilities for completing the tasks.
Now that the basic terminology related to Scrum has been defined, below is the step-by-step Scrum process:
Here is a video that explains the Scrum Process into further detail:
Finally, you can see below a graphic representation of the Scrum Software Development Process: