Managing after sprint is complete in CWM

[saxtonjoshu]

After a sprint is complete, currently our process is to keep the story on the sprint and associate the sprint with a change or story -> release with a change. (I am trying to get our organization back to the normal way of doing things). 

When I view the story form in the fulfiller view (Default view) - I do not see the Sprint field populated on the form. When I look at the story in the backlog planning view on the sprint, the sprint is populated for that same story. 
Which field has the CWM sprint field ot add to the fufiller view? 

[SVimes]

My last position was the first time I would have been exposed to something like this. At the end, I was in control of the process so I could decide how to move forward, inform my team, train, update operational teams, etc. as needed. We did have Agile Development 2.0 installed at the time.

That aside, CWM documentation does refer to Enterprise Agile Planning (available with Strategic Portfolio Management with a Pro license) to support gaps, connecting EAP with CWM, and a note not to use CWM and Agile Development 2.0 at the same time for sprint management.

Looking through CWM alone, we still have Epic (although not currently displayed in CWM, but can be referenced on the CWM tasks), Sprint, Story, and Scrum Task so that leaves things like Release, Theme, and Product. There is a whole thread HERE that goes into these things.

If you MUST move to CWM for agile development tasks, you may need to pare down to Sprint, Story, and Scrum Task for the traditional Agile-type tasks.

• You could create separate folders for Releases and Themes with representative task boards to describe the work and create a prerequisite dependency on some arbitrary "final" task on a Sprint board.
• You could create an Agile folder with separate boards representing a Release or Theme with all the tasks representing a backlog you can assign to the various sprints and a separate folder for Completed Agile to move the boards to when you are done with them.
• You could create business logic on the sn_cwm_task, sn_cwm_sprint, and sn_align_core_scrum_epic tables.

Regardless, getting creative to make ends meet is a solution until the OOTB CWM solution is caught up with all the other components if you do not/cannot implement EAP.

[saxtonjoshu]

That's not exactly my question. 

My question is how you handled the CWM tasks (Stories, incidents, etc.) that get added to a sprint and then the sprint ends and you complete the sprint. I would expect the completed stories would be moved somehow to be deployed to production and marked as completed. In OOTB ServiceNow the story state is complete, but our organization does not mark the story as complete until AFTER it's deployed to Production. 
How did you deal with the work in the sprint after the sprint ends? 

[SVimes]

To clarify, I didn't have the opportunity to actually implement CWM before the instance I worked on was retired. I just started planning.

In my case, I would adjust the process to fit the technology if the technology cannot be adjusted to fit the process. Technological limitations have forced hands often enough that processes can't always be the law of the land. That's why we have workarounds.

If I am only using CWM and need Stories to be marked as complete AFTER they have been deployed, I need to make sure I am marking them as completed before marking the Sprint complete otherwise CWM is going to force me to move the incomplete Stories back to the task list. That being said, my Sprints should be managed in such a way that the final task of any Sprint would be "Promote changes to PROD and mark Stories complete" so I am making sure the appropriate tasks go to the backlog or are moved to another Sprint before I mark the Sprint I am working on as complete.

The alternative is to change the definition of DONE from Deployed to Approved Deployment for marking Stories as complete.

Making customizations to CWM look possible if you want to dig into the UI Builder components, but that may not be worth the effort as ServiceNow continues to develop the CWM application.