Releases of large changes are often executed in a separate project with a separate project team. Are BiSL's Management processes also responsible for the management of these projects?

Question

Options

• Ayes
• Bno

• A
  13% (5)
• B
  88% (35)

Explanation

BiSL's Management processes (such as Planning & Control, Financial Management, and Demand Management) govern the ongoing functional management organization - they oversee the day-to-day delivery of information services, not the governance of separate change projects. When a large release is executed as a distinct project with its own project team, that project falls under project management governance (e.g., PRINCE2 or a similar methodology), which operates independently from BiSL's Management layer. BiSL's role in such projects is limited to functional involvement - like specifying requirements or accepting deliverables - not managing the project itself.

Why A is wrong: Choosing "yes" confuses the scope of BiSL Management processes with project management. BiSL manages the functional management organization; it does not take on responsibility for separately structured project organizations simply because those projects relate to information systems.

Memory tip: Think of BiSL Management as managing the lights-on organization - steady-state operations and services. Large change projects are like a temporary construction crew working next door; BiSL may interact with them, but it doesn't run their project.

No community discussion yet for this question.