Relationship between Agile Stories, Agile Releases, Change Management and Release Management

selenaasmith · ‎10-19-2016

My customer wants a UI Action to create a Normal Change record from an Agile Story record. While it's definitely possible to do so, is it considered best practice? How does SN's Agile Development module coexist with the Change and Release Management pieces?

BALAJI40 · ‎10-19-2016

Basically agile methodology related to future development, issues to be modify on previously developed, enhancements etc....

Change management helps your organization understand and work to minimize the risk of changes to the IT environment.Change requests are often entered after the root cause of problems or incidents is determined to require a change to the environment. Other changes are scheduled, such as routine server maintenance or a hardware upgrade. The change management process in the Express platform helps you manage changes from entering and scheduling the change, to obtaining approvals and performing associated tasks.

View solution in original post

paschos · ‎04-26-2019

Yes, it does make sense to have a UI Action and connect stories to changes. Change Mgmt should be used to capture your approvals so nothing should go to production without an approved change. We also use Release records to group changes together and release together as a "package". Treating stories as changes and combining them in a release gives the organization the holistic view of changes that are targeting implementation.

Paul Ciarfella · ‎04-26-2019

This is where everyone's model of "best practice" agile, or definition of agility, release management, scrum or scrumbut or scrummerfall differs.

I agree with your approach if the organization is tracking releases. Another approach is if the model is one of continuous delivery and there is no "release" (nor are there any sprints). So delivery or completion of a story via a change request makes sense.

Now, is that a normal change request or a standard change request???? Again, it depends on how the organization is managing infrastructure changes. Some stories could be "standard" changes, say if the story is maintenance on a deployed service with no impact, whereas a story that is introducing a new feature that requires sign-off or is service-impacting may be a normal change.

paschos · ‎04-29-2019

Fair point... I assumed @selenaasmith is using Release Mgmt since the question was around guidance for using Agile and Change/Release Mgmt. We are not yet in the continuous delivery model but would like to be this year. We are thinking that we would create normal change tickets associated to a Release when introducing changes to our customers and standard change tickets for daily deployments into production (daily deployments into production environment will not mean new functionality is available to our users yet). Is that the approach you are using?

Paul Ciarfella · ‎04-29-2019

Yes that is similar to our approach. Our CICD tools (Jenkins, etc) automatically create and close one type of standard change for record keeping for each build or deployment. Other standard changes are entered via the change catalog and close automatically at the end of the change window in an effort to reduce manual labor.

Normal changes are used to major releases or new product deployments.