Your approach to funding is a critical success factor for your asset management strategy. As you see in Figure 1, the funding strategies, from most to least desirable, are:
- Funded reuse/usage team. A team of one or more people in the role of asset engineer is provided explicit funding to support and enhance the reuse efforts within your teams
- Asset-level funding. Funding for a specific asset, such as a security framework or collection of physical tools, is explicitly budgeted for. This funding should cover the development, enhancement, and long-term support and maintenance of the asset.
- Team-based funding. Funding for the use, development, and enhancement of assets is included in the budget individual teams. Such funding is often accompanied by mandates along the lines of “The team will achieve X% levels of reuse” (although teams are rarely measured against these mandates in practice).
- No funding. With this approach (re)use occurs on an ad-hoc basis within teams, often driven by tactical decisions at the team level as opposed to strategic decisions at the organizational level.
- Chargeback. Teams are charged for usage of an asset. In some extreme cases teams are charged to download an intangible asset from the asset repository, typically because that’s easier to than charging for actual usage.
Clicking the diagram opens the interactive DA Browser where you can learn more about all goals, decision points and options of DA.
Table 1 compares and contrasts these funding strategies. Combinations of these strategies can of course be implemented.
Table 1. Comparing the reuse funding strategies.
Strategy | Advantages | Disadvantages | Considerations |
Funded reuse/usage team |
|
|
|
Asset-level funding |
|
|
|
Team-based funding |
|
|
|
No funding |
|
|
|
Chargeback |
|
|
|