11. Getting Testing Done in the Sprint - The Customer Test Team

I don’t mean the acceptance test team, although many think and organize it as if it is the same.

On a test conference a few weeks ago I heard the story of moving testing out of the sprint, or adding a specific test sprint after a development sprint. Both ‘worksrrounds’ I dislike, you lose the flexibility and feedback loop. It was something like the ‘IndependentParallelTesting’ story, also not my favorite solution.

During the conference I posted a tweet, and got replies from Sander and Marcel. Lucky me I’m not alone Emoticon met brede lach (I like the last comment from Sander, the process just should support and embrace it, see: http://www.smartusecase.com.)

image

image

The most clear characteristic of the customer test team is that they aren’t part of the scrum team. You could call them early adopters, power users or the customer test team. Often they execute real life scenario’s, play around in the application or when they are early adopters they do some real work with it.

Beside the question, “do we really need them” is the challenge with these disconnected test teams is, how to get them and their information in a sprint. Threat them as operational findings is a way. But doesn’t solve the challenge of getting their usages data, their findings and reports back on our backlog and in a sprint.

A nice explanation can be found in this video from ‘Groeten uit Delft’ where Rob van Lanen (www.agilestudio.nl) explains how they work together with operations.

 

Beside the solution of giving the ‘disconnected’ customer test team a copy of Microsoft Test Manager 2012 and let them execute their test cases in a ‘structured’ exploratory way. http://msdn.microsoft.com/en-us/library/hh191621(v=vs.110).aspx
Microsoft Test Manager - start exploratory test

A nice work around to get the findings and knowledge from the customer test team in your teams project, is create a separate backlog for them (read this old post – will update it soon).

Two other interesting technologies which can help teams with this scenario (findings found outside the team) are:

  1. PreEmptive Analytics for TFS.
    PreEmptive Analytics for TFS CE offers a free, lightweight way to integrate feedback-driven development processes into your development workflow. Your applications will automatically send back exception report data to your PreEmptive Analytics endpoint service as errors occur during their execution


    http://blogs.msdn.com/b/bharry/archive/2012/04/11/preemptive-analytics-in-visual-studio-and-tfs-11.aspx
  2. Collecting IntelliTrace Data Everywhere
    The collector saves IntelliTrace data as a recording that contains details about exceptions, threads, Web requests, modules, and other system information that is collected while your application runs. In most sections of the recording, you can select one of these items and start debugging with IntelliTrace in Visual Studio Ultimate.

 

Past Tips:
01. Getting Testing Done in the Sprint - The Team and Activities
02. Getting Testing Done in the Sprint – Regression Test Sets
03. Getting Testing Done in the Sprint – Test Automation
04. Getting Testing Done in the Sprint – Undone Backlog Item
05. Getting Testing Done in the Sprint – No Double, Triple Testing
06. Getting Testing Done in the Sprint – PBI Implementation Sequence
07. Getting Testing Done in the Sprint – Risk and Business driven Tests
08. Getting Testing Done in the Sprint – Write Logical Acceptance Tests
09. Getting Testing Done in the Sprint – Test Tasks on the Board
10. Getting Testing Done in the Sprint – the Definition of Done

Next Tips:
12. Getting Testing Done in the Sprint – The Test Branch

 

Comments (1) -

I enjoyed this read. Keep it up.

Add comment