1.11 Business Requirements Oversight Committee (BROC)

 < Day Day Up > 



The BROC is established in order to meet, review, approve, and coordinate major projects that affect all enterprise business units and to establish project implementation schedules coordinated with other related enterprise project activities. The SPMO serves as facilitator of these meetings. The meetings are staffed by business leaders designated and empowered from the various segments of the company. The BROC has final review, approval, and disapproval authority for all proposed projects. Any proposed projects generally must meet all of the following criteria:

  1. The project must be correlated to a business need that requires such an application's integration or installation effort in order to perform this function.

  2. The project must positively impact corporate systems and users. Products or tools used for external customers or for revenue generation are not usually within BROC scope.

  3. The project must exceed a preset dollar limit, which will vary by enterprise. In most cases for mid- to large-sized companies, this amount is $50,000. The project must also provide services to a specific, defined business process or function.

  4. Internal corporate application systems are also placed under the same level of scrutiny and must submit to the BROC prioritization process for any of the following when costs exceed the preset limits:

    • Application version upgrade (major new release/upgrade)

    • New application to replace existing legacy system

    • Major new functionality in existing system(s)

    • Customization of standard application code

Although the BROC reserves the right to review other system changes, it does not normally review or prioritize bug fixes, patches, or minor enhancements/configuration changes to systems already in production. Generally, normal internal support processes are followed for these types of changes. The primary functions of the BROC are to gather and review new project requests.

All new application project requests that fall within the scope of the aforementioned criteria should be submitted to the BROC for review and approval. The project proposal submitted should follow the basic guidelines of the SEP methodology and, at a minimum, must include the following:

  • High-level business requirements

  • Proposed scope

  • Proposed schedule

  • Business unit budget for project

  • Justification

The BROC is also expected to review, prioritize, and approve projects. As projects are submitted for approval, they are reviewed for cross-functional integration between business units, along with determination of application architecture for enterprise systems.

All approved projects are to be given a priority for implementation. The BROC is responsible for determining project dependencies and risk. It is also required to review and approve internal IT-initiated projects as stated in Item 4 of the project criteria listed above.



 < Day Day Up > 



Managing Software Deliverables. A Software Development Management Methodology
Managing Software Deliverables: A Software Development Management Methodology
ISBN: 155558313X
EAN: 2147483647
Year: 2003
Pages: 226

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net