agile basics2 software engineering development

agile

1. AGILE METHODOLOGY
PRESENTED TO:
MR. MANESSH KUMAR
MRS. DEEPTI GUPTA
PRESENTED BY:
MOHIT KUMAR
1313310092
CSE
3/2/2016 1

2. Contents of the table
Definition
Manifesto
Principles
Characteristics
Overview
Philosophy
Agile methods
Agile practices
Experience and Adoption
Pitfalls
Criticism
Application outside software development
3/2/2016 2

3. What is Agile software development?
Agilesoftwaredevelopmentisaset
of principlesfor software
developmentinwhichrequirements
andsolutionsevolvethrough
collaboration between self-
organizing,cross-functionalteams.
3/2/2016 3

4. Agile Manifesto
Individualsandinteractions:self-organizationand
motivationareimportant,asareinteractionslikeco-
locationandpairprogramming.
Workingsoftware:workingsoftwareismoreusefuland
welcomethanjustpresentingdocumentstoclientsin
meetings.
Customercollaboration:requirementscannotbefully
collectedatthebeginningofthesoftwaredevelopment
cycle,thereforecontinuouscustomerorstakeholder
involvementisveryimportant.
Respondingtochange:agilemethodsarefocusedonquick
responsestochangeandcontinuousdevelopment.
3/2/2016 4

5. Principles
TheAgileManifestoisbasedontwelve
principles:
Customersatisfactionbyearlyandcontinuousdeliveryof
valuablesoftware
Welcomechangingrequirements,eveninlatedevelopment
Workingsoftwareisdeliveredfrequently(weeksrather
thanmonths)
Close,dailycooperationbetweenbusinesspeopleand
developers
Projectsarebuiltaroundmotivatedindividuals,who
shouldbetrusted.
3/2/2016 5

6. Principle continued..
Face-to-faceconversationisthebestformofcommunication
(co-location)
Workingsoftwareistheprincipalmeasureofprogress
Sustainabledevelopment,abletomaintainaconstantpace
Continuousattentiontotechnicalexcellenceandgooddesign
Simplicity—theartofmaximizingtheamountofworknot
done—isessential
Bestarchitectures,requirements,anddesignsemergefromself-
organizingteams
Regularly,theteamreflectsonhowtobecomemoreeffective,
andadjustsaccordingly
3/2/2016 6

7. Characteristics of Agile Software
Development
--Light Weighted methodology
--Small to medium sized teams
--vague and/or changing requirements
--vague and/or changing techniques
--Simple design
--Minimal system into production
3/2/2016 7

8. Overview
Therearemanyspecificagile
developmentmethods.Most
promotedevelopment,teamwork,
collaboration,and process
adaptabilitythroughoutthelife-
cycleoftheproject.
3/2/2016 8

9. Philosophy
Comparedtotraditionalsoftwareengineering,
agilesoftwaredevelopmentmainlytargets
complexsystemsandprojectswithdynamic,non-
deterministicandnon-linearcharacteristics,
whereaccurateestimates,stableplans,and
predictionsareoftenhardtogetinearlystages—
andbigup-frontdesignsandarrangementswould
probablycausealotofwaste,i.e.,arenot
economicallysound.
3/2/2016 9

10. Adaptive vs. predictive
Agilemethodslieontheadaptivesideofthis
continuum.Onekeyofadaptivedevelopment
methodsisa"RollingWave"approachtoschedule
planning,whichidentifiesmilestonesbutleaves
flexibilityinthepathtoreachthem,andalso
allowsforthemilestonesthemselvestochange.
Adaptivemethodsfocusonadaptingquicklyto
changingrealities.Whentheneedsofaproject
change,anadaptiveteamchangesaswell.
3/2/2016 10

11. Predictive
Predictivemethods,focusonanalysingandplanning
thefutureindetailandcaterforknownrisks.
Intheextremes,apredictiveteamcanreportexactly
whatfeaturesandtasksareplannedfortheentire
lengthofthedevelopmentprocess.
Predictivemethodsrelyoneffectiveearlyphase
analysisandifthisgoesverywrong,theprojectmay
havedifficultychangingdirection.
Predictiveteamsofteninstituteachangecontrol
boardtoensuretheyconsideronlythemostvaluable
changes.
3/2/2016 11

12. Iterative vsWaterfall
Inthewaterfallmodelthereisalwaysaseparate
testingphaseafterabuildphase.
However,inagiledevelopmenttestingisusuallydone
concurrentlywith,oratleastinthesameiterationas,
programming.
Becausetestingisdoneineveryiteration—which
developsasmallpieceofthesoftware—userscan
frequentlyusethosenewpiecesofsoftwareand
validatethevalue.
3/2/2016 12

23. 3/2/2016 23

24. 3/2/2016 24

25. 3/2/2016 25

26. 3/2/2016 26

27. 3/2/2016 27

28. Agile Method
Adaptive software development(ASD)
Agile modeling
Agile Unified Process(AUP)
Business analyst designer method (BADM)
Crystal Clear Methods
Disciplined agile delivery
Dynamic systems development method(DSDM)
Extreme programming(XP)
Feature-driven development(FDD)
Lean software development
3/2/2016 28

29. 3/2/2016 29

30. Agile Practices
Acceptance test-driven development(ATDD)
Agile modeling
Backlogs(Product and Sprint)
Behavior-driven development(BDD)
Cross-functional team
Continuous integration(CI)
Domain-driven design(DDD)
Pair programming
Planning poker
Refactoring
3/2/2016 30

31. Experience and Adoption
Agilemethodswerefirstusedbytechnologyearly
adopterssuchasTektronix.
Agilecanbeusedwithanyprogrammingparadigmor
languageinpracticeAgilehasusuallybeenclosely
associatedwithobject-orientedenvironmentssuchas
SmalltalkandLispandlaterJava.
TheinitialadoptersofAgilemethodswereusually
smalltomedium-sizedteamsworkingon
unprecedentedsystemswithrequirementsthatwere
difficulttofinalizeandlikelytochangeasthesystem
wasbeingdeveloped.
3/2/2016 31

32. Common Pitfalls
Lack of overall project design
Adding stories to a sprint in progress
Lack of sponsor support
Insufficient training
Product owner role is not properly filled
Excessive preparation/planning
Lacking test automation
3/2/2016 32

33. Criticism
Theagilemovementisinsomewaysabitlikea
teenager:veryself-conscious,checkingconstantly
itsappearanceinamirror,acceptingfewcriticisms,
onlyinterestedinbeingwithitspeers,rejectingen
blocallwisdomfromthepast,justbecauseitis
fromthepast,adoptingfadsandnewjargon,at
timescockyandarrogant.ButIhavenodoubts
thatitwillmaturefurther,becomemoreopento
theoutsideworld,morereflective,andalso
thereforemoreeffective.
3/2/2016 33

34. Aplicationsoutside s/w development
Integratedcustomerengagement-toembed
customerswithinanydeliveryprocesstoshare
accountabilityforproduct/servicedelivery.
Facilitation-basedmanagement-adoptingagile
managementmodels,liketheroleofScrum
Mastertofacilitatetheday-to-dayoperationof
teams.
Anenablingorganisationalstructure-withafocus
onstaffengagement,personalautonomyand
outcomesbasedgovernance.
3/2/2016 34

35. THANKS
3/2/2016 35