Agile

                                          Agile Methodology

AGILE methodology is a rehearse that promotes continuous iteration of development and testing all over the software development life cycle of the project. Both development and testing activities are concurrent clashing the Waterfall model.

                            

•       The customer has initial and frequent opportunities to glimpse at the product and make decision and changes to the project

•       Narrow projects can be implemented very promptly. For extensive projects, it is harsh to estimate the upshot time.

•       Error can be hooked in the middle of the project.

•       Development process is iterative, and the project is accomplished in short (2-4) weeks iterations. Very less planning is done.

•       Documentation attends less priority than software development

•       Every iteration has its own testing phase. It concede implementing regression testing every time unusual appearance or logic are released.

In agile testing when an iteration confine , shippable visage of the product is delivered to the customer. New features are usable right later shipment. It is handy when you have marvelous contact with customers

.

•       Testers and developers endeavor together.

•       At the cease of every sprint, user acceptance is performed

•       It requires finale communication with developers and together analyze requirements and planning.

There are various methods present in agile testing:-

SCRUM  is an agile development approach which concentrates uniquely on how to manage tasks within a team-based boost environment. Basically,

Scrum is borrowed from activity that occurs during a rugby match. Scrum believes in entitle the development team and advocates working in cramped teams (say- 7 to 9 members).

It consists of three roles, and their responsibilities are explained as follows:

Scrum Master:-

Master is responsible for context up the team, sprint meeting and removes hyndrance to progress

Product owner:-

The Product Owner build product backlog, prioritizes the back log and is culpable for the delivery of the functionality at exclusive iteration

Scrum Team:-

Team manages its own trial and organizes the trial to complete the sprint or cycle.

Product Backlog:-  This is a repository where requirements are tracked with details on the no requirements to be completed for each release.

It should be finance and prioritized by Product Owner, and it should be dispersed to the scrum team. Team can also appeal for a new requirement addition or alteration or deletion.

Scrum Practices:-Practices are described in detailed:

Process flow of Scrum Methodologies:-Process flow of scrum testing is as follows:

         •          Each iteration of a scrum is admitted as Sprint

         •          Product backlog is a list where all details are             enrolled to get end product

      •      During each Sprint, top items of Product backlog                are preferred and turned into Sprint backlog

      •     Team works on the construe sprint backlog

      •     Team analyze for the daily work

      •     At the cease of the sprint, team delivers product functionality