Scrum Framework Do you think it is a process

Scrum Framework - Do you think it is a process?

Most of the people think that “scrum” is a process oriented, but it’s a framework within which process, techniques and practices are employed.

It designed to address complex product development with effective team collaboration. It boosts the productivity with highest possible value in iterative and incremental way. Co-creators of scrum are Ken Schwaber and Jeff Sutherland.

Why scrum got lot of attention from people over waterfall model at that time?

Waterfall model is a lengthy process which takes several months and deploys complete product.

Plan ->design->build ->test -> review -> deploy.

Serious problems that encounter with this process are

  • User requirements might go wrong.
  • Planning might go wrong.
  • Issues might have observed after delivering the product.

All these might lead to start the entire process again.Whereas scrum delivers smaller chunks of the product in an effective and iterative way.

Plan-> design-> Build->Test->Review->Deliverable product

Each of the above cycle is called as sprint.A release cycle contains ‘n’ number of sprints.

Most of the software companies consider 4 weeks as a sprint. There can be small sprints also.

Scrum life cycle

Now let’s understand the scrum keywords and their importance.

The 3 roles of a Scrum

Product owner – Defines the required features for a product.

ScrumMaster – Leads the team by protecting the process and make sure that the things are going in a right way.

Team – Made up of developers, testers and writers etc. Anyone can play any role.

Scrum Artifacts

Product backlog

This is where product owner creates a list of user stories for a product considering customer requirements. Each user story explains a new functionality or fix for a bug mentioned by customer. It grooms continuously.

Release backlog

It’s a subset of Product backlog, which will be consider for a product release. Handle by Product owner.

Sprint backlog

It’s a subset a of Release backlog, which will be taken for a sprint. Handle by product owner and Scrum Master.

Burndown chart

Shows the progress of work for a sprint. This will be updated by Team every day.

Scrum Ceremonies

Sprint Planning

Sprint planning occurs before starting of the sprint with all the team members and the product owner.

This again internally divided into two meetings.

  • One is with Product owner and Team where product owner assign backlogs to a sprint based on the priority.
  • Second one will be conducted internally with Team. The main goal is to plan and estimate sprint backlogs considering team capacity and velocity.

Team capacity – The effective work spend by each team member on each day of a particular sprint.

Most of the software companies consider 5 hours per day for a team member and consider total sprint days are 4 weeks. So, a single team member capacity without considering leaves, holidays are 5*20 = 100 hours.

Team velocity – Each sprint backlog item will be assigned with some points based on task complexity by Team.

Sprint points are like 1,3,5,8,13,20,40 like that.

After completion of the sprint, all the points for completed backlogs will be calculated and the total is consider as team velocity.

Planning – Divide a backlog as per DOD. A DOD mainly consists of analysis/design, implementation, testing(with code coverage of 80%), integration and verification of a backlog.

Daily Scrum Meets

These are also called as stand-up meetings where all the team members assemble at a particular time and each team member answers the following points.

  • What did I do yesterday?
  • What I am going to do Today?
  • Are there any obstructions?

Sprint Review

Occurs on last day of the sprint where all team members, product owner and stake holders assemble.

Team presents the functionalities that they completed in that sprint by demo. The purpose is to obtain the feedback for implemented functionality/feature.

Sprint Retrospection

Team conducts this meeting after the sprint planning. Scrum master leads this meeting.

The main objective is to improvise each sprint by taking the answers from team members for the below queries.

  • What went good in the sprint?
  • What went bad?
  • Are there any ideas to improvise?
  • What should be done differently?

Conclusion:

Scrums can be used to deliver the right product in right time to customer with quality. The sprint timelines may vary based on team and requirements.

Search Site


Newsletter

Get the latest updates from us with your email id without any spams.


Lets Connect

© 2017 shoutera. All Rights Reserved.