Documenting IT Application Procedures: When & Why

While it is generally beneficial for IT applications to have readily available documented procedures, it may not always be necessary or applicable to every application. Here are some considerations and exceptions to keep in mind:

Legacy Systems: For older or legacy IT applications, documentation may be limited or out-of-date, making it challenging to provide comprehensive procedures.

Open-Source Applications: Some IT applications may be open-source software where documentation is provided and maintained by the community rather than a specific vendor or developer.

Third-Party Applications: Vendor-provided applications may come with their own documentation and procedures, negating the need for the organization to create separate documentation.

Simple Applications: For straightforward applications with minimal complexity or customization, detailed procedures may not be essential, and user guides or tutorials might be sufficient.

Agile Environments: In agile software development environments, where frequent changes and updates occur, creating and maintaining extensive documentation can be challenging. Instead, focus may be on user stories and user acceptance testing to ensure that the application meets requirements.

Business Context: The criticality of the application to the organization's operations and compliance requirements should be considered when determining the level of documentation needed.

Training and Support: Providing adequate training and support materials can sometimes replace the need for exhaustive procedures.

In summary, while comprehensive documentation is desirable, the practicality of creating and maintaining procedures may vary based on the nature of the application and the organization's specific needs and context.