One story, design and development

Hey there,

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?




0 answers

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,942 views 12 18
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot