What is Agile?

Agile is a conceptual framework for software development which promotes

development iterations throughout the life-cycle of the project.
Agile methods have two main units of delivery: Releases and Iterations.
A release consists of several iterations each of which is like a micro-project of its
own. !eatures defects enhancement re"uests and other work items are
organi#ed estimated and prioriti#ed then assigned to a release.
Within a release these work items are then assigned $y priority to iterations.
%ach iteration is an entire software project: including planning re"uirements
analysis design coding testing and documentation.
Agile methods also emphasi#e working software as the primary measure of
progress.
Agile methods are also called &adaptive& methods which implies that when the
needs of a project change an adaptive team changes as well.
'he result of each iteration is working tested accepted software and associated
work items.
Agile (ethodologies:
'he various agile methodologies share much of the same philosophy
however from an implementation standpoint each has its own recipe
of practices terminology and tactics.
)crum is one of the agile methodologies used in the software
development.
*ver the last couple of years in particular )crum has garnered
increasing popularity in the software community due to its
simplicity proven productivity.
What is )crum?
+y ,efinition )crum is an agile lightweight process that can $e used
to manage and control software and product development using
iterative incremental practices.
In more )impler words )crum is a general set of guidelines that
govern the development process of a product from its design stages
to its completion.
'he product is developed in a series of --to-.-week iterations or
)prints.
)/R0( 1rocess ena$les the creation of self-organi#ing agile teams.
)crum 1rocess:
'he scrum process has 2 main phases.
Planning: - All the features defects Issues /ustomer Re"uests and any
other enhancements are reviewed during the planning phase. Work to
$e done over the life of a project is summed up in a 1roduct +acklog.
'he 1roduct +acklog contains a list of features needed for the project3
this is the $ig picture for the project.
Sprint Cycle: - 'he sprint cycle is an iterative cycle of a$out 2-. weeks in
which the actual development of the product is done.
Closure: - In this phase the product4s development is $rought to a close
and the product is released.
)print /ycle:
)print /ycle:
)print 1lanning (eeting: - A meeting at the $eginning of a sprint where
the sprint is planned. Items from the 1roduct +acklog are selected to $e
completed in the sprint $ased on the priorities set $y the 1roduct
*wner.
Sprint Backlog: - )print +acklog is decided which lists the items that will
$e completed in the current sprint taken from the product $acklog.
SCRUM Master: - 'he team4s leader is called the )crum (aster. 5e should
$e one of the mem$ers of the working team - that is he should $e one of
the people who is actually doing the work on the project. 'he )/R0(
(aster measures progress removes impediments and leads the team
meetings.
Sprint Review Meeting: - A sprint is closed with a )print Review (eeting
similar to a postmortem meeting at the end of other traditional projects
where the progress made in the last sprint is demonstrated the sprint is
reviewed and the team gets together to evaluate what worked well and
what needs to $e improved during their ne6t iteration.
/omparison $etween Waterfall (odel
and )/R0( testing.
Waterfall (odel
1redictive (odel
!ocused on planning in detail with re"uirements capture analysis
design coding and testing in a strict pre-planned se"uence
0nsuita$le if re"uirements are likely to change.
Iterations are e6pensive
,ifficulty in changing the direction from the planned one.
)/R0( 'esting
Adaptive (odel
!ocused on developing completely developed and tested features
7very small su$set of whole8 every few weeks.
)uita$le if project needs change with changing realities.
Iterations follow waterfall cycle
%asy to adapt as per changing needs
)/R0( 1rocess and 9A
Agile and )crum are really changing the way testing is perceived
throughout the project. 'esting is not a phase at the end3 it really is
integrated throughout the entire iteration cycle and it goes hand in
hand with programming tasks.
!ew things a 9A professional should e6pect when an organi#ation
adopts Agile:)crum development techni"ues:
+etter communication and more colla$oration among 9A ;
development
A new <peer to peer= relationship $etween development and 9A
personnel
>ooking for ways to optimi#e testing efforts will $e a <must=
'est within each iteration rather than at the end of a development
lifecycle
,ecide what to test when a product is still unfinished
/olla$orate with team mem$ers rather than working in isolation
1articipate in daily status meetings that are a ma6imum of -?
minutes long
Agile 'esting
What is Agile 'esting?
Agile as the name refers implies something to o very !uickly" #ence Agile $esting refers
to validate the client re"uirements as soon as possi$le an make it customer frienly"
As soon as the %uil is out& testing is e'pecte to get starte an report the %ugs !uickly if
any foun" As a $ester& you nee to provie your thoughts on the client re!uirements
rather than (ust %eing the auience at the other en" )mphasis has to %e lai own on the
!uality of the elivera%le in spite of short timeframe which will further help in reucing
the cost of evelopment an your fee%acks will %e implemente in the coe which will
avoi the efects coming from the en user"
Agile testing is used whenever customer re"uirements are changing dynamically
*f we have no SRS& BRS %ut we have test cases oes you e'ecute the test cases %linly or
o you follow any other process"
$est case woul have etail steps of what the application is suppose to o"
+, -unctionality of application"
., *n aition you can refer to Backen& is mean look into the /ata%ase" $o gain more
knowlege of the application"
Advantages offered $y Agile (ethodology:
+" saving of time and money
." $his approach leas to focus more on the application rather than documenting
the things"
0" $his approaches that in case there is any Change re!uest or enhancements come in
%etween any phase& it can %e implemente without any %uget constraint"
1" All phases of S/2C nee to %e complete very !uickly3 there is a transparency to
each iniviual working on the pro(ect with the status of each phase"
4" /aily meetings an iscussions for the pro(ect following Agile approach can help
to etermine the issues well in avance an work on it accoringly"
5" 6uick coing an $esting makes the management aware of the gaps e'isting in
either re!uirements or technology use an can try to fin the workaroun for the
same"
7" Corresponing fee%ack will %e taken from user an will work on it on the other
han"
8888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888
$he wor 9Agile: itself goes with the meaning 9move !uickly: an so the testing" *n
agile testing& no conventional testing practices are applica%le to wait until the entire
evelopment cycle activities are complete& whereas the testing is closely intact with the
evelopment an is one in parallel as an when a piece of coe is evelope"
Agile $esting has %een an evolving methoology we;ve %een seeing over the last few
years" $he popularity of this methoology can %e accreite to several reasons such as the
prouct evelopment lifecycles an <o to market cycles =<$M, are shrinking in the light
of ever changing %usiness ynamics"
)veryone wants to put the prouct out in the market as soon as possi%le capturing the
customer share as soon as possi%le to gain control on the changing %usiness ynamics"
Agility& it seems is paying iviens for such short <$Ms an proviing a !uick R>*"
Some of the principles %ehin the Agile $esting ?Reference: Agile Manifesto@ are:
Customer satisfaction %y rapi agile scrum =sprint, process& continuous elivery
of useful software
Aorking software is elivere fre!uently =weeks rather than months,
Aorking software is the principal measure of progress
)ven late changes in $esting Re!uirements are welcome
Close& aily cooperation %etween %usiness people an evelopers
-ace-to-face conversation is the %est form of communication
Pro(ects are %uilt aroun motivate iniviuals& who shoul %e truste
Continuous attention to technical e'cellence an goo esign
Simplicity
Self-organiBing teams
Regular aaptation to changing circumstances
http:88www"techgig"com8we%inars8Software-$esting-in-Agile-Methoology-+51