What is Agile Methodology?How Agile is Processed

agile software

agile software

Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.

: In this type the whole product or the application is divided or categorized into various modules, and each module is developed and tested and delivered in increments hence it is also termed to be incremental model.
: After each module is developed and tested it gains feedback from the client and only when the client is satisfied it moves on to next module.
: It has different approaches extreme programming, SCRUM, etc always extreme programming is used (Below is all about extreme programming).


  • Each module separate user story, the requirements in Agile is termed to User story.
  • Each module is considered to be separate project.
  • Developer and tester work in pairs for e.g. one developer writes codes and other verifies it, in similar way one tester writes test case and other reviews it and execute it.                                                                                                                       

How Agile is processed:

: It starts up initially with the requirements phase, in this phase all the requirements are gathered from the client.

: After gathering the requirements team starts discussing about the Scope of the project which means what we are going to do, how we are going to start etc.

: After discussing they categorize the functionality and breaks the whole application into several modules.

: Once the module is decided, the Development team starts writing the codes and develops the particular application, in the project environment (Please scroll down to know the definition)

After the module is been developed, QA team starts testing the module, if they find any issues they report it to Dev team and fix the issues before releasing it to client

: Once testing part is successful it is implemented on real time environment and delivered to the client.

: After it is been delivered to client, Client has their exclusive QA team who does their testing, and let the company knows if they have any issues, or if they need any modifications.

Once the customer is satisfied with that particular module that particular module is signed-off(Client is satisfied hence closing that module work) and we will move on to next module.

If client is not satisfied we will work on same module until he says OK.

Speak Your Mind