SDLC - Part 2

Business Analysis
Training
SDLC in Detail

Classification: Restricted
Agenda
• Incremental Approach
• Iterative Approach
• Agile-Scrum

Incremental Approach

Incremental Approach
• The incremental model is essentially a series of waterfall cycles.
• The requirements are known at the beginning of the project and are
divided into groups for incremental development.
• A core set of functions is identified in the first cycle and is built and
deployed as the first release.
• The software development cycle is repeated, with each release adding
more functionality until all requirements are met.
• Each development cycle acts as the maintenance phase for the previous
software release.
• While new requirements that are discovered during the development of a
given cycle can be implemented in subsequent cycles, this model assumes
that most requirements are known up front.
• A modification to the incremental model allows development cycles to
overlap. That is, a subsequent cycle may begin before the previous cycle is
complete.

Example of Incremental Approach
Incremental development is a staging and scheduling strategy in which
various parts of the system are developed at different rates, and integrated
as they are completed.

Incremental Approach - Advantages
• Generates working software quickly and early during the software life
cycle.
• This model is more flexible – less costly to change scope and requirements.
• It is easier to test and debug during a smaller iteration.
• In this model customer can respond to each built.
• Lowers initial delivery cost.
• Easier to manage risk because risky pieces are identified and handled
during it’d iteration.

Incremental Approach - Disadvantages
• Needs good planning and design. The majority of requirements must be
known in the beginning.
• Needs a clear and complete definition of the whole system before it can
be broken down and built incrementally.
• Total cost is higher than waterfall.

When to Use Incremental Approach
• The incremental model is good for projects where requirements are
known at the beginning, but which need functionality early in the project
or which can benefit from the feedback of earlier cycles.
• Because each cycle produces a working system, it may also be
advantageous for projects whose continued funding is not assured and
may be cut at any time.
• It is best used on low to medium-risk programs.
• If the risks are too high to build a successful system using a single waterfall
cycle, spreading the development out over multiple cycles may lower the
risks to a more manageable level.

Iterative Approach
• Iterative development is best defined in terms of its processes that allow
for dynamic development rather than any single defined method or
approach.

Iterative Approach
Definition
Iterative approach or development is a process that grows a system feature
by feature during self-contained cycles of analysis, design, development and
testing that end in the production of a stable, fully integrated and tested,
partially complete system that incorporates all of the features of all previous
iterations.

Example of Iterative Approach
Iterative development is a rework scheduling strategy in which time is set
aside to revise and improve parts of the system.

Iterative Approach
• Iteration comes from word Iterative means repetitious.
• Iteration means the act of repeating a process usually with the aim of
approaching a desired goal or target or result. Each repetition of the
process is also called an "iteration," and the results of one iteration are
used as the starting point for the next iteration.
• In software development, An iteration is made up of a series of activities
that include conducting needs analysis, developing parts of the system,
then deploying and testing them. In the end, one or more functionalities
are ready for integration into the final product.

Iterative Approach - Advantages
• More adaptable to changes.
• Allows for early detection of risks associated with a given project
• QA can be performed at the end of each iteration.
• Project managers are in a better position to assess the impact of changes
on the delivery dates.
• Early visible progress.
• A continuous improvement methodology.
• Corrective actions can be taken at the end of each iteration.

Iterative Approach - Disadvantages
• It is difficult to freeze requirements, and they may continue to change in
later iterations because of increasing customer demands. As a result,
more iterations may be added to the project, leading to project delays
and cost overruns.
• The project requires a very efficient change control mechanism to
manage changes made to the system during each iteration.
• More time spent in review and analysis
• A lot of steps that need to be followed in this model
• Delay in one phase can have detrimental effect on the software as a
whole

When to Use Iterative Approach
•Requirements of the complete system are clearly defined and understood.
•When the project is big.

Difference between Incremental and Iterative
Incremental development is a staging and scheduling strategy in which
various parts of the system are developed at different rates, and integrated
as they are completed.
Iterative development is a rework scheduling strategy in which time is set
aside to revise and improve parts of the system.

Agile Methodology

Agile Approach

What is Agile
 Processes and techniques for incremental and iterative software
development
 Agile Manifesto
 – “We are uncovering better ways of developing software by doing it
and helping others do it. Through this work we have come to value”:
 Individuals and interactions over processes and tools
 Working software over comprehensive documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan

What does the Agile Manifesto Mean?

Principles of Agile

Principles of Agile (2)

Central: Incremental and Iterative
Development

Agile Methods

Scrum Lifecycle
 Planning
–Vision, expectations, funding
 Staging
– Identify requirements, prioritize iteration
 Development
– Implement system ready for release in each sprint
 Release
–Operational deployment

Development team
product owner
scrum master
SCRUM team

Agile Methods – Scrum (1)

Scrum Roles and Process

Scrum Ceremonies
1.SPRINT PLANNING
(Discuss top PBI scope>estimate)
2. Daily stand up meeting
(<15 minutes, what I did till this meeting, what ill do till next meeting ,
what's blocking me)
3. Sprint review (last day)
(To demonstrate what is ready to ship to po, no ppt, demo on prodn
env
4. Sprint retrospective –
what went right, what went wrong

Product Backlog
PBIs are Uniquely ranked items, progressive
user stories are short plain language of description of functionality in
terms of customer benefit/need
Stories (=requirement) priority estima
te
As a user I want to be able to easily install
the application so that I can access my
bank account on my mobile
1 5
As a user I want to be able to view my bank
transaction history so that I can track my
transactions
2 3

Commitment
– Team takes responsibility to complete the Sprint. To avoid things that
will stand in its way
Focus
– Team’s focus is maintained. Distractions, interruptions are fielded
Openness
– Overall and individual status and commitments kept open.
Respect
– Team responsibility rather than scapegoat.
Courage
– Management and team have the courage to take responsibility to do
what is necessary

Thank you

SDLC - Part 2

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Similar to SDLC - Part 2

Similar to SDLC - Part 2 (20)

More from Lakshmi-BA

More from Lakshmi-BA (15)

Recently uploaded

Recently uploaded (20)

SDLC - Part 2