Technology Deployment Requirements

Whenever we introduce a new (instance of a) technology to the environment, we're obliged to do at least the following:

  • document the rationale and authorization
  • document how to build/buy one
  • document how our clients are expected to operate it
  • document evergreen data (cost + lifetime)
  • plan for how it will be fixed when it breaks
    • document common problems and their resolution (if known)
    • provide sufficient ready expertise for support
      • document that in the Who Does What list
      • budget expected staff time for the support
  • update DNS appropriately
  • update inventory data appropriately
  • update edocs appropriately
  • arrange for monitoring of the functionality the technology will provide
  • plan for any kind of relevant backups
Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2013-01-02 - BillInce
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback