Story/Feature communication

[s03jlord1]

Hi,

I'm curious to know how other companies communicate minor releases to their internal ServiceNow users.
We are a fairly large company that are constantly running in sprints, to develop stories/enhancements/features/fixes into our environment. Large items such as Upgrades/Go Lives/downtime are always sent by mass email to the entire company with banners on our portals but how do you communicate the rolled up output of your sprint items to the userbase?
The person who raised the story typically gets a walk through and notification to say its complete etc but we are finding we are missing people/info isnt passed on etc.

Newsletters? MS Teams integration? Mass email? Anything else?

Perfect example would be a new field added/removed from a global form or a minor adjustment to a module/App that people use across the business.

Thanks! 

[Brenda Williams]

Hi,

We work in sprints but batch everything up in a release on a monthly basis. We put together release notes for each release within in a KB article and have a category in our knowledge base that folks can refer to. We have a ServiceNow slack channel across the org and post there in advance of a release with the KB link as well as we have a status page that we post the date and time we are performing the maintenance to do the release with the KB link. We post the night of our release again with the KB link that we are completed in the same slack channel. Then we send out a mass email to all users called The Cycle that highlights the biggest changes of our release and it contains the link to our KB as well. Users can't say they are missing something from our end unless they are choosing to ignore us. We haven't had any complaints of too much notifications either. Editing response as I forgot that we do also put up the banner about a week prior to a release that also includes the KB link.