Change management in Znuny has often been synonymous with one additional package: ITSMChangeManagement. It gave IT teams changes, work orders, a change advisory board and a fixed set of states to move through. It was a predecessor to process management. Starting with Znuny 7.5, ITSMChangeManagement is deprecated. In the next LTS release, after 7.5, we will say goodbye, bringing the best parts of change management to process management.
Origin of ITSMChangeManagement
ITSMChangeManagement first shipped in April 2010 as part of ITSM 2.0, in the
pre-Znuny era. It was designed together with ITIL consultants and co-funded
by a group of companies that agreed on a shared model of how a change should
be handled: which roles take part, which states a change passes through, how
work orders are planned and approved.
Where it misses the mark
- Complex
- Rigid
- Yet another Add-on
The future: Process Management
When ITSMChangeManagement was designed, Process Management did not exist yet.
It arrived in the framework almost three years later, in early 2013. Today it is how our customers model their individual workflows.
The best of Change Management
Deprecating ITSMChangeManagement does not mean dropping what it did well. A major focus for the next LTS release is enhancing Process Management, to bring the best of what ITSMChangeManagement offered to Znuny Framework.
A while in the making
As it will take us time to sort out the how, what and when, you can be sure:
- Znuny 7.5: ITSMChangeManagement is deprecated. It is still available,
but it will not receive new features. - Next LTS release: ITSMChangeManagement will no longer be available as part of it.
- Now: if you use ITSMChangeManagement today, start looking at how your
change workflow would look as a process, and possibly close out changes and trade them for processes. Contact us for help!
We will keep you up to date as the work progresses, including the pre-release testing of the Process Management improvements.
- News