Last Saturday was an Agile Day at Webonise Lab! The meet brought a wide array of QA Executives, QA Engineers and Agile Testers to address concerns on Agile Development and testing and grasp a fresh perspective on the often talked about methodology.


As you’ll see below, it’s important to quantify why agile works. Who is using it, who is planning to use it and how can you practice it?


But second, it’s equally important to understand the agile method as a qualifier. How does it define each action during the development process?


Let’s start by quantifying. Tushar Somaiya, Agile Testing Alliance Co-Founder , gave a look into Agile Testing Alliance, “a non-profit testing community and certification organization created to grow agile testing awareness, practices and acceptance” and discussed the current market values on Agile Testing.


Somaiya believes agile is the future, and the numbers seems to agree. According to the respondents of VersionOne’s “Annual State of Agile Development Survey,” the number of organizations practicing agile development in 2014 is up to 88% compared to 84% in 2012 and 80% in 2011.

Future Agile Implementation

Source: Annual State of Agile Development Survey 2012

However, Tushar is completely aware of the challenges that arise in the implementation of agile methodology, and he sought to provide ideal solutions to the pressing concerns through the “Problem on the wall” activity. [This is an exercise we recommend you try in your own offices.]


Problem on the Wall Exercise

Write the nature of your current dilemma onto a post-it and attach it to the wall in your office. Have a designated reader go through and propose the dilemma to the group. Spend five minutes hearing solutions from team members, even those who are not directly involved in the project being discussed.


Abhijeet Thalkari, Webonise QA Engineer shared his experience:

“Since developing my own automation framework through Sahi OS, I have stuck by it and continued using it, but I was never entirely convinced of its suitability to the agile methodology. The ‘Problem on the Wall’ activity gave me the assurance, from other team members and 3rd party participants in my field, that this tool is completely suitable as long as we are implementing all of the many features present in the paid version, which fortunately, we are!”


So, what are we getting out of the ‘Agile Method’?



the ability to think and draw conclusions quickly; intellectual acuity.


“Agile development allows me to quickly and consistently respond to an ever-changing project,” said William Slater, Webonise Project Manager. “I am in constant contact with the client to ensure that we change alongside the product.”


In short, as an organization we place an emphasis on qualifying each piece of the development process.  By exhibiting agility each step of the way, we are able to create a fresh and flexible project that each member of the team is held accountable for. When we move closer towards our goals, we have the ability to step back, look at the work we’ve done, make adjustments and repeat. This is the essence of what makes this methodology so effective and efficient.


Aditya Garg, QAAgility Technologies Co-Founder, drove into this further during his presentation “Agile Testing and Testers role in Agile Development”.


Key Values of Agile

Adaptability - Agile is being responsive to change. These changes could mean performing a multitude of functions outside your known set of expertise. You need to be adaptable to keep up with these changes, which are very common in the agile development methodology.


Flexibility - An agile environment calls for frequent changes. A certain degree of flexibility is necessary to ensure you can iterate whenever there is a need to. A flexible team is also of the essence to properly execute these changes without sacrificing efficiency.


Agility - With each iteration made, actions should follow quickly. Considering the speed of the methodology and development, we should change ourselves to keep up.


With nearly 90% of organizations using this methodology, there are certainly identifiable benefits. Having hold ups? Want to drive into how agile can better your clients experience? Get in touch!


Note: Many of our QA Engineers have become members of the working committee for ATA, so if you have questions, suggestions or comments for the recent meetup and for the following ones, tell us! We’ll be glad to relay the message.


Coming up: We’re happy to announce that one of our teams moved on to the second round of bugATAhon 2014, BugATAhon was an event held during the 2nd ATA Pune Chapter meet wherein teams composed of three members are asked to showcase their testing skills. It’s a competition to find bugs! One of the two teams from Webonise got into 2nd round. Round 2 of the bugATAhon event will be held nationally. Although details are yet to be announced, we’re already gearing up!