Best Practices
ADRs
It is best to use Git for ADR management. Sharepoint is second best. An already mismanaged Confluence instance is plain silly.
Advice for SAs
Why is it convenient to trumpet '..As Code' as industry best practice and not 'Low Code'? Seems this is done for convenience and arrogance and not to solve an actual problem. Cutting to the chase, you do your job and let the folks who manage platforms do theirs. You might notice, the platform folks are the only ones in this conversation that actually deliver.
MicroServices
If you are going to argue about MicroServices make sure you understand them and the Use Case at hand....Also, API Gateways are designed to facilitate them
ServiceNow (and others)
It is plain silly to change a user's job title just to allow them to do functions they should be able to do anyway. Silly was used and not stupid, because stupid is not a nice word
ITIL
It's not an excuse not to do your job.
Problem Management
What the heck is a Candidate Incident???? If you aren't sure, maybe you don't know your role or your environment!
Anyone can be a Problem Owner. Arbitrary organizational limits are nonsensical.
If you have tried the same rollout in Change Management that has repeatedly failed and impacted your customer, it is time to look to Problem Management
When you have a 'problem', does it make sense to send your problem manager home first?
CMDB
Best Practice is to get all of your crap in there, not just what is easy
Change Management and Change Control
If an auditor can't describe or measure the 'risk' they call out in your change control process, it isn't a risk
Removing a Standard Change Template because a Standard Change was canceled borders on moronic. Now, if a Standard Change fails - yep, remove the template.
Patching is a CHANGE dopey. It still needs Change Control.
Don't invoke Change blackout periods, fix your Change process. Learn to Test. If your deployment process sucks, fix it.
Incident Management
Incident Management process and platform should not be more complicated than the incidents themselves.
It is NOT a best practice to continually change the IM process without engagement. IM is a service that has customers, not a source of absolutes.
If the root cause of the issue is not explicitly known, opening the communication and discussion to a larger audience is the appropriate method.
ITSM
You don't get to change the process for friends
Problem tickets should not start with the solution. It should start with a description of the problem.
Just because you are certified, does not mean you know anything about your environment or how your business runs. It just means you passed a test. Ask a couple of questions before going off and writing unusable policies by yourself.
ITSM Communications
Read emails before responding to them. If three people on the same team respond without scrolling down - you all failed the IQ test
SaaS
Why on earth would you force anyone on the planet to go through Citrix to get to a SaaS app - ServiceNow no less. Does ITIL say that you should know nothing about IT to be in IT?
About Us
