Hi all,
My company is new to using Scrum to develop software. Prior to this we used a waterfall process. In the old process, development would develop the project to a Command Specification, and when they were finished testing would test to their Test Design Specification, created from the Command Specification.
Now using Scrum, we are breaking projects down into PBIs which are then tackled by team. Initially, we had coding tasks for the developers, and testing tasks for the testers. But what we are finding is that there is little value in testing such granular PBIs with such granular Acceptance Criteria. It's trivial and it does not really fully exercise the functionality.
It seems to us now to make more sense to test a group of PBIs as part of a Feature. That is, when all of the development PBIs in a feature are done, then a Testing PBI will be scheduled by the Project Owner with testing tasks within that Testing PBI
created by the Testing Lead.
I have not investigated the "Test" tab in TFS much so I don't know how to use that part of TFS for handling testing.
Are we on the right path for testing using TFS?
Steve