SDLC(Software development life

cycle)By

Sapna

SDLC- Software development life cycle  is a term used in systems engineering, information systems and software engineering to describe a process for planning, creating, testing, and deploying an information system.

SDLC Definition

SDLC

Waterfall Spiral Agile Rational Unified Process(RUP) AD hoc

SDLC Methodologies

Waterfall Methodology

The waterfall model is a sequential design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production/Implementation, and Maintenance.

Description

Agile software development is a group of software development methods based on iterative and incremental development, in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.

Agile Method

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

Agile Software Development Methods

Scrum is an iterative and incremental agile software development framework for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal",

Scrum

Product owner Development team Scrum Master

Roles

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

Retrospective)

Meetings

Scrum TeamProduct Owner, Scrum Master and Development Team

Product OwnerT 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 MasterThe person responsible for the Scrum process, making sure it is used correctly and maximizing its benefits.

Development TeamA cross-functional group of people responsible for delivering potentially shippable increments of Product at the end of every Sprint.

Sprint burn down chartDaily progress for a Sprint over the sprint's length.

Release burn down chartSprint 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.

SprintA time period (typically 1–4 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.

SpikeA 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.

Terminologies

Waterfall VS Agile

Waterfall VS Agile