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
  12% (5)
• B
  88% (36)

Explanation

BiSL's Management processes (covering areas like contract management, financial management, and supplier management) are scoped specifically to the ongoing, operational management of information provision services - not to one-time project initiatives. Large releases involve temporary project organizations governed by project management frameworks (such as PRINCE2), which exist outside BiSL's scope entirely. BiSL explicitly draws a boundary between "running" the information provision (BiSL's domain) and "changing" it through major projects (a separate project management domain).

Why A is wrong: Selecting "yes" conflates BiSL's Management processes with project management responsibilities. The fact that a release affects information services does not mean BiSL Management governs the project itself - only the eventual handover of results back into operational management falls within BiSL's remit.

Memory tip: Think of BiSL Management as the "keep the lights on" layer. When a whole new electrical system needs to be installed (a large release project), you bring in a separate construction crew - BiSL Management just takes over once the lights are back on.

No community discussion yet for this question.