Scribd
Upload
165 views

SDLC (Software Development Life Cycle) : by Sapna

The document defines the Software Development Life Cycle (SDLC) and summarizes several SDLC methodologies. It describes the waterfall model as a sequential design process with distinct phases from conception to maintenance. It then explains that agile software development is iterative and incremental, with requirements and solutions evolving through collaboration between cross-functional teams. Finally, it provides an in-depth overview of the scrum framework for agile software development, covering roles, meetings, terminology, and comparing it to the waterfall model.

Uploaded by

Zerihun Alemayehu
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
165 views

SDLC (Software Development Life Cycle) : by Sapna

The document defines the Software Development Life Cycle (SDLC) and summarizes several SDLC methodologies. It describes the waterfall model as a sequential design process with distinct phases from conception to maintenance. It then explains that agile software development is iterative and incremental, with requirements and solutions evolving through collaboration between cross-functional teams. Finally, it provides an in-depth overview of the scrum framework for agile software development, covering roles, meetings, terminology, and comparing it to the waterfall model.

Uploaded by

Zerihun Alemayehu
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 20

SDLC

(Software development life


cycle)
By
Sapna

SDLC Definition

SDLC- Software development life cycle is a


term used in systems
engineering,information
systemsandsoftware engineeringto
describe a process for planning, creating,
testing, and deploying an information
system.

SDLC

SDLC Methodologies
Waterfall
Spiral
Agile
Rational Unified Process(RUP)
AD hoc

Waterfall Methodology

Description

Thewaterfall
modelis
asequentialdesignprocess,
used
insoftware
development processes, in which progress is seen
as flowing steadily downwards (like awaterfall)
through
the
phases
of
Conception,
Initiation,Analysis,Design, Construction,Testing,
Production/Implementation, andMaintenance.

Agile Method

Agile software developmentis a group


ofsoftware
development
methodsbased
oniterative and incremental development, in
which requirements and solutions evolve through
collaboration
between
self-organizing,crossfunctional teams.

Agile Software Development


Methods
Adaptive Software Development(ASD)
Agile Modeling
Agile Unified Process(AUP)
Crystal Methods (Crystal Clear)
Disciplined Agile Delivery
Dynamic Systems Development Method(DSDM)
Extreme Programming(XP)
Feature Driven Development(FDD)
Lean software development
Kanban
Scrum
Scrum-ban

Scrum

Scrumis an iterative and incrementalagile


software development framework for managing
product development. It defines "a flexible,
holisticproduct development strategy where a
development team works as a unit to reach a
common goal",

Roles
Product owner
Development team
Scrum Master

Meetings
Sprint Planning Meeting
Daily Scrum Meeting
End Meetings (Sprint review and Sprint
Retrospective)

Terminologies
Scrum Team
Product Owner, Scrum Master and Development Team
Product Owner
T he person responsible for maintaining the Product Backlog by representing
the interests of the stakeholders, and ensuring the value of the work the
Development Team does.
Scrum Master
The person responsible for the Scrum process, making sure it is used correctly
and maximizing its benefits.
Development Team
A cross-functional group of people responsible for delivering potentially
shippable increments of Product at the end of every Sprint.
Sprint burn down chart
Daily progress for a Sprint over the sprint's length.
Release burn down chart
Sprint level progress of completed product backlog items in the Product
Backlog.

Terminologies
Product backlog (PBL)
A prioritized list of high-level requirements.
Sprint backlog (SBL)
A prioritized list of tasks to be completed during the sprint.
Sprint
A time period (typically 14 weeks) in which development occurs on a set of backlog
items that the team has committed to. Also commonly referred to as a Time-box or
iteration.
Spike
A time boxed period used to research a concept and/or create a simple prototype.
Spikes can either be planned to take place in between sprints or, for larger teams, a
spike might be accepted as one of many sprint delivery objectives. Spikes are often
introduced before the delivery of large or complex product backlog items in order to
secure budget, expand knowledge, and/or produce a proof of concept. The duration
and objective(s) of a spike will be agreed between the Product Owner and Delivery
Team before the start. Unlike sprint commitments, spikes may or may not deliver
tangible, shippable, valuable functionality. For example, the objective of a spike might
be to successfully reach a decision on a course of action. The spike is over when the
time is up, not necessarily when the objective has been delivered.

Waterfall VS Agile

Waterfall VS Agile

You might also like