Agile View of Process

Why Agility
Agility Principles
Xp
 Why Agility
Effective response to change
Effective communication among all
stakeholders
Drawing the customer onto the team;
eliminate the us and them attitude
Organizing a team so that it is in
control of the work performed
Rapid, incremental delivery of
software
 Agile Principles
satisfy the customer
Welcome changing
Deliver working software frequently
Business people and developers must work
together daily throughout the project.
Build projects around motivated individuals. Give
them the environment and support they need, and
trust them to get the job done.
facetoface conversation.
Simplicity
selforganizing
Agile Process Models
Extreme
Dynamic Programming
System
Development
Method

Adaptive
Software
Development
Feature Driven
Development
XP Extreme Programming
 XP Phases
It uses an object-oriented approach.
XP Planning-
listening, leads to creation of user stories
that describes required output, features, and
functionality.
Agile team assesses each story and assigns a
cost (development weeks. If more than 3
weeks, customer asked to split into smaller
stories)
grouped for a deliverable increment next
release
 XP Design-
KIS principle (keep it simple) Nothing
more nothing less than the story
use of CRC (class-responsibility-
collaborator) cards in an object-oriented
context.
spike solutionsa design prototype for
that portion is implemented and
evaluated.
refactoringan iterative refinement of
the internal program design.
 XP
XP Coding-
Recommends the construction of a unit test
Encourages pair programming. Two people
work together at one workstation.
XP Testing-
All unit tests are executed daily and ideally
should be automated
Acceptance tests are defined by the
customer and executed to assess customer
visible functionality
Adaptive Software
Development
 ASD Phases
Speculation-
project is initiated and adaptive cycle
planning is conducted as per customers
constraints like (Delivery date).
Collaboration-
Communication
Assist each other
Work hard
Pair Programming
 ASD
Learning
software developers often overestimate
their own understanding of the
technology, the process, and the project
and that learning will help them to
improve their level of real
understanding.
Three ways: focus groups, technical
reviews and project postmortems.
 T1 topics
Introduction to software engg
Generic view of process
Process Models
Agility model (basic)
Agile view of process
principles
XP,ASD
Requirement Engineering
Functional, nonfunctional, tasks, eliciting requirements
Building Analysis Model
 T1 format
14 marks Objectives
6 marks subjective