AGILE – SCRUM PROJECT EXECUTION METHODOLOGY

Scrum is a process framework that enables teams to deliver the highest business value in the shortest time. Team first builds a log of work items to be delivered. It is called Product backlog and is owned by a product owner. The delivery of work items in Product backlog occurs over multiple iterations called Sprints.

In each sprint team picks the work items from product backlog and put them in the sprint backlog. Life of a sprint backlog is same as of a sprint. Usually the size of the all the sprints is same, either of 2 to 4 weeks. Best way to decide the length of a sprint is, the duration you expect there will be no change in the work items you are planning to work in a sprint.

Each sprint is given a unique number (first sprint is called sprint 1) starting from 01 and increases by one with every new sprint. To ensure team is following the scrum, a Scrum master works with the team to guide and resolve their issues. To know more about scrum https://www.agilealliance.org/glossary/scrum

Before starting the sprint 1, the scrum master must run a Sprint 0. There is no fix duration of the sprint 0. During the sprint 0, the team should get the all the required information to start the development in Sprints. Below are the typical information team must have before starting the Sprint 01.

Once team gets what it needs to commence the development work, scrum master should announce the end of Sprint 0, and announce the date of Sprint 1.

During the project execution under scrum, you need to maintain various controls. The project progress will be assessed using these controls during the project. To understand the controls which you need to maintain during the Scrum, please refer the below diagram.

As advised by Scrum Alliance, sprint duration should be 2-4 weeks. To understand how a sprint should be executed, a 2-week sprint example.

Analysis phase i.e. 20 % of the sprint is spent for the Analysis/ Design of the user stories picked into the sprint backlog. Development phase i.e. 50% of the sprint is spent on coding, unit testing, test cases development, automation script development, code reviews, User stories clarifications etc. At the end of the development phase, the development team announces the code freeze and plan for a demo to PO/ BA/ test team.

The purpose is to bring the ownership of doing the things right at the first time. It also brings the focus on various stakeholders who are supposed to provide necessary information to the team and remove their impediments. Testing phase consumes next 20% of the sprint where various functional/non-functional tests gets executed manually or with automation.

The purpose is to bring the ownership of doing the things right at the first time. It also brings the focus on various stakeholders who are supposed to provide necessary information to the team and remove their impediments. Testing phase consumes next 20% of the sprint where various functional/non-functional tests gets executed manually or with automation.

Product backlog refinement is a continuous activity where the team in collaboration of PO/BA size and prioritize the User Stories, add details & acceptance criteria. It helps in sprint planning to create sprint backlog. Team spends time whenever they have bandwidth.

There are 4 ceremonies which are supposed to be conducted.