Comedy 

SystemDesign Agile Vs Waterfall

$23.20

Agile Software Development with Scrum (Series in Agile Software Development)

From Amazon

Sales Rank 83551 Schwaber, Ken/ Beedle, Mike

eXtreme Programming is an ideal many software shops would love…
Buy now

Language:
hello everyone my name is Vimala VenkatAysen today I'm going to be presentingsystem analysis and design our childversus waterfall methodologiesin this presentation I'll be goingthrough introduction to system analysisand designhdl-c the system development lifecyclewaterfall methodology its advantages anddisadvantages agile methodology itsadvantages and disadvantages and alsothe differences between waterfallmethodology versus agile and at the endwe will also look into which one to gowith in our system development projectsso let's get into the details systemanalysis and design deals with planningthe development of information systemsthrough understanding and specifying indetail what a system should do and howthe components of the system should beimplemented and work together so whendeveloping systems most of theorganizations use a standard of stepscalled the systems development lifecycle SDLCas the common methodology for systemsdevelopment ste LC is a process forplanning creating testing and deployingan information system it aims to producehigh quality systems that meet or exceedcustomer expectations so this isachieved by delivering systems whichmove through each and every clearlydefined phase and also within scheduledtime frames and cost estimates as youcan see from here the phases areplanning analysis design developmentimplementation and maintenance so why doorganizations have to go through allthese computer systems are complex andoften are integrated with multipletraditional systems supplied bydifference of where vendors so in aneffort to improve the systems analysisand design processes differentapproaches and methodologies have beendeveloped so a number of SDLCmethodologies have been created tomanage the complex computer systems someof them are waterfall agile rapidprototyping eye trait of an incrementallean spiral and devops in the next fewslides we will look into agile andwaterfall methodologies in detailwhatever methodology follows asequential linear process and is themost popular version of the systemsdevelopment lifecycle for softwareengineering and IT projects so if yousee the image here progress is seen asflowing steadily downwards like awaterfall through the phases of softwareimplementation this means that any phasein the development process begins onlyif the previous phases complete and alsothe waterfall approach doesn't definethe process to go back to the previousphase to handle any changes in therequirement it is the earliest approachand most widely known that was used forsoftware development at the completionof each and every phase a milestone hasbeen reached and a document is producedto be approved by the stakeholdersbefore moving on to the next activity orphase let's look at advantages ofwaterfall methodology waterfall is bestused for simple and unchanging projectsit's easy to use and manage because thewaterfall model follows the samesequential pattern for each project itis easy to use and understand the teamdoesn't need any prior knowledge ortraining before working on a waterfallproject it is also a rigid model eachphase are specific deliverablesinterview so it's easy to manage andcontrol discipline is enforced everyphase in waterfall has a start and endpoint and it's easy to share progress ofits stakeholders and customers and alsoby focusing on requirements and designbefore writing code the team canunderstand and reduce the discovermissed deadlines it requires awell-documented approach whateverrequires documentation for every phaseresulting in better understanding of thelogic behind the code and test it alsoleaves a paper trail for any futureprojects or if stakeholders need to seemore detail about a certain phasedisadvantages of waterfall methodologychanges can't be easily accommodated soonce the team completes a phase theycan't go back if they reach the testingphase and realize that the future wasmissing from the requirements phase itis very difficult and expensive to goback and fix it software is in theuntil later the project has to completetwo to four phases before the codingactually begins as a result stakeholdersdon't see any working software untillate in the lifecycle gathering accuraterequirements can be challenging one ofthe first phases in a waterful projectis to talk to customers and stakeholdersand identify the requirements so howeverit can be difficult to pinpoint exactlywhat they want this early in the projectoftentimes our customers don't know whatexactly they want early on and insteadlearn identify requirements as a projectpromiseslet's look at what is agile methodologya journal is a time boxed I try toapproach to software delivery that pillsoftware incrementally from the start ofthe project instead of trying to deliverit all at oncenear the end this is exactly opposite tothe waterfall approach let's look at itin the next slide in the waterfallapproach you go through each phase likedefine build release in a longer cycleonly after all this is complete thecustomer sees the final producthowever in agile it is time boxed so youhave shorter cycles and you keep addingfeatures to every cycle so the customerget to see the product at each and everycycle how do we follow agile methodologyin our projects sit with the customermake a list of features the customerwant called user stories so we basicallybreak down the project project intolittle bits of user functionality calleduser stories estimate the user storyfollowing the agile estimation techniqueprioritize them and then continuouslydeliver them short two-week cyclescalled iterations so then as you andyour customers start delivering one ofthe two things is going to happen you'lldiscover that you're going fast enoughall is good are you have too much to doand not enough time so at this point youhave two choices you can either do lessand cut scope which is recommended oryou can push out the date and ask formore money so you update the plan as yougoadvantages of agile changes embracedsince its shard of planning cycles it'seasy to accommodate and accept changesat any time during the project there isalways an opportunity to refine andReaper it as the black backlog hittingteams introduced changes to the projectin a matter of weeksn gold can be unknown a child is verybeneficial for projects where the endgoal is not clearly defined as theproject progresses the goals will cometo light and development can easilyadapt to these evolving requirementsfaster high quality delivery breakingdown the project into iterations allowsthe team to focus on high qualitydevelopment testing and collaboration soinstructing is conducted during eachhydration the defects get identified andsolved more quickly and this highquality software can be delivered fasterwith consistent successive iterationsstrong team interaction as wellhighlights the importance of frequentcommunication and face-to-faceinteractionsteams work together and people are ableto take responsibility and own parts ofthe projects customers are heardcustomers have many opportunities to seethe work being delivered share theirinput and have a real impact on the endproduct they can gain a sense ofownership by working so closely with theproject teams continuous improvementagile projects encourage feedback fromusers and team members throughout thewhole project so lessons learned areused to improve future iterations whilethe level of flexibility in our child isusually a positive it also comes withsome trade-offs here are some of thedisadvantages of Foggia planning can beless concrete it can sometimes be hardto pin down a solid delivery datebecause agile is based on time boxdelivery and project managers are oftenreproducing the tasks it's possible thatsome items originally scheduled for adelivery may not be complete in time anadditional Sprint's may be added at anytime in the project adding to theoverall timeline team must beknowledgeable as ill teams are usuallysmall so team members must be highlyskilled in a variety of failures theyalso must understandand feel comfortable with the chosenagile methodology time commitment fromdevelopers agile is more successful whenthe development team is completelydedicated to the project documentationcan be neglected the agile manifestoprefers working software overcomprehensive documentation so some teammembers may feel like it's not necessaryto do the comprehensive documentation soagile team should find the right balancebetween documentation and discussionfinal product can be very differentthe initial agile product might not havea definite of plan so the final productcan look much different than what wasinitially intended because agile is soflexible new iterations may be addedbased on evolving customer feedbackwhich can lead to a very different finaldeliverable the difference is betweenwaterfall methodology versus our childcan be summed up in two words widgetversus flexible waterfall is a muchstricter rigid process whereas agile isflexible and continuously evolving hereis more on the differences waterfall issequential an agile doesn't enforce alinear process waterfall is a structuredprocess where you can't start on a newface until the previous one has beencompleted on the other hand agile is aflexible process allowing you to movethrough the project as you like inwaterfall projects you can't changethings that were done in previous stageswhereas agile is very accommodating tochanges waterfall projects usuallyinclude defined requirements in advancewhereas requirements are expected tochange and evolve in agile projects atthe end of the day they both want todeliver quality products in an efficientwayso what a fall or agile when decidingbetween agile versus waterfall it canall boil down to this if you anticipateor expect any changes throughout theproject go with agile if you know theproject is fixed unchanging andpredictable Waterfall may be a betterchoiceso as you can see here and what if allyou have a design and you deliver thatat the end that's when you have yourfinal product in agile for everyiteration you have something usable andfinally at the end you have the finalproductquestions for you all whichmethodologies have you used at work andwhich one you think worked best for yourindustry any experience with a childwaterfall hybrid approach do you haveany important lessons learned from theagile project that you want to sharethat might help others in their projectsat work last question what do you thinkthe role of existing managers with agiletransformation especially the technicalmanagers and team leads you see lots ofconflicts and responsibilities betweenagile roles and the traditionalleadership roles these are some of thereferences that I have used thank youfor watching the presentation

INFO 550 Presentation

$23.20

Agile Software Development with Scrum (Series in Agile Software Development)

From Amazon

Sales Rank 83551 Schwaber, Ken/ Beedle, Mike

eXtreme Programming is an ideal many software shops would love…
Buy now

Related posts

Leave a Comment