Scribd
Upload
63 views

SCRUM Methodology: Created by Rajwant Singh

The document describes the basic steps of the SCRUM methodology: 1. Define the team roles including the stakeholder, project manager, scrum leader, and delivery team. 2. Create an initial product backlog by listing all features and requirements in order of priority. 3. Plan sprints as iterations of fixed duration, such as one week, to complete tasks from the backlog. Daily standups keep the team aligned and help remove obstacles.

Uploaded by

amrish\_88
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
63 views

SCRUM Methodology: Created by Rajwant Singh

The document describes the basic steps of the SCRUM methodology: 1. Define the team roles including the stakeholder, project manager, scrum leader, and delivery team. 2. Create an initial product backlog by listing all features and requirements in order of priority. 3. Plan sprints as iterations of fixed duration, such as one week, to complete tasks from the backlog. Daily standups keep the team aligned and help remove obstacles.

Uploaded by

amrish\_88
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

SCRUM methodology

Created by
Rajwant Singh
1. Define your Team

Identify the Stakeholder, Project Manager, Scrum Leader and Delivery Team.
 Stakeholder can be the Customer, End User. Essentially, for whom the project
or product is developed for.
 Project Manager is essentially the Product Owner who is in touch with the
Stakeholder. This role manages the Backlog (will explain Backlog in upcoming
slides) and is the only person who can prioritise the Backlogs for sprint.
 Scrum Leader or ScrumMaster facilitates the team, removes any obstacles or
issues and ‘isolates’ the team from distractions.
 Delivery Team is the group of people responsible for actually delivering the
project.
2. Create Initial Product Backlog

 A meeting called Sprint 0 is held which is attended by whole Team. If it suits,


Stakeholders can be invited as well.
 The Product backlog (or a User Story) is a wish list or Feature List
(requirements) that is expected to be completed in the project. For e.g.
iesphere Login Page is a feature. And “creating a Login Page” is a Backlog.
 Project Owner can priorities the Backlog items. For e.g. IT helpdesk creation
module feature in iesphere can carry more priority than Login Page creation.
3.Plan Sprints

 A Sprint is an iteration or a loop or a cycle of days fixed to complete tasks.


 Given that the Project Manager has prioritised the Backlog and before Sprints are started,
another meeting is held where Backlog with highest priority is discussed. In this meeting, the
Backlog is divided into tasks. It can be only one or many. These tasks are sized as per effort
required. It can S for small, M for medium, L, XL. And then these Tasks are assigned to Team
members.
 Lets say a Sprint is fixed to be a Week long. Hence all the created tasks are to be completed
in this fixed duration.
 And so on, next Backlog in next Sprint…
 An XL task can sometimes be big enough to be made a Backlog itself and then divided into
smaller tasks and then assigned a complete Sprint to finish it.
 Also, a Backlog can be small enough to become a task and squeezed into existing Sprint. You
can always work on multiple Backlogs in one Sprint, there is no max or min number but
Capacity of the team.
Task Card

 This can be used to better understand Tasks


How can I plan a Sprint duration?

 This depends on the number of delivery team members available.


 And the number of days and then the respective number of hours in each day.
 Lets assume there are 3 delivery team members who can work 8 hours after
giving them an hour of break and an hour of discussions etc. or frankly
speaking, an individual works 8 hours a day. Total 5 days Sprint will have
3x8x5 = 120 hours.
 Project Leader needs to use his/her experience to deduce that how many
tasks can be completed in the available hours and hence assign those Tasks to
this Sprint.
Daily Standups

 Every morning, at least 15 minutes are set aside for meeting between Team
and Scrum Master to discuss progress, any roadblocks etc.
 Scrum Master can in turn meet Project Leader.
 If any additional requirement arises in ongoing Tasks, those are duly noted
down but not acted upon. They will be tended to in next Sprint.
Sprint End – Review and Retrospect

 Lets say end of Sprint falls on Friday evening…


 The product/project outcome after the Sprint is discussed and can be shared
with Stakeholders if needed.
 Whole team meets and status of all tasks are discussed.
 Team can discuss the way the goals were achieved. Share knowledge of
roadblocks faced and how they were eliminated.
 In case any task was not completed, the Sprint is deemed to have Failed. This
task will be moved to then next Sprint. As we are part of IT, Test Driven
methodology is better to figure out whether Tasks outcome is to be deemed
as Success or failure.
Next Sprint

 As obvious, Sprint is planned for remaining Backlogs and so on…


Release

 Once all Backlogs have been completed successfully, the product should be
ready for release.

You might also like