I'm curious how other teams handle the following:
Workflow: Design work is done one sprint in advance of development work.
You create a user story - "as a user, I would like faster access to peanut butter so that I can make my sandwich more quickly".
Now this task requires both design and development work. So do you assign story points to this story as a whole, accounting for both design and development work? And if so, does that mean the story enters the sprint twice? One sprint for design and one sprint for development?
Or do you create a design task and a development task? But if you do that, do you ever bring the story into the sprint? Or is it just a backlog reference?
How do you handle tackling one user story that needs to be worked on in two different sprints, one for design and one for development?
And if you use epics instead of a user story, where does the user story fit into the epic?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs