Hi brain trust,
I basically lead a team of Quality engineers who are embedded on Scrum teams. One team has been replaced by an agile / lean-thinking Product Owner but the QE is very detailed / waterfall approach. Right now, the habit is hard to break from the QE as she was used to having a very detail-oriented PO with multiple toolsets to track requirements, etc. I’m trying to get her buy-in to be more flexible (but that’s another story) and eventually we’ll get there but right now, I need a short-term solution.
So, the process is that the PO will put up a story with very high-level Acceptance criteria. QE will then provide some Testing notes with the details she wanted and then include those as part of the AC before being locked-in during the Backlog grooming sessions.
The PO thinks that the additional AC are looking like test steps and very detailed (and to be honest, looking a bit un-agile). The QE is used to raising bugs as the requirements are usually loosely followed by the Developers, hence, the user story goes back and forth and has a longer feedback loop at the end of the delivery (Making the devs and QA collaborate more and building the feature together is again, another story to discuss!). That is the reason she wants to put more details at the start of the design / requirement phase.
Question is, how do I find the right balance at its current state?