Hi all,
I’m a QE Manager at a global brand. We have 8 domain-focused scrum teams working under SAFe, building a greenfield monolith PWA for use in retail stores.
Stakeholders are asking for E2E test plans—ranging from user journeys that span a few teams to broader scenarios involving downstream systems like ERP and finance. Some of these feel more like UAT, which I’d prefer to avoid as a final phase.
I’m open to having QEs write a System E2E Integration Test Plan, but I’m struggling with how to plug this into SAFe practically. Specifically:
How do we trigger these tests incrementally as features become available?
How can we get scrum teams to collaborate on executing these tests early—even if some steps need to be faked initially?
Should these tests be represented as sprint backlog items? If so, how do we decide which team owns what and when?
Would love to hear how others have approached this in SAFe environments. Thanks!
There will be thousands of variations, what ones are the ones they want testing.
Does it warrant downstream testing?
In my experience they are worried about something going wrong. You may already be able to put their mind at reset with a slight change to reporting or something. Having said that normally if you go back with a lot of questions they start to see the scale of what they have asked for. Normally (not always) it goes away and life carries on, if it doesn’t go away then worry about it
I like that technique…asking a bunch of questions so people realize the depth. Thanks @leetestsmurray. The why is mostly because important stakeholders asked for this scope of testing. In addition. I think it will uncover important problems. A curse of scrum is that it optimizes focus to one’s own sprint goals, IMO. It doesn’t incentivize team members to collaborate with other teams enough. And I think bugs hide between teams.
