06. Getting Testing Done in the Sprint – PBI Implementation Sequence

A challenge in getting testing done in a sprint is the fact that the software (PBI) isn’t ready to be tested till implementation/ coding is done. 

How To.
Work on completing each item in the sprint backlog and finish one item after another, see task boards below.

BAD -- Not able to start testing task board, every team member works on a different pbi. Testing can only start at the end of the sprint.

image

GOOD -- Ready to start testing task board, team members work together on a pbi one after another till it’s done. Testing can start early.

image

It is a good practice, but not often followed. it really helps getting testing done.

 

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

Next Tips: 
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 – Done
11. Getting Testing Done in the Sprint - The Customer Test Team
12. Getting Testing Done in the Sprint – The Test Branch

Add comment


Şarkı Sozleri