|P is for Practical|
> that potentially leaves you with other teams in the mix (say a database management and operations teams).
Almost true in my case. Unfortunately, there are no real database teams per se. The hardware team looks after hardware, makes sure the os is up and the capacity is ok. Beyond that, it is considered 'application' and out of their remit.
Because of that, I tend to get a little more say in the stuff that I do. I'm also lucky that most of what I do is internal to the business. However, as an international business we have 24 hour access requirements. This is where our SLAs come into play.
Downtime is inevitable but is generally mitigated as much as possible. I don't really mention it as downtime is a lot rarer for my work.
> As you mention DNS it sounds like web development
That is part of my work but i used DNS as an easy to understand example of not choosing a fixed time for launches.
Thanks for your comments :)