The enterprise needs to define the assets that are most important and beneficial to track. Everything else should be in
support of that decision. The assets for the enterprise should provide value, they should be used, they should not sit
dormant in the repository, if so, they should be removed.
To accomplish this the Asset Governance Board needs to be created. This board, or boards, owns the responsibilities of
many of the decisions defining the assets and the repository.
With the reuse strategy and assessments created, now the attention should turn to identifying what is most important to
an enterprise.
One way to start this is to identify the areas in the software development process that need some productivity
improvements. Looking at the roles in the enterprise that need help, or consistency in their tasks and work
products are also places to look for assets to focus on.
Some enterprises take a top-down approach, and begin describing the development approach and environment to which
they want to migrate. To take this approach, determine the objectives of the assets you will be defining, governing,
and supporting. Some of this motivation and objectives should come from the Reuse Strategy document.
With that understood, next conduct the tasks in this section that will address how the repository should be
organized, what asset types should be used, and what workflows and review processes should be in place.
|