So friends in my last few posts, we tried to know what various ‘Agile Methodologies‘ are and ‘Scrum‘ is the one which is mostly used. Now let’s try to find out, What actually is ‘SCRUM’ ?
According to Wikipedia:
Scrum (an abbreviated form of scrummage, which is now rarely used, except as a verb), in the sports of rugby union and rugby league, is a way of restarting the game, either after an accidental infringement or (in rugby league only) when the ball has gone out of play.
Scrum, in our case , is an iterative & incremental project delivery framework.
So Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. It allows us to rapidly and repeatedly inspect actual working software (at end of sprint cycle/iteration). The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.
At end of sprint cycle/iteration , stakeholders can see real working software and decide to release it as is or continue to enhance it for another sprint.
So a typical Scrum cycle looks like :
Characteristics of Scrum:
- Self-organizing team
- Product progresses in a series of “sprints” (ideally 2-4 weeks)
- Requirements are captured as items in a list of “product backlog”
- No specific engineering practices prescribed
- Uses generative rules to create an agile environment for delivering projects
- And of-course it is one of the “Agile Processes”
Now, we know the basic of Scrum methodology. Let’s talk about Roles in Scrum.
Roles: There are following 3 roles in scrum.
Team: Responsible for doing the work
- 7 +/- 2 People
Product Owner: Responsible for maximizing the value of the work that the Team does
- Owns the vision and overall goals
- Owns the prioritized list of what needs to be produced to achieve maximum value and ROI (the Product Backlog)
- Decides when product is ready to ship
Scrum Master: Responsible for ensuring the Scrum process is understood and followed. Scrum Master is the one who is: ‘Process Owner’ , ‘Problem Solver’ and ‘Protector’ of the Team.
As a Process Owner, Scrum Master :
- Teaches Scrum to Team, PO, and stakeholders
- Coaches the Team, PO, and stakeholders to achieve maximum value and ROI by improving practices
- Change agent for the organization
As a Problem Solver, Scrum Master :
- Helps remove blocks and assists the Team and Product Owner
As a Protector , Scrum Master:
- Protects the Team from disruption
Now, let’s look at the Scrum cycle (in detail) again:
We can see the three roles and the how they fit in the scrum cycle. Apart from ‘Roles’ , the above image also shows ‘Scrum Ceremonies‘ and ‘Scrum Artifacts‘.
Scrum Ceremonies:There are following ceremonies in Scrum:
- Sprint Planning
- Daily Scrum Meeting
- Sprint Review/Demonstration
- Sprint Retrospection
Scrum Artifacts:There are following artifacts in Scrum:
- Product Backlog
- Sprint Backlog
- Product Increment
We will discuss about ‘Scrum Ceremonies‘ and ‘Scrum Artifacts‘ in detailed manner in my next post.