I'm part of a small IT team in a business that operates in a highly regulated industry. Despite having only three of us, our setup is quite complex with numerous virtual machines, data segments, firewalls, and domains. We generally manage things well, but we're currently using Teams to log our changes, which often gets messy since it can be hard to search through. We're dealing with changes like expanding drives, allocating RAM, and other configurations, but this informal system is causing us to lose track of what we've done over time. We've got a ticketing system, but we're not using it effectively since it came bundled with other tools. I'm looking for suggestions on how to record and track changes more systematically, with a focus on something that's quick and simple to implement since we don't have lots of time to learn something new. Any advice?
5 Answers
If you're looking for a leaner solution, you could start using a shared document or a simple ticketing system for daily operations. For any larger changes, keep retrospectives to learn from past actions and tweak your process over time. It could be as simple as dedicating a Teams channel to formalize these approves and track changes!
Above all, keeping thorough tickets for all changes, especially for significant tasks, is essential. Utilize your company’s official documentation system to track changes accurately. Whether it's a change document, a configuration management database, or a simple log, everything needs to be recorded. This will help your team find historical context later on without digging through chats or emails.
Implementing a ticketing system is a solid first step for tracking changes reliably. Most organizations establish a Change Approval Board (CAB) to review and discuss changes regularly, which might help you maintain clarity and accountability. It's essential to document everything formally instead of relying on chats or emails, especially for changes that have potential risks.
A concept from ITIL is distinguishing between Standard and Normal Changes. Standard Changes follow pre-approved procedures and can be executed by authorized personnel. In your case, ticket templates could streamline this process. Normal Changes, which require more planning and assessment, would also benefit from a consistent documenting method.
Consider adopting an infrastructure as code approach. Store your configuration files in Git, where every change is tracked and version-controlled. This way, you can manage changes through pull requests, which become your change requests. It simplifies the process and lays down a clear audit trail.
Absolutely, having that official process protects you from issues down the line. It's crucial for accountability!