Agile SDLC: An Example
First, company leaders begin planning – they create a broad overview of what the project will need. At the same time, they will be moving ahead with the design process – they may be designing small parts of a program independently of one another. Coders will begin writing the code – they'll create sprints that include specific task sets that will tie together to serve a particular code module.
As the code is being created, the features and modules are being rolled out. They're being tested during the process: this creates a lot of little “streams” or “threads” of movement that team managers have to control.
As the project moves toward completion, parts of the software are released. An interface may be released that's not yet finished, or features may be upgraded after the fact. Coders are still coding, testers are still testing, but the software is being used in a production environment. As new features and updates become available, they are continuously delivered in an automated way.
All of this is really a gross oversimplification, but it's an example of how something might go when you start to implement the agile method over the traditional waterfall.