Workflow configurations for deploying stages

[Cassandra_Fitzgerald]

I'm setting up a new project for a team where their workflow is:  (see screenshot).

In a typical sprint, a work item doesn't make it all the way to 'Deploy to Prod', and will usually get to 'Deploy to Staging'. 

They would like for me to make 'Deploy to Staging' have a Resolution set to it, so that their sprint reports show the work that has been done, otherwise all of the issues that are in Deploy to Prod status for indefinite amounts of time, outside of the sprint parameters, will make the project reports and tracking not ideal.  But, they want to keep Deploy to Prod as a second 'done' status with a resolution as well.

I obviously do not like this scenario, or else I wouldn't be phoning a friend! Ive not had experience with a team in this environment, so I would LOVE to hear how you all have configured this before.  Any guidance would be much appreciated!

[Benjamin]

HI @Cassandra_Fitzgerald ,

I have seen this done in various ways but usually the deploy to stage and prod is a separate work item. It really depends on the team definition of done and what is the measurement. In this case, the team is saying their definition of done is deploy to staging. Then why include the deploy to prod in the workflow. It seem to me there are two work item here combine into one. Each one having their definition of done. 

First is to sit down with the team and define what is the definition of done for staging and what is for Prod. Also, there might even be another before deploy to staging. How do you know when something is really ready for staging. What says this peice of work and ready to transition from development to staging. 

Lets just say for the assumption that process is good and work flow had to be setup this way. Even if you place a resolution of Done for when it goes to staging. What will be use for Production? Done again. You could see now there's a conflict. Well, why not use staging done and prod done...Now you have two definition of done in the same ticket which defeats the purpose what truely defines when a ticket is complete. 

IF you can split up the work into these pieces,

1. what it takes to say done for development?

2. what it takes to say done for staging?

3. what it takes to say done for production?

[Trudy Claspill]

Hello @Cassandra_Fitzgerald 

Having the Resolution field set is not the indicator to the Sprint that the work was completed.

When a Sprint is ended the items in the right-most column will be considered "complete" regardless of their status. Items in all other columns will be moved to the backlog or another sprint depending on how you answer the prompt when closing the sprint.

Did the team agree that deployment to prod was part of the definition of done? Do the people who look at the sprint reports consider the work not done if it has not deployed to prod? If so then I would not make the requested change.

Is the team that is responsible for deploying to prod part of the team responsible for the rest of the work in this workflow? If not then perhaps a renegotiation of the definition of Done is needed, with a separate task being generated for the team that is responsible for deployment to prod.