Who takes the final decision as to when a functional change to a mainframe application is to be released for use?

Question

Options

• Aapplication management
• Bbusiness information management
• Ctechnical infrastructure management

• A
  4% (2)
• B
  86% (42)
• C
  10% (5)

Explanation

Business Information Management (B) holds the final release decision because functional changes exist to serve business needs - the business owns both the requirements and the risk/benefit tradeoff, so only they can authorize when a change goes live.

A (Application Management) is wrong because application teams are responsible for building and maintaining the application, not for deciding when it enters production use - that authority sits with the business, not the development/support function.

C (Technical Infrastructure Management) is wrong because infrastructure teams manage the platforms and environments that host applications; they have no mandate over business-driven release decisions for application functionality.

Memory tip: Think of it as "whose problem does this change solve?" Functional changes solve business problems, so the business (Business Information Management) gets the final word on go-live - the technical teams advise and enable, but never authorize on behalf of the business.

No community discussion yet for this question.