Agile tester is not responsible for testing!! 4 essential differences

Geert Bossuyt

The tester is a member of a Scrum team. This is a different mindset from the traditional views on testers in software development. The agile tester focuses on delivering value instead of on testing. The agile tester is responsible for delivering what the business needs instead of just finding bugs. Most importantly: the agile tester is not responsible for testing!

Recently I published an article on testing in a Scrum team for the Eurostar 2010 newsletters. It’s about the mindset of an Agile tester. This blog post summarizes the core of that article.

To get there, together!

Good interaction is the key to good results. An agile mindset and working in an agile process facilitates a cooperative spirit: “To get there, together !”. To have that ‘Agile Mindset’ means to respect the balance that is presented by the Agile Manifesto and take all decisions you make ( big or small) in the spirit of these principles.

A good Scrum Team feels responsible for the delivery of the desired software on time and according to the agreed quality standards. From a testing perspective some modern test approaches like SmarTEST are designed for ‘agility’ in the testing process. Although SmarTEST has a strong focus on people and interaction, the big change for the tester may still not be fully perceived. Full adaptation of agile principles means that the agile tester is not responsible for testing! How about that?! The team as a whole is responsible for the collective result, which includes testing as one of the steps.

What does this mean for the role of the tester?

For a tester to be truly successful in an agile team he needs to change in four way. These four points describe the heart of the mindset of an agile tester.

  1. The tester is responsible for delivering what the business needs (not for finding bugs).
  2. The tester is focussed on delivering business value (not on just writing, executing and reporting tests)
  3. The tester is a full-time member of the team (not just at the start and end of a sprint)
  4. The tester is no longer a tester, he's a team member with a talent for testing

Of course this is only the top of the agile testers mindset.

How about independent testing ?

Independent testing in an agile environment doesn't differ much from the more traditional approach. Some of the testing is moved to the team's responsibility. Things like integration testing and user acceptance testing allow the team to learn. They need to learn from executing these tasks themselves so that they can understand their customers and their environment better.
Choose independent testing for cross team testing, regression testing and non functional testing.

Conclusion
The agile tester feels responsible for the whole, is fulltime committed to the result, is focussed on delivering business value and acts like a true member of the team.

Independent testing is still desired. It’s important to leave integration testing and user acceptance testing to the responsibilities of the Team so they can keep on learning from what they deliver.

Parting thoughts

Not every tester will be able to change his mindset and become team member first and tester second. These testers can provide most value when working in an independent test team.
Finding those really great testers that are able to become part of the Scrum Team is a challenge. Having them in the teams is a critical factor the success of your teams.

Comments (7)

  1. [...] This post was mentioned on Twitter by bishoph, Daryl Searle. Daryl Searle said: http://bit.ly/ceAv4j - interesting view of the role of tester within the scrum team [...]

  2. Vincent Partington - Reply

    November 16, 2010 at 3:53 pm

    If I read your post correctly, the agile tester is responsible for testing. Shouldn't your title be "Not only an agile tester is responsible for testing" or "An agile tester is not only responsible for testing"??

  3. Bossuyt Geert - Reply

    November 16, 2010 at 6:55 pm

    Hi Vincent,

    Both your alternative phrases are correct, but the point is that the tester is in the first place a member of the Team and thus responsible for delivering working software.

  4. QuickLinks for December | (Agile) Testing - Reply

    December 2, 2010 at 1:13 am

    [...] Agile tester is not responsible for testing!! 4 essential differences [...]

  5. Aaron Hodder - Reply

    January 4, 2011 at 10:19 pm

    Or perhaps, you've just defined what a tester actually is!

    You could reword your blog post with:

    A tester on an agile project is not what I thought a tester was, but what a tester actually is. Huzzah!

  6. Nicolas V - Reply

    October 7, 2011 at 10:56 am

    A way to enhanced the role of testers.

    In practice, testers are paid to find bugs anyway. to do it, one manner is to write, execute and report tests.
    indirectly, finding bugs contribute to delivering what the business needs.

    But of course, tester must be a full-time member of the team.

  7. Bossuyt Geert - Reply

    October 13, 2011 at 6:42 pm

    In practice, tester are paid to give insight in the delivered quality. Not to find bugs.
    This is an essential difference !

    The step from 'tester' to 'teammember' is hugh. For the tester, for the team and for the organization.
    But, organizations that pay their testers to find bugs, must ask themselves whether they also pay their project managers to make a gantt chart and their developers to compile their code.

Add a Comment