Phy-gital Roundtable: Breakfast Roundup from Germany and Netherlands

02 May '15 | Debjyoti Paul

German Shoppers: Meet Them in the Fast Lane to Phy-gital

15 January '15 | Ralf Reich

Shoppers Will Share Personal Information (But They Don’t Want to be “Friends”)

15 January '15 | Anil Venkat

Modernize or Perish: Property and Casualty Insurers and IT Solutions

14 January '15 | Manesh Rajendran

Benelux Reaches the Phy-gital Tipping Point: Omnichannel Readiness is Crucial

13 January '15 | Anil Gandharve

The New Omnichannel Dynamic: Finding Core Principles Across Industries

13 January '15 | Debjyoti Paul

Technology does not disrupt business – CIO day 2014 Roundup

02 December '14 | Anshuman Singh

Apple Pay – The Best Is Yet To Come

02 December '14 | Indy Sawhney

Digital transformation is a business transformation enabled by technology

01 December '14 | Amit Varma

3 Stages of FATCA Testing and Quality Assurance

06 October '14 | Raman Suprajarama

3 Reasons why Apple Pay could dominate the payments space

18 September '14 | Gaurav Johri

Beacon of Hope: Serving Growth and Customer Satisfaction

05 August '14 | Debjyoti Paul

The Dos and Don’ts of Emerging Technologies Like iBeacon

30 July '14 | Debjyoti Paul

What You Sold Us On – eCommerce Award Finalist Selections

17 July '14 | Anshuman Singh

3 Steps to Getting Started with Microsoft Azure Cloud Services

04 June '14 | Koushik Ramani

8 Steps to Building a Successful Self Service Portal

03 June '14 | Giridhar LV

Innovation outsourced – a myth or a mirage or a truth staring at us?

13 January '14 | Ramesh Hosahalli

What does a mobile user want?

03 January '14 | Gopikrishna Aravindan

Testing is going agile

Posted on: 10 February '11

Going Agile… If you are wondering whether iterative delivery methods are being adopted and taking hold, stop wondering; we are here and the trends continue to support the shift. Recent surveys published by various industry analysts show an increase in companies looking towards iterative/agile methods for the delivery of their software products. It is from personal experience in working with companies in transition from waterfall to iterative that I write some useful suggestions and recommendations.

Driving Collaboration

This is probably the single most important element of success for any organization going agile. For example, align all the team members’ performance goals/bonus payouts to the success criteria of the project. Co-habitation of the various disciplines (team members from product/business, development and testing) has to be enabled (team rooms/open spaces / no physical barriers to communication, etc…) and practiced. For your remote teams, ensure the daily meetings / WebEx sessions are taped, posted and reviewed. The offshore teams must be fully integrated with the onsite team.

Test Organization and Responsibilities

Onsite test consulting leaders work on the collaboration/iteration testing activities directly with the delivery team, validate the test scenarios/coverage and are the primary conduit to the offshore testing team directing regression, the iteration and the production release. Providing adequate onsite testing resources to keep up with the iteration will be very important to the offshore testers keeping up with regression and iteration. Agile testing requires early testing and integration to validate the quality of the iteration.

Metrics

Yes, metrics and process improvements still apply in the agile world. Specific to agile, we are analyzing whether we delivered the value addition software the business requested, backlog burn-down, iteration defects and cycle time to close, number of builds/iterations against plan, etc. Project Management will be tracking these and other development and testing metrics to look for efficiencies in our estimate and planning assumptions. With each iteration, the planning/estimation accuracy should increase.

Tools

The intent here is to enable collaboration through common tools, processes and frameworks. The data produced must be accessible, maintainable and transparent. For example, we refer to tools like Requirements Management, Test Management, Source Code and Documentation Management. In addition, automation test execution tools are mandatory for the success of agile delivery. Ensure you have an automation framework in place before you go ahead and script test cases. If not done properly, the efficiencies you expect from automation will not be realized and the test team will fall behind in regression and iteration validation.

Naturally, how a company embraces iterative/agile delivery and to what extent will depend on their maturity level across people, process and technology. What usually happens is a mix-match of iterative principles/methodologies with some aspects of waterfall. It is during this “agile-like” period of transition that creates the most challenges for the team expected to deliver the return on investment. Stay the course and continually get support/reinforcement from your business and technology leaders.

Mindtree Blog Archives

Mindtree blog Archives are a collection of blogs by various authors who have independently contributed as thought leaders in the past. We may or may not be in a position to get the authors to respond to your comments.

  • Well said. Agile can be embraced and adopted in a mature organization. Frameworks are just frameworks. Scrum is a good example of a framework. Take bits and pieces of what works for your organization!

    http://agilescout.com/traps-and-pitfalls-of-agile-software-development/

  • Paul Fratellone

    Agreed. Every company/culture and maturity will be different. The keys to success is understanding what can be implemented, adopted and be effective when making improvements.

  • agile testing

    I really so much impressing as per agile testing methodology…..Thanks buddy