SCRUM Overview

Reddi Babu Karanam (138894)

Anantesh Padigar : (229904)
Muppala Suresh : (231381)
Hari Babu Thatikonda : (235815)

April 14, 2016

Copyright © 2012 Tata Consultancy Services Limited

1
 Chapter - 1

Agile Introduction

Types of Agile methodology

SCRUM Introduction

2
 Agile Introduction

 What Is Agile?
 Agile methodology is an alternative to traditional
project management for software development.
 It helps teams respond to unpredictability through
incremental, iterative work cadences, known as
sprints.

Why Agile?
 Agile development methodology provides
opportunities to assess the direction of a project
throughout the development lifecycle.

3
 Types of Agile methodology

Agile methods are processes that support the agile philosophy.

Agile promotes adaptive planning, evolutionary development,

early delivery, and continuous improvement, and it
encourages rapid and flexible response to change.

4
5
 Scrum Introduction and Background
• Scrum is a lightweight agile project management framework with
broad applicability for managing and controlling iterative and
incremental projects of all types.

• Name taken from the sport of Rugby, where everyone in the team
pack acts together to move the ball down the field.

• Analogy to development is the team works together to successfully

develop quality software.

6
 Chapter - 2

SCRUM Roles

7
Overview

8
Product Owner

9
Scrum Master

10
Development Team

11
 Chapter - 3

SCRUM Artifacts

12
User Story : 1

13
User Story : 2

14
The 3 Artifacts

15
 Artifact # 1 : Product Backlog

 A list of features, prioritized by business value

 Contains User Stories with high level details

 Maintained by Product Owner

 Is a Live/Evolving artifact

16
Product Backlog Sample

17
 Artifact # 2 : Sprint Backlog

 Subset of Product Backlog, loaded onto

Sprint’s “timebox”

 Lists work for team in a given sprint

 Maintained by Development Team

 Converts Product backlog to an Increment

18
Sprint Backlog Sample

19
 Artifact # 3 : Increment

 Potential Shippable product

 Evolved from Product backlog after every sprint

 All increments must be classified as ‘Done’

20
Burn-down & Burn-up Charts

21
Why 2 charts ?

22
 Chapter - 4

SCRUM Events

23
Overview

24
Sprint Planning

25
Daily Scrum Meeting

26
Sprint Review

27
Sprint Retrospective

28
Waterfall vs Agile Model - 1

29
Waterfall vs Agile Model - 2

30
 Thank You

IT Services
Business Solutions
Consulting