Please login or join to subscribe to this thread
I would suggest that end-to-end testing within sprints is expected by all agile methods and frameworks but limitations around testing environments, availability of testing staff, maturity of continuous testing practices and overall QC practices will impede this.
What this means is that we end up with Scrum-Fall - the Definition of Done represents a partially completed set of work items which need to go through further stages of testing to become a truly potentially shippable product increment.
In addition to the tests made by each teams is common the existence of a System Team that assists in building and support the development environment, typically including the management of the toolchain that support the continuous delivery pipeline.This team provides the integration of all parts from the other teams and performs the end to end solution testing when necessary, and assists with deployment and release on demand. I think without a centralized team to make the integration the Safe framework can generate unexpected integration errors.
There has been a lot written about testing. What information are you looking for, specifically?
Scrum doesn't dictate exactly how you will test, because it's a framework that can be applied to many different types of products and problem solving. However, it does demand that each increment be thoroughly tested to ensure it works with previous increments. There are different ways to address this, including TDD or automated testing. Your team will have to experiment and find the best way to accomplish this, so that your product is adequately tested without overly impeding the team's progress. Even full regression testing, which you might be referring to, can be approached in various ways. Of note, though: Scrum recognizes no sub-teams, so if you're adhering to the Scrum framework, then your entire scrum team owns testing. You can't ship code over the wall and wait for someone else to test it.
We struggled with this very topic on our project. More so, because we have multiple Scrum teams working on different products that are all integrated. (Lesson learned: Don't break up Scrum teams along product lines. Align teams to features.)
You have to find a way to build it into the stories and, thus, the sprint backlog. Otherwise, like Kiron said, your teams won't be delivering releasable content. It can be disconcerting not to do full regression testing as we used to.
I can only advise you to read the following site https://www.scaledagileframework.com/system-team/
I hope it helps you somehow.
chapter 16 on quality in the book linked below gives some good guidance on end to end testing. In short propagating a few messages across the layers in first sprints may give enough confidence that the framework design is coherent and further development can continue.
succeeding with agile Mike cohen
Please login or join to reply