Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

How to extend (prepend) the development sprint with a design sprint

Sahand Seifi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 27, 2017

We use the following product development process at our company:

- We have our regular development sprints,

- But before any feature or UX improvement goes into a development sprint, it has to pass a design sprint. Design sprints are similar to dev sprints: tasks are identified, pulled into a 2 week design sprint and pass through stages.

Now we basically want to implement the design sprint as part of Jira. This is what we have achieved so far:

1. We'd use one project, not two. Reason being that the design task, let's call it Feature A, has many dependencies (attachments, unique ID, integration to other systems, ...) which we would like to retain as it goes through the design sprint and then enters the development sprint. Basically, we re-use the same task for both sprints.

2. We have created separate jira issue types - "UX Improvement" and "New Feature" - for design sprints. (DONE)

3. We created a separate board for design sprint. Our design sprint is filtered to use only tasks of "UX" and "Feature type", while our dev board is filtered to "Task", "Bug", "Story".

What we haven't achieved and need help with:

1. Our workflow looks like this right now:

New feature -> Design todo -> design in progress -> dev todo -> dev in progress -> ...
New bug -------------------------------------------------------------------^

The problem is Jira workflows seem to only allow one entry point in the workflow. So we either are creating new issues in the "dev todo" stage (good for bugs since they don't require design, bad for features), or we create new issues in the "design todo" stage (good for features, bad for bugs).

2. Upon completion of a task in design sprint (going to last lane), we want it to automatically change to a "task" or "story", but remain as a "todo" and not be "completed". Otherwise, it wouldn't show up as an available story when going to the dev board.

Looking forward to hearing suggestions!

2 comments

Comment

Log in or Sign up to comment
Adam Dutton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 21, 2018

Any updates Sahand? I'm very curious how you're managing this after 11 months without any responses!

Jeremiah Rappley
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 8, 2019

Hey Sahand, if you haven't already come up with a solution for this, I'd be happy to offer some suggestions. It is possible to create separate workflows for different issue types so that your UX Improvement and New Feature issue types are assigned the (New feature > Design todo > Design in progress > Done) workflow and your TaskBug, and Story issue types are assigned the (Dev todo > Dev in progress > ...) workflow. 

As for your last point, changing an issue type programmatically through automation isn't a very simple process. I've usually seen teams work around this by automatically generating a new issue when an existing one is marked complete, and then linking them automatically. So for example, when the design issue is marked complete, it would automatically kick off a dev task in the Todo column and link it back to the design task.

I'd be happy to provide more detailed information if you're still in need of a solution.

Like # people like this
TAGS
AUG Leaders

Atlassian Community Events