System Testing - how to manage?

Posted Wed, 07/01/2009 - 14:29 by admin

How to manage System Testing if:
A. most of the task in sprint finish at end of iteraiton
B. Testing team is not experienced yet in the area of testing
This leads to the end of faults in testing and failure of iteration

‹ Planning poker How the fault corrections should be defined in backlog? ›

A. depending on available

by roman.sorokiewicz - 07/04/2009 - 00:20

A. depending on available resources/timeline either add some time for testing (by planning smaller tasks or making longer sprints) or introduce external group of testers and assume some bug fixing tasks into incoming iterations. Second approach might seem to be ineffective and against rules (as many iterations might fail), but it depends on system architecture and complexity. Sometimes it is just not possible to test the task during one iteration, ie in case of demand of large integration.

B. inexperienced testers will create problems, no matter what methodology is used. ISEB training/certification or external support should do the trick.

testing - how to handle it?

by jurek wachala - 07/13/2009 - 19:24

I agree to leave the decision where testeters are located to the team. If system does not support option of joining testers to the team or is expensive in long term, better to keep it outside and introduce internal testing tools (i.e pair programing)

But if possible I would really push to include testers to the team, even for consulting. All the doubts they might have on coding phase are cheaper to fix or check with customer then, rather than during testing phase.