Scribd
Upload
4 views

Agile

The document discusses the Spiral Life-Cycle Model and Agile methods, emphasizing risk analysis, evaluation, and planning in software development. It highlights the Agile Manifesto's values and principles, aiming to reduce overheads and enhance responsiveness to change. Additionally, it details the Scrum framework, including roles and responsibilities, while addressing challenges and benefits of Agile methodologies.

Uploaded by

bartakeabhi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
4 views

Agile

The document discusses the Spiral Life-Cycle Model and Agile methods, emphasizing risk analysis, evaluation, and planning in software development. It highlights the Agile Manifesto's values and principles, aiming to reduce overheads and enhance responsiveness to change. Additionally, it details the Scrum framework, including roles and responsibilities, while addressing challenges and benefits of Agile methodologies.

Uploaded by

bartakeabhi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Agile Model

By: Dr. Sumit Dhariwal


Spiral Life-Cycle Model
• Precede each phase by
– Alternatives
– Risk analysis
• Follow each phase by
– Evaluation
– Planning of the next
phase

Radial dimension: cumulative


costs to date
Angular dimension: progress
through the spiral.
2
Spiral Life-Cycle Model (Cont.)
• Minimize risk via the use of prototypes and
other means.

• Two types of risk:


– Analyzable Risk: Time and cost
– Un-analyzable Risk:
• Personnel turnover
• Difference between small-scale and large-scale
software
• Evaluate the delivery promises of a hardware supplier

3
Spiral Life-Cycle Model (Cont.)
• Precede each phase by determining:
– Objective of the phase;
– Alternatives for achieving the objectives;
– Constraints imposed on those alternatives.

• Strategy is analyzed from the viewpoint of risk.


Attempts are made to resolve every potential risk.

• Follow each phase by:


– The results of the phase are evaluated.
– The next phase is planned.

4
Spiral Life-Cycle Mode (Cont.)
• Strengths
– The emphasis on alternatives and constraints
supports the reuse of existing software and the
incorporation of software quality as a specific
objective.
– There is essentially no distinction between
development and maintenance since maintenance
is another cycle of the spiral.

• Weaknesses
– For large-scale software only
– For internal (in-house) software only
5
Comparison of Life-Cycle Models
• Different life-cycle models have been
presented
– Each with its own strengths and weaknesses

• Criteria for deciding on a model include:


– The organization
– Its management
– The skills of the employees
– The nature of the product

• Best suggestion
– “Mix-and-match” life-cycle model
6
Agile methods
• Dissatisfaction with the overheads involved in software design
methods of the 1980s and 1990s led to the creation of agile
methods.
• The aim of agile methods is to reduce overheads in the
software process (e.g. by limiting documentation) and to be
able to respond quickly to changing requirements without
excessive rework.

Chapter 3 Agile software development 7


Agile Manifesto Values

• Individuals and Interactions over Processes and Tools


• Working Software over Comprehensive Documentation
• Customer Collaboration over Contract Negotiation
• Responding to Change over Following a Plan

8
Agile Manifesto Principles
▪ Satisfy Customer
▪ Welcome Changing Requirements
▪ Deliver Frequently
▪ Collaborate Daily
▪ Motivate Team
▪ Maximize Through Simplicity
▪ Promote Technical Excellence
▪ Deliver Working Software
▪ Promote Sustainable Development
▪ Promote Face-to-Face conversation
▪ Self Organized Team
▪ Reflect and Adjust Regularity
• Simplicity – Develop just enough to get the job done for right now.
• Self-organizing teams encourage great architectures, requirements, and
designs – Skilled and motivated team members who have decision-making
power, take ownership, communicate regularly with other team members,
and share ideas that deliver quality products.
• Regular reflections on how to become more effective – Self-improvement,
process improvement, advancing skills, and techniques help team
members work more efficiently.
Agile SDLC
Example
SCRUM

It is an Agile S/w development method for project management

Characteristics:
Prioritized work is done.
Completion of backlog items
Progress is explained

Problems with agile methods


It can be difficult to keep the interest of customers who are involved in the
process.
Team members may be unsuited to the intense involvement that characterizes
agile methods.
Prioritizing changes can be difficult where there are multiple stakeholders.
Maintaining simplicity requires extra work.
Contracts may be a problem as with other approaches to iterative development.
Chapter 3 Agile software development 13
Scrum is an agile process that allows us to focus on
delivering the highest business value in the shortest time.
It allows us to rapidly and repeatedly inspect actual working
software (every two weeks to one month).
The business sets the priorities. Our teams self-manage to
determine the best way to deliver the highest priority
features.
Every two weeks to a month anyone can see real working
software and decide to release it as is or continue to
enhance for another iteration.
The Scrum process

Chapter 3 Agile software development 15


Scrum benefits

• The product is broken down into a set of manageable and understandable


chunks.
• Unstable requirements do not hold up progress.
• The whole team have visibility of everything and consequently team
communication is improved.
• Customers see on-time delivery of increments and gain feedback on how
the product works.
• Trust between customers and developers is established and a positive
culture is created in which everyone expects the project to succeed.

Chapter 3 Agile software development 16


Scaling agile methods

• Agile methods have proved to be successful for small and


medium sized projects that can be developed by a small co-
located team.

Chapter 3 Agile software development 17


Scrum Framework Continued..
• Team Role Product Owner
Scrum Master
Development Team
Product Owner
• The Product Owner is responsible for managing the Product Backlog,
accountable for the delivery of shippable item that adds value to
the business.

• Product Owner responsibilities-


– Create Product Vision
– Collaborate with Team and Stakeholders
– Participates in Scrum ceremonies
– Prepare and manage Product Backlog by maximizing business
value and value based prioritization
– Drive Product Development
– Being available for development team
– Manage and influence Release
•
Scrum Master
The Scrum Master plays unique role of servant-leader for the Scrum
Team.

• The Scrum Master responsibilities-


– Manages scrum team,
– Remove impediments for the scrum team,
– Implement scrum framework
– Push the change in support of scrum in the organization.
– Guide and coach the scrum team
– Protect team and drive team success
– Keep track of sprint progress and goal

▪ Scrum Master Service to Product Owner


▪ Scrum Master Service to Development Team
▪ Scrum Master Service to the Organization

You might also like