I am aware of the fact that agile testing is an ongoing process and should happen in parallel to development. But how is that actually achieved? Is it even possible to fix all found issues in the same sprint?
Current project status: The company uses Scrum several years now, so everyone is familiar with that. However, we haven't had dedicated testers yet, as the intent was to have self-organizing teams, where everybody is responsible for everything. Well, that did not work as expected ;) So, each team will get one dedicated tester.
My plan is to integrate the tester at the very beginning of the sprint (2 weeks): estimation, sprint planning meetings etc.
To prevent defects, Acceptance Criteria will be refined by the Three Amigos (Tester, Developer, Product Owner) into thin slices / steel threads. Thereby it should be possible for the Testers to verify functionality asap while the developers can go on with development of the next slice. Level of automation for each slice will be defined together.
Still, I think testers should be able to go through the user stories manually and create bigger Test Cases or do Exploratory Testing in the same sprint. If that is done at the very end, how is it possible to fix defects in the same sprint; maybe it is not that important?
Would be very interesting how it works for you guys (Sprint length, type of Testing, responsibility of the Testers etc.)