Hi Everyone! My team is working on features for a mobile app. We have Android and iOS developers. I'd like to check with the community on the best way to assign tasks in jira for them.
Currently we have one product story with requirements and acceptance criteria, and several sub-tasks assigned to each of the developers. Because ultimately they're working on the same feature, and it can't be completed until all sub-tasks are done. However each person has their own velocity + summer vacation are adding to the complexity. We're now in a situation where Android is far ahead on their dev tasks, and iOS is far behind (2 sprints behind). Therefore we need to add all stories with open sub-tasks to the current sprint. We don't like this for 2 reasons: (1) it's hard to see what is the real commitment is for each sprint, and (2) it's impossible to estimate the team velocity, because we estimate at the story level.
We were thinking about creating a user story for each developer, but then we're not sure where to store the requirements. Should we duplicate them for each story? If there's a change and someone forgets to update all tickets, we might end up in a situation where stories would have different description. We also love having comments all in one place, it's useful for knowing the context.
Ideally we'd like to be able to both see the progress of a feature/product task and be able to estimate the sprint velocity correctly.
I'm curious to know what other companies are doing in such situations. The team is open for a change, so I'm doing my research now. Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.