Scribd
Upload
59 views15 pages

Lecture 8 - Agile Software Development

This document provides an overview of Scrum, an agile software development method. Scrum emphasizes short development cycles called sprints, prioritized backlogs of requirements, daily stand-up meetings, and demonstrations of deliverables to customers. It was conceived in the 1990s to help projects with tight timelines and changing needs. Scrum principles align with the agile manifesto and incorporate requirements, analysis, design, development, and delivery in a flexible framework conducted through sprints and guided by a product backlog and daily stand-ups.

Uploaded by

Sufyan Abbasi
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
Download as ppt, pdf, or txt
59 views15 pages

Lecture 8 - Agile Software Development

This document provides an overview of Scrum, an agile software development method. Scrum emphasizes short development cycles called sprints, prioritized backlogs of requirements, daily stand-up meetings, and demonstrations of deliverables to customers. It was conceived in the 1990s to help projects with tight timelines and changing needs. Scrum principles align with the agile manifesto and incorporate requirements, analysis, design, development, and delivery in a flexible framework conducted through sprints and guided by a product backlog and daily stand-ups.

Uploaded by

Sufyan Abbasi
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1/ 15

Introduction to Software Engineering

Agile Software Development(3)

Muhammad Nasir
m.nasir@iiu.edu.pk
Agenda
 SCRUM
 Sprint
 Back Log
 SCRUM Meetings
 Demos
SCRUM
 Scrum (*the name is derived from an
activity that occurs during a rugby
match) is an agile software
development method
 Conceived by Jeff Sutherland and his
development team in the early 1990
 * A group of players forms around the ball and the teammates
work together (sometimes violently!) to move the ball
downfield
SCRUM
SCRUM
 Scrum principles are consistent with
the agile manifesto and are used to
guide
 Development activities within a
process that incorporates the following
framework activities: requirements,
analysis, design, evolution, and
delivery.
SCRUM
 Within each framework activity, work
tasks occur within a process pattern
called a sprint.
 The number of sprints required for
each framework activity will vary
depending on product complexity and
size
SCRUM
 The work conducted within a sprint is
adapted to the problem at hand and is
defined and often modified in real time
by the Scrum team.
SCRUM
 Scrum emphasizes the use of a set of
software process patterns that have
proven effective for projects with tight
timelines, changing requirements
 Back Log
 Sprints
 Scrum Meetings
 Demos
Back Log
 A prioritized list of project
requirements or features that provide
business value for the customer.
 Items can be added to the backlog at
any time (this is how changes are
introduced).
 The product manager assesses the
backlog and updates priorities as
required
Sprints
 Sprints—consist of work units that are
required to achieve a requirement defined in
the backlog that must be fit into a
predefined time-box (typically 30 days)
 A time-box is a project management term
that indicates a period of time that has
been allocated to accomplish some task.
Scrum Meetings
 Scrum meetings—are short (typically 15
minutes) meetings held daily by the Scrum
team.
 Three key questions are asked and
answered by all team members:
 What did you do since the last team meeting?
 What obstacles are you encountering?
 What do you plan to accomplish by the next team
meeting?
Scrum Meetings
 A team leader, called a Scrum master,
leads the meeting and assesses the
responses from each person.
 The Scrum meeting helps the team to
uncover potential problems as early as
possible.
 Also, these daily meetings lead to
“knowledge socialization” and thereby
promote a self-organizing team structure.
Demos
 Demos—deliver the software
increment to the customer so that
functionality that has been
implemented can be demonstrated
and evaluated by the customer.
Demos
 It is important to note that the demo
may not contain all planned
functionality, but rather those
functions that can be delivered within
the time-box that was established.
The End
 Thanks for listening
 Questions would be appreciated.

You might also like