Ken Schwaber and Jeff Sutherland are considered parents of Scrum, and they introduced it in 1996. Scrum term comes from Rugby as once teams are stuck in a maul, the game is restarted. It is a framework that helps project management without specifying how to undertake, implement, and test a design. Scrum is not a methodology.
Why we need Scrum?
To understand this, let’s review the waterfall approach…
In a waterfall, the project is initiated by clients, and the project charter is given to a Project Manager. The project Manager hires individuals to plan, build, test, review, and deploy the product. All this is done sequentially.
There is very less involvement of the sponsor/client to review the product. Hence, you may end up with totally the wrong product that the client does not accept.
Scrum, on the other way, does this in chunks. Here, the product owner is always engaged, and before starting the next sprint, feedback is taken by the product owner.
See the below info-graph, which is a simple way to explain the key difference between waterfall & scrum management.
What is Sprint in Scrum?
A sprint is a time-boxed and result-oriented period. Its duration varies from one two-four weeks. Every sprint must add some value and should be deliverable to the client. Once the client reviews it and comments are put in the product log, they are used in the next sprint. Sprints are a “pull” based system where teamwork in a cross-functional manner. This engagement of both parties helps for easy final approval.
Product backlog came from the product owner included in the sprint backlog, and the sprint starts resulting in an incremental addition. This addition is sent to the product owner who reviews and accepts, rejects, or makes comments, if any.
The comments are further included in a product backlog, and again sprints are applied. A project can be completed in a few sprints but can go as many as required.
The output of the scrum has no chance to fail at the end. On the other hand, a waterfall is quite risky as-as the end to make a change in the project is very costly. A company goes bankrupt if this happens.
Sprint is synonymous with iteration; the only difference is that a sprint cannot go more than thirty days.
Who is a Scrum Master?
Like we have a Project Manager in a traditional waterfall in the same way, the person helping the things get done properly and managing all the engagements is known as a scrum master. He acts like a servant and a bridge between the product owner and the team.
What are the Key Roles in Scrum Management?
There are three roles in Scrum.
- The Product Owner
- Scrum Master
- The Team
The Product Owner
This is the one responsible for defining the features of the required product. This guy has bright ideas to put into the final product. This should be a knowledgeable person.
The Scrum Master
They call him a servant leader who helps keep things going and helps a median between the product owner and the team.
The team consists of around seven members plus or minus two. If you have more members, then split into more teams. Teams must be cross-functional to do all necessary analysis, design, implementation, testing, and documentation.
Sprint mechanisms in scrum are really helpful in getting things done efficiently. It will take off pressure from a team member, and the probability of project success will increase for sure. This is done under the agile umbrella and hence very adaptive in nature. This is what it has on traditional waterfall techniques.