8/18/2019 Striking the Balance Waterfall and Agile

1/2

Striking the Balance: Waterfall and Agile - Part 1, posted onSeptember 13, 2013 b Amol Patki

!oda, companies ha"e a plethora of choices s#ch as S$%&', ()treme Programming *+P, Beha"ior ri"en e"elopment *B, .eat#re ri"en e"elopment *., /ean and anban softarede"elopment methods #nder the #mbrella of agile along ith e)iting aterfall method for proectimplementation $ompanies can select the best combination of s#itable methodologies to ma)imi4eb#siness "al#e for the c#stomer

5n this blog series, e ill disc#ss "ario#s methodolog selection aspects across dimensions s#ch asb#siness6 application, location and teams, tools and also e)plore best-practices in both methodologies tobalance agilit ith discipline and control

!his blog e ill be disc#ssing abo#t methodolog selection pointers aro#nd b#siness and applicationrelated dimension

5t is important that, methodolog goals are aligned ith proect goals Proects are more s#itable for agilede"elopment hen the primar proect goals are rapid "al#e deli"er and responsi"eness to changeWaterfall ill the right approach for proects that demand higher predictabilit, stabilit 7 ass#rance

Proects that co"er significant enhancements, entirel ne de"elopment or initial prototping of a neconcept in t#rb#lent, dnamicall changing en"ironments8 here re9#irements are emergent agileadoption is more s#itable as it red#ces risk significantl Waterfall is more #sef#l in proects herestakeholders desire to ha"e rigoro#s man#al and e)plorator testing, there is need to integrate se"eralindependentl e"ol"ed applications, improperl mod#lari4ed large e)isting sstem is replacingincrementall

 Agile initiall started ith small to medi#m teams of people orking on relati"el small applications d#e totight coordination and shared tacit knoledge constraints ;oe"er, recentl, man large scale programs

ha"e doc#mented s#ccessf#l deli"er of agile transformation b #se of scaling options a"ailable likeisciplined Agile eli"er *A, Scr#m of Scr#ms *S

8/18/2019 Striking the Balance Waterfall and Agile

2/2

ha"e to be doc#mented in detail s#ch that the designers can acc#ratel and proacti"el predict flas Also, s#fficient n#mber of reso#rces has to be allocated for elaborate doc#mentation to keep #p ith thegoals of predictabilit, stabilit and ass#rance thro#gh standardi4ation and process capabilit

 Agile and aterfall are not e)cl#si"e, b#t there has been considerable polari4ation associated ith bothapproaches and m#ch of these differences are rooted more in perception and misconceptions rather thanin realit 5n man cases, the manner in hich companies appl their #dgment and skills in #sing themethodolog has a higher impact than the methodolog itself

5n the ne)t post, 5 ill disc#ss abo#t ho /ocation and !eam dimension impacts methodolog selectionconsiderations for aterfall and agile

http:66infossblogscom6application-ser"ices620136126striking>the>balance>aterfall>Part2html

 

References:

1 Balancing Agilit and iscipline: A ?#ide for the Perple)ed  B Barr Boehm, %ichard !#rner 2 Agile Proect 'anagement ith Scr#m en Schaber 'icrosoft Press, 2003

http://www.infosysblogs.com/application-services/2013/12/striking_the_balance_waterfall_Part2.htmlhttp://www.infosysblogs.com/application-services/2013/12/striking_the_balance_waterfall_Part2.html