I'm working on a pretty large-scale project that is looking to ship in the next year.
I lead the Dev and QA teams (5 developers and 2 testers) - we're doing pretty well, but the team is new, there is a big learning curve for them. We are using Agile to build the solution. Prior to this, the team had built some very small applications losing a "loose Agile" approach.
By loose I mean - sprint durations changed at a whim, there was some testing, some requirements - at the end of the day, much of the workload fell to the developers - which can't scale. They didn't really track anything.
It was more - "let's just do what we always do, and we'll go back and update DevOps later" kind of approach.
Fast forward to now, we've got the devs on board with working on tasks and stories - using story points and updating hours. QA is getting the ball rolling with test cases and suites - and just recently our devs jumped in to help run test causes during the last sprint.
The customer is sending over requirement docs (which is fine, we're not going to change the world overnight) but our business analysts/product managers are taking this information and throwing it into stories and/or having the customer add this information directly into features and stories with no analysis lens being applied or back and forth with the customer. Essentially, they are copy and pasting the "information" into the features/stories.
It ends up that we have features and user stories that as one of our developers said - has a lot of information, but not a lot of requirement and requires us to go back and sit down with the customer to rewrite them.
We've spent the last few weeks working with the team to try and figure out how best to get them to translate this information into requirements that are easily digestible, roll-up to the larger customer vision, and will let us get started.
And don't get me wrong, I'm all for developers chipping in on the requirements (we are) BUT I'm not keen for them to have to redo them and then do all the development too :)
What's worked for people in disseminating information into requirements/backlog items/stories?
What has worked well for you with customers?
How do you do this in agile without a PM/BA saying - "It's agile, the devs can redo the changes?"
Would love to hear other approaches we might not have tried.
(Thanks in advance)