| 5.4 Continual Improvement Manager (CIM): | | Our CIM is a Change Manager with responsibility to break down peoples natural reluctance to change and to promote relentless improvements. | | Improvements have simple go/no-go decision point; will the improvement increase effectiveness and/or productivity. | | We suggest that an improvement request that is not able to demonstrate that it brings increased effectiveness and/or productivity is not an improvement and should be rejected. |
| Relentless Continual Improvements: | | An improvement idea that will lead to an increase in effectiveness of the service and increase in the productivity of people is good for all parties. | | The application that was good enough last year will not be good enough next year - continual improvements must be demanded to ensure that as the business evolves, its application service evolves in parallel. | | The bespoke user interface is designed to match corporate layout standards and any improvements that are needed shall be delivered - we understand that it is your application and it must look like your application.. |
| Practical Limits: | | Text shall be limited to about 20 rows of data to deliver acceptable response times for most users. | | Images shall be limited to about 100,000 bytes using a file format as PNG. | | Audio shall be limited to about 100,000 bytes using a file format as MP3. | | Video is not yet supported by any open international standards and so a special Flash download may have to be used pending HTML5 standards. |
| | | Cannot be Sanctioned: | | * Any improvement request that would impact on the foundation policies such as no data can be deleted cannot be sanctioned. | | * Any improvement request that could reduce security or compromise privacy such as loose sign-in rules cannot be sanctioned. | | * Any improvement request that would require a change to international standards such as HTML or SQL cannot be sanctioned. | | * Any improvement request that could cause the application not be be able to used by certain computers, printers or other equipment cannot be sanctioned. | | * Any improvement request that demands the download and installation of special software cannot be sanctioned. |
| We choose not to: | | * Develop a set of web pages or service for an up-front fee - plenty of student designers may build your HTML web pages at £100 per page. | | * Operate web systems that have been developed by other people to different standards that may fail from time to time. | | * Deliver web services that contain bugs, that crash your computer or can be hacked by SQL injections, buffer overflow and other common defects. |
| Document Control: | | 1. Document Title: Continual Improvements. | | 2. Reference: 165400. | | 3. Keywords: ITIL Continual Improvements. | | 4. Description: ITIL Continual Improvements. | | 5. Privacy: Public education service as a benefit to humanity. | | 6. Issued: 13 Feb 2017. | | 7. Edition: 2.2. |
|