The effective retrospectives for agile testers.

The effective retrospectives for agile testers.

Agile In Nutshell.

Agile In Nutshell.

Difference between traditional and Agile development

Difference between traditional and Agile development :

New Series started form this month: Agile QA

Agile QA:

Agile methodology is an adaptive methodology, its people oriented. 

It helps us to increase productivity and reduce risks. 

There are 2 popular agile methods- Extreme programming (XP) and Scrum.

Characteristics of the Agile methodology: 

1. Frequent Delivery  2. More Iterations  3. Test frequently  4. Less defects

Brief about SCRUM and XP : 
Scrum: Each iteration would called a scrum which can be a 1- 2 Months.
In Scrum Client prioritise his requirements what  he want first. 
If developer did not meets all the  requirement which was being fixed for a 
perticular scrum  than rest of the development part would be transferred to  
the next scrum (would be delievered in the next build),   
means developer cann't increase time decided for a scrum. Its fixed.  

Extreme Programming (XP): here iteration period would be
less then in scrum, which is being 2-4 weeks. 
Here developer priorities what to do first on the basis of  
client requirement. This duration which was being fixed for a iteration, 
can be increase if the some development part is still pending. 
The build would deployed with having all the client needs.
Thus iteration period is not fixed here it can be increase but iteration
should meets all the client's requirement in  this build. 
More attension is required for testing in XP.

Test Selenium PHP Logo :)

Daily Scrums

Daily Scrums:

It improve communications, eliminate other meetings, identify and remove

impediments to development, highlight and promote quick decision-making, and improve

everyone’s level of project knowledge.

The ScrumMaster ensures that the Team has the meeting. The Team is responsible for conducting the Daily Scrum. The ScrumMaster teaches the Team to keep the Daily Scrum short by enforcing the rules and making sure that people speak briefy. The ScrumMaster also enforces the rule that chickens are not allowed to talk or in anyway interfere with the Daily Scrum.

The Daily Scrum is not a status meeting. It is not for anyone but the people transforming the

Product Backlog items into an increment (the Team). The Team has committed to a Sprint Goal,

and to these Product Backlog items. The Daily Scrum is an inspection of the progress toward

that Sprint Goal (the three questions).

Follow-on meetings usually occur to make adaptations

to the upcoming work in the Sprint. The intent is to optimize the probability that the Team will

meet its Goal. This is a key inspect and adapt meeting in the Scrum empirical process.

Responsibilities of the ScrumMasters:

The responsibilities of the ScrumMasters can be summarized as follows:

• Remove the barriers between development and the Product Owner so that the Product Owner directly drives development.

• Teach the Product Owner how to maximize ROI and meet his or her objectives through Scrum.

• Improve the lives of the development team by facilitating creativity and empowerment.

• Improve the productivity of the development team in any way possible.

• Improve the engineering practices and tools so that each increment of functionality is potentially shippable.

• Keep information about the team’s progress up-to-date and visible to all parties.