What is Agile Development approach.

What is Agile Development approach.

If I say in short. it's a Cheap,best and effective. mechanism,

Explanation.
70% we use scrum approach for Agile development which one of the popular way. rest are few.

Now question is what is
Scrum:-

Scrum is a way to restart the game after an interruption, where the forwards of each side come together in a tight formation and struggle to gain possession of the ball when it is tossed in among them

or

Scrum is just one of the many iterative and incremental agile software development method. You can find here a very detailed description of the process.

ref:-
http://stackoverflow.com/questions/11469358/what-is-the-difference-between-scrum-and-agile-development

in brief this is the way of developing the project. 

few terminology we used in scrum.

1. Scrum master
2. Scrum
3. Sprint
4. Backlogs
5. these are the popular one.

functionality of scrum:-

1:-Scrum master:-
Represents management to the project
Typically filled by a Project Manager or Team Leader
Responsible for enacting scrum values and practices

Main job is to remove impediments

2-Scrum Team:-
Typically 5-10 people
Cross-functional (QA, Programmers, UI Designers, etc.)
Members should be full-time
Team is self-organizing

Membership can change only between sprints

3:-sprint:-
in product development, a sprint is a set period of time during which specific work has to be completed and made ready for review.
ref:-
or
A month-long iteration, during which is incremented a product functionality
NO outside influence can interference with the Scrum team during the Sprint

Each Sprint begins with the Daily Scrum Meeting

Daily scrum:-
Is a short (15 minutes long) meeting, which is held every day before the Team starts working
Participants: Scrum Master (which is the chairman), Scrum Team
“Chickens” and “Pigs”

Every Team member should answer on 3 questions

-----------------
Scrum Artifacts:-

Product Backlog
Sprint Backlog

Burn down Charts

Backlogs:-

1. A backlog is a list of features or technical tasks which the team maintains and which, at a given moment, are known to be necessary and sufficient to complete a project or a release: if an item on the backlog does not contribute to the project's goal, it should be removed;

product backlogs:

Requirements for a system, expressed as a prioritized list of Backlog Items

Is managed and owned by a Product Owner

Spreadsheet (typically)

Usually is created during the Sprint Planning Meeting

Can be changed and re-prioritized before each PM

note:-

Estimation of Product Backlog Items:

Establishes team’s velocity (how much Effort a Team can handle in one Sprint)

Determining units of complexity. 

Size-category (“T-Shirt size”)

Story points

Work days/work hours

Methods of estimation:

Expert Review

Creating a Work Breakdown Structure (WBS)

sprint backlogs:-

1. The sprint backlog is a list of tasks identified by the Scrum team to be completed during the Scrum sprint. During the sprint planning meeting, the team selects some number of product backlog items, usually in the form of user stories, and identifies the tasks necessary to complete each user story.
2. or

A subset of Product Backlog Items, which define the work for a Sprint

Is created ONLY by Team members

Each Item has it’s own status

Should be updated every day

No more then 300 tasks in the list

If a task requires more than 16 hours, it should be broken down

Team can add or subtract items from the list. Product Owner is not allowed to do it

Burn down chart:-

Are used to represent “work done”.

Are wonderful Information Radiators

3 Types:

Sprint Burn down Chart (progress of the Sprint)

Release Burn down Chart (progress of release)

Product Burn down chart (progress of the Product)

---------------------------------------------------------------------------

pros/cons

Advantages

Completely developed and tested features in short iterations 

Simplicity of the process

Clearly defined rules

Increasing productivity

Self-organizing

each team member carries a lot of responsibility

Improved communication

Combination with Extreme Programming

cons:-

“Undisciplined hacking” (no written documentation)

Violation of responsibility 

Current mainly carried by the inventors

-------------------------------------------------

ref:-

https://en.wikipedia.org/wiki/Scrum_(software_development)