Now a days we are using different methodology for software development life cycle. One of the most famous and widely used methodology is AGILE.

Why Agile is preferable?

There are 2 methodologies for SDLC, one is waterfall which is old one and it have linear process. Where each stage have the dependency on the previous stage.

For any new project whole project will go for design phase first then development and then verification and validation. So complete project work in a linear way. But problem with waterfall is if any requirement change in between then how we will accommodate it? If development was already completed then we again have to go back and start project from scratch.

That’s when Agile methodology come into the picture. In Agile complete project is divided into blocks and each block will go in all phases like designing, development testing. And in parallel team can work on second block. For example any requirement slightly change after completion of first block then team directly incorporated that requirement in second block and no need to work again on first block . Also we can work on multiple blocks on same time so that we can complete project in less time.

So agile is more fast and flexible methodology, Fast because we can work in parallel and Flexible because any requirement change can be incorporated.

Agile Terminology:

In agile there are some terms which u must aware of because these terms are used everywhere for Agile.

• Scrum: Agile can be used by different frameworks like Scrum, Kanban or some customized frameworks. Scrum is most famous one among them. Scrum is model that follows predefined roles, responsibilities and meetings. 
• User Stories: A user story is a very high-level definition of a requirement, containing just enough information (acceptance criteria) so that the developers/testers can produce a reasonable estimate of the effort to implement it.
• Epic: A very large user story that is eventually broken down into smaller stories. In normal practice Epic is used for whole project and then it divided into smaller user stories based on Acceptance criteria.
• Sprint Backlog: A sprint backlog is a segment of Product Backlog Items that the team selects to complete during a Scrum sprint. These PBIs are typically user stories taken from the product backlog.
• Daily Stand-up: A Daily stand-up is a whole team meeting that happens daily at the same time and usually lasts for 15 minutes or less. Each team member needs to provide the following information: what did I do yesterday, what am I planning to do today and what impediments do I currently have.