Going the Scrum Way

In one of my earlier piece, I had focussed on Agile Methodology. Like every other thing the Agile Methodology also evolved and over a period of time there were variations introduced to it. But at the heart of all different type of Agile Methodologies, one thing which remained consistent was its fundamental principle to put consumers before self.

Scrum is an agile software development framework for managing projects. Scrum is an iterative and incremental method and like other agile methodology, it focuses on project management process which is more flexible and accountable.

Scrum is different from other agile methodology because it heralded the idea of “empirical process control” which in a layman’s language means that it takes into account an actual progress of the project in order to decide next course of action or deal with adversaries.

But at the core of Scrum Methodology still lies the cardinal belief that the there is no leader and the team decides how to go past a hurdle. It’s a collective effort of the team to meet the goal.

First, reason why Scrum works smoothly and efficiently is because in it project is divided into Sprints. Secondly, there are set of roles, responsibilities, and meetings that never change. The two clubbed together form a project management methodology in which people relish working.

There has been some confusion regarding Sprint and Scrum and there are folks out there who think both are same (I was also one of them) but that isn’t true.

A Sprint is a basic and essential subsidiary of Scrum Methodology. In Sprint, the team decides the amount of work which needs to be accomplished in certain time period. Sprint length varies from 3 to 4 weeks.  Once a Sprint has set it goals and framed its timelines then it’s not altered unless and until there is something really important.

In Scrum methodology there are three principal roles: Product Owner, Scrum Master, and Team Member.

Product Owner is the go-to man in Scrum. She/he is the person responsible to bring the product to a potentially shippable state at the end of each Scrum sprint. Product Owner is the man who communicates vision to the team and makes sure that product meets it requirement.  Product Owner prioritizes product backlog and micro-manages other nitty-gritty’s of the sprint.

Scrum Master acts as a facilitator for Product Owner and Team. The fundament role of Scrum Master is to shield the team from distractions and motivate the members to achieve the goals of the sprint.

In Scrum, Team is responsible for building the product which is good to be shipped. A team consists of mix of all professionals required to complete sprint product backlog. Tam members are self-organizing group and there is no hierarchy among them.

Building products using Scrum is fun and interactive. Product Owner takes care of preparing product backlog. Product backlog contains new set of features and enhancements which need to be implemented and some spill over of previous sprint, if any.

Sprint planning meeting is performed at the start of each sprint where priority for product backlog items and sprint length is decided based on opinion of all team members.

During Sprint, daily meetings (10-15mins) are conducted where members pick items from product backlog. It’s a good habit to conduct Sprint review at the end of each sprint.

The fabric of Scrum Methodology lies in teamwork and conviction. And in the process you get the pleasure of creating something which adds value to our life.


2 thoughts on “Going the Scrum Way

Leave a Reply

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

WordPress.com Logo

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

Google+ photo

You are commenting using your Google+ 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