Software

Dr B Veera Jyothi
Assistant
Professor
Engineering CBIT, Hyderabad
The Manifesto for
Agile Software Development

 “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
 That is, while there is value in the items on the right,
we value the items on the left more.” Kent Beck et al
What is “Agility”?

 Effective (rapid and adaptive) response to

change
 Effective communication among all stakeholders
 Drawing the customer onto the team
 Organizing a team so that it is in control of the
work performed
Yielding …
 Rapid, incremental delivery of software
Agility and the Cost of Change
An Agile Process

 Is driven by customer descriptions of what is

required (scenarios)
 Recognizes that plans are short-lived
 Develops software iteratively with a heavy
emphasis on construction activities
 Delivers multiple ‘software increments’
 Adapts as changes occur
 Agility Principles - I

1. Our highest priority is to satisfy the customer through early and

continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive
advantage.
3. Deliver working software frequently, from a couple of weeks to a
couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily
throughout the project.
5. Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the job
done.
6. The most efficient and effective method of conveying information
to and within a development team is face–to–face conversation .
Agility Principles - I

7. Working software is the primary measure of progress.

8. Agile processes promote sustainable development. The
sponsors, developers, and users should be able to maintain a
constant pace indefinitely.
9. Continuous attention to technical excellence and good
design enhances agility.
10. Simplicity – the art of maximizing the amount of work not
done – is essential.
11. The best architectures, requirements, and designs emerge
from self–organizing teams.
12. At regular intervals, the team reflects on how to become
more effective, then tunes and adjusts its behavior accordingly .
Human Factors

 The process molds to the needs of the people

and team, not the other way around
 key traits must exist among the people on
an agile team and the team itself:
 Competence.
 Common focus.
 Collaboration.
 Decision-making ability.
 Fuzzy problem-solving ability.
 Mutual trust and respect.
 Self-organization
Extreme Programming (XP)

• The most widely used agile process, originally

proposed by Kent Beck
• XP Planning
• Begins with the creation of “user stories”
• Agile team assesses each story and assigns a cost
• Stories are grouped to for a deliverable increment
• A commitment is made on delivery date
• After the first increment “project velocity” is used
to help define subsequent delivery dates for other
increments
Extreme Programming (XP)
Adaptive Software Development

Originally proposed by Jim Highsmith

ASD — distinguishing features
 Mission-driven planning
 Component-based focus
 Uses “time-boxing” (See Chapter 24)
 Explicit consideration of risks
 Emphasizes collaboration for requirements
gathering
 Emphasizes “learning” throughout the process
Adaptive Software Development

Originally proposed by Jim Highsmith

ASD — distinguishing features
 Mission-driven planning
 Component-based focus
 Uses “time-boxing” (See Chapter 24)
 Explicit consideration of risks
 Emphasizes collaboration for requirements gathering
 Emphasizes “learning” throughout the process
Adaptive Software Development

ad ap t ive cycle p lanning Req uirement s g at hering

uses m issio n st at em e nt JAD
pro je ct co nst raint s m ini-sp ecs
b asic re quirem e nt s
t ime-b o xed rele ase p lan

Release
s o ft wa re in cre m e n t
ad ju s t m e nt s f or s ub s e qu e nt cy cle s
co mp o nent s imp lement ed / t est ed
f o cus g ro up s f o r f eed b ack
f o rm al t echnical review s
p o st mo rt ems
Dynamic Systems Development
Method

• Promoted by the DSDM Consortium (

www.dsdm.org )
• DSDM—distinguishing features
• Similar in most respects to XP and/or ASD
• Nine guiding principles
• Active user involvement is imperative.
• DSDM teams must be eThe focus is on frequent delivery
of products.
• Fitness for business purpose is the essential criterion for
acceptance of deliverables.
Dynamic Systems Development
Method
• Iterative and incremental development is necessary to
converge on an accurate business solution.
• All changes during development are reversible.
• Requirements are baselined at a high level
• Testing is integrated throughout the life-cycle.
• mpowered to make decisions.
Dynamic Systems Development
Method
Scrum

 Originally proposed by Schwaber and Beedle

 Scrum—distinguishing features
 Development work is partitioned into “packets”
 Testing and documentation are on-going as the product
is constructed
 Work occurs in “sprints” and is derived from a
“backlog” of existing requirements
 Meetings are very short and sometimes conducted
without chairs
 “demos” are delivered to the customer with the time-
box allocated
Scrum
Crystal

• Proposed by Cockburn and Highsmith

• Crystal—distinguishing features
• Actually a family of process models that allow
“maneuverability” based on problem
characteristics
• Face-to-face communication is emphasized
• Suggests the use of “reflection workshops” to
review the work habits of the team
Feature Driven Development
• Originally proposed by Peter Coad et al
• FDD—distinguishing features
• Emphasis is on defining “features”
• A feature “is a client-valued function that can be implemented in two
weeks or less.”
• Uses a featur<action> the <result> <by | for | of | to> a(n) <object>
• A features list is created and “plan by feature” is conducted
• Design and construction merge in FDD
Feature Driven Development

Reprinted with permission of Peter Coad

Agile Modeling

• Originally proposed by Scott Ambler

• Suggests a set of agile modeling principles
• Model with a purpose
• Use multiple models
• Travel light
• Content is more important than representation
• Know the models and the tools you use to
create them
• Adapt locally
ANY QUESTIONS
 THANK YOU
STAY HOME
STAY SAFE
KEEP LEARING