Agile Familiarisation. Overview of what Agile is June 2008. Sound Familiar. Time to market for projects is too long Unrealistic deadlines Poor Estimation Requirement Changes Immature architecture and design No Documentation or too much Inadequate Testing. Projects today are.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Overview of what Agile is June 2008
Responding To Change
Typical water fall model development (With some overlap)
Agile model with Iterations
Small iterations help in getting early feedback
Testing team peak
Development team peak
Design team peak
No big team peaks/Spikes
All the teams formed at start of project
Development team is idle or not formed
Requirements and test team are not on project
“Iterative development is an approach to building software (or anything) in which the overall lifecycle is composed of several iterations in sequence.
Each iteration is a self-contained mini-project composed of activities such as requirements analysis, design, programming, and test.
Usually the partial system grows incrementally with new features, iteration by iteration; in other words, incremental development.”
Agile development is a methodology of software development that
emphasizes customer satisfaction through continuous delivery of
Functional software. Based on a variety of iterative development
disciplines Agile methods put developers to work in small teams to
tight budgets and short timescales.
Agile Method Types