If there is no role for “tester” on a Scrum Team, how can they ensure the product is fit for purpose and of high quality? Consider Acceptance Test Driven Development.
Consider building an ATDD process. Acceptance Test Driven Development pairs Acceptance Testing with TDD to achieve a powerful effect, namely you not only build the “thing right” (TDD) but you also build the “right thing.”
Acceptance testing is also a wonderful way to shorten and amplify the communication feedback loop a.k.a. practice the Second Way within the team. I’ve personally developed/scrum mastered for a team that practiced something like this and saw extremely beneficial work patterns and valuable software that emerged as a result.
Last, UAT and Exploratory Testing will probably be valuable practices. Consider using User Voice and stakeholder feedback for live products and perhaps tapping the Product Owner or internal stakeholders and some exploratory testing efforts. Also, don’t discount the value of “eating your own dog food” if the product is something your organization can use as it develops. Consider the sweetness that is the Trello Development Board.
If you want to learn more about ATDD, here are some helpful links:
- “Acceptance Test Driven Development (ATDD): an Overview” – Elizabeth Hendrickson
- “Is Acceptance Test Driven Development (ATDD) Worth the Effort?” – Peter Karas
- David Starr pluralsight course on Test First Development:
- Consider using http://cyber-dojo.org/ as a learning tool to investigate and build your skill in writing both unit tests and acceptance tests.