In this organization template the asset governance is centrally funded and controlled. The asset repository and
management is also centrally funded and managed, implementing governance policies. But the asset production is
formalized in the respective communities, where the domain expertise resides. The reuse scope is at the community,
cross-community, and enterprise level. The domain experts from the communities produce the assets or work with asset
production teams in the communities. Those who produce the assets follow key assets into the context of the asset
consumers to help insure their success, as noted by the "support" line. The asset use is planned and opportunistic.
A key differentiator from this template and the Governed Community is the separation of asset production and asset
management. The functions around asset management require some overhead, and the organization can achieve some
efficiency by centralizing them. Meanwhile the asset production activities are benefited by staying within the
community, being close to the domain experts.
This template also promotes the use of asset experts helping asset consumers be successful with using the assets. Not
all assets require this, but when the reuse costs of key assets can be mitigated with proper support, then the value of
the asset and the repository is preserved, or perhaps increases.
In many situations there will be a modified structure from the one shown above. The enterprise will not all be on the
same, single organizational structure for the reuse scope, but rather it will be a mixture of templates as shown below.
In this example the central asset governance board provides the policies to the asset governance board in the modified
self-governed community. The central asset governance board also provides policies to one or more governed communities,
each of which manage their own repositories and asset production and the funding associated with them.
The example could be modified further to reflect migrations from the community repositories to the centrally managed
repository as well.
|