In this organization template the asset governance is centrally funded and controlled. The asset repository and
management is also centrally funded and managed. The asset production is also centrally managed, and domain experts
from the communities participate in the central production team. The reuse scope is at the community, cross-community
and enterprise level. In this organization template the experts from the centralized asset production team follow key
assets into the communities to help ensure success using the assets (as noted by the "support" line in the image). The
asset use is planned and opportunistic.
A key differentiator between this template and the Enterprise Partial template is the asset production activities are
centralized as well. To make an asset reusable, and to reduce the friction in reuse transactions, there often is some
packaging and other overhead activities required across assets. For certain kinds of assets, such as coarse-grained
solutions which comprises many assets it may be justified to centralize the production and packaging of the assets.
A challenge with this template is the asset production may be performed organizationally too distant from the domain
experts in the communities. This has be monitored closely and communication must be constant. The majority of the
asset-based development work, including the configuration of the repositories and the development of the assets must be
done within the context and purpose of positively impacting the asset consumers. Anything that causes a hurdle or a gap
to not understand the asset consumers clearly should be removed.
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.
|