21.2 Cross-Organizational Objects

Cross-organizational objects are artifacts produced and used across projects involved in product development and maintenance. These are mostly in the form of documents. Typically, high-level or cross-organizational units carry the responsibility for such objects, such as department management or a sales division. Many people use cross-organizational objects more or less independently of their roles in connection with product development and maintenance.

One or more responsible people must be appointed for cross-organizational objects. The objects may be divided into groups, for which different units carry the responsibility, as long as no object falls between two job responsibilities.

Configuration Management Considerations

It's uncommon for cross-organizational objects to be placed under configuration management. These objects are rarely used as the starting point for other objects, and changes do not often occur. It may, however, be a good idea to assess which objects are used by many people and at least place these under configuration management, so an old version can be re-created and so the history of the objects and reasons for changes will be accessible. It may also be useful to place high-level plans under configuration management, as a basis for documenting various courses of events.

Identification

It's important to define standards for unique identification so that it's clear which type of object one is dealing with. Clashes in unique identification must be avoided between cross-organizational configuration items and other items, such as other cross-organizational items, components for reuse, or product-specific items.

Storage

It may be useful to establish separate configuration management libraries for different types of cross-organizational configuration items (such as staff information, sales material, and business plans), under different people's responsibility. Cross-organizational items must under no circumstances be stored with items for specific products or components for reuse.

Change Control

No specific considerations apply to change control of cross-organizational items, apart from general principles. Configuration control board(s) may be difficult to form and to make function, but nevertheless, it's important to have board(s) that represent the relevant stakeholders.

Status Reporting

Status reports for cross-organizational items must be accessible to everybody with access to or an interest in the items. This may warrant access control for direct search in metadata, if many types of cross-organizational items are handled in the same place (e.g., using the same tool).



Configuration Management Principles and Practice
Configuration Management Principles and Practice
ISBN: 0321117662
EAN: 2147483647
Year: 2002
Pages: 181

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