Check List for Your IT Documentation#
A good IT documentation: What is it that makes a difference? At bookshops you can find extensive literature to deal with the subject in detail and as a whole.
Our suggestion: Quick successful results first, and then you can consider things as a whole. The following checklist helps you to take a pragmatic approach to achieve first successes. But nevertheless, we recommend the literature ;-)!
# | Checkpoints | Implemented by | Date of implementation | Status |
---|---|---|---|---|
1. Organizational preparations | ||||
1.1 | Have you clarified all requirements for the IT documentation? (What do you want to document? What benefits do you want to generate?) | |||
1.2 | Did you define a team for the management and development of the IT documentation? | |||
1.3 | Did you involve also staff and specialist departments who are supposed to work with the IT documentation? | |||
1.4 | Did you consider the previous documentation? Have you decided if you want to keep it (or parts of it) or if it shall be renewed? | |||
1.5 | Have you clarified which third-party applications you want to integrate in your IT documentation? | |||
1.6 | Did you define milestones specifying which targets you want to reach and when? When do you want to apply the IT documentation in a productive way? | |||
2. Learn to know i-doit | ||||
2.1 | Did you order a test license? Did you make an evaluation with respect to your requirements? | |||
2.2 | Do you know the i-doit basics? (Did you participate in a webinar covering the basics? Did you read the Knowledge Base?) | |||
2.3 | Did you purchase i-doit? (Did you subscribe to an object package and conclude a support contract?) | |||
3. Implementation of i-doit | ||||
3.1 | Is a pre-configured (virtual) machine available covering all system requirements? Are all the required system settings carried out? | |||
3.2 | Is i-doit installed? | |||
3.3 | Is the license installed? | |||
3.4 | Did you set up the essential Cronjobs? | |||
3.4 | Did you set up a backup and recovery procedure? | |||
3.5 | Did you set up a test system? (This is an option which may cause additional costs.) | |||
4. Configuration of i-doit | ||||
4.1 | Did you integrate all relevant third-party applications? Did you test the respective integration? | |||
4.2 | Did you define all persons and person groups authorized for login? | |||
4.3 | Did you remove the login-rights of the preinstalled persons or did you change their passwords? | |||
4.4 | Are the relevant object types activated and the others deactivated? | |||
4.5 | Are the relevant categories assigned to the object types and the others deactivated? | |||
4.6 | Did you create additional object types which you require? Are they configured with the relevant categories? | |||
4.7 | Are the additional attributes which you require mapped by custom categories? Are they assigned to object types? | |||
4.8 | Did you pre-configure the object lists globally for all persons authorized for login? | |||
4.9 | Did you pre-configure the dashboard globally for all persons authorized for login? | |||
5. Initial Filling | ||||
5.1 | Has the previous documentation been replaced (for example, Excel sheets by CSV import)? | |||
5.2 | Have you automated the data imports (for example, JDisc, OCS Inventory NG, CSV files)? | |||
5.3 | Have the manual (re-) works been finished? | |||
6. Using i-doitductively | ||||
6.1 | Did you integrate the IT documentation into all relevant (manual/automated) processes? | |||
6.2 | Are the persons authorized for login well-trained? (Trainings, if necessary?) | |||
6.3 | Are all the requirements fulfilled? | |||
6.4 | Did you initiate mechanisms to adapt your IT documentation constantly to new requirements? (Follow-up projects, meetings on a regular basis?) |
Was this checklist helpful? Do you have any other suggestions or additions? We are happy to receive your feedback!