While it is obvious why we should have a release and revision control system for processes and procedures, its worth some discussion why this is even more important for a task library.
As a Task library is in effect a Master Library for important tasks in the organization it has to be accurate and the most current edition to include them in process maps.
In creating a release and revision control system several approaches can be taken based on your particular needs. These could include:
- Only one master task to be in use at a time. e.g. Start the motorcycle this way every time.
- Different master task based on release version. e.g. The procedure changes over time, and the new one is the recommended one, but not included or updated in all process automatically.
- Various task masters based on different configuration and application within processes. e.g. Removal of a air filter in an automobile would have different characteristics based on model, year and configuration
When you have decided which model/s best meet your needs then you will need to number, name and control them accordingly. If using a system such as TaskMap, a unique Task ID can help in this process. We would recommend the following:
- Individual numbering for each task group
- Group the tasks according to a logical function or collection. e.g. All tasks associated with an oil change or regular maintenance, adding new clients to your system
- Create a release or version for the current published version/s of the task library.
Example of version control for ITIL best practices with TaskMap Central (SharePoint repository)
Brilliant series – thank you so much for sharing your insights and wisdom! I look forward to building a Task Library in my organization!!