Task: Conduct Recurring Problem Analysis
For a given problem evaluate and verify the problem exists across time, or projects, or locations.
Disciplines: Asset-Based Development
Purpose
To protect the organization's investments in Reusable Assets and to ensure that the proper assets are developed.
Relationships
RolesPrimary Performer: Additional Performers:
Outputs
    Main Description

    Developing a reusable asset generally requires additional effort and cost to the organization. The effort, and therefore its associated cost, is expended in preparing the asset's artifacts, creating supporting packaging material, such as documentation and guidance for the Asset Consumer, submitting the asset and preparing the metadata, and conducting reviews and approvals of the asset.

    Therefore, it becomes necessary to govern the asset creation process. A critical step in this governance is to understand what the recurring problems are that will justify the costs for developing a reusable asset.

    As asset ideas come forward, the organization should conduct recurring problem analysis to justify the development and long-term maintenance of the asset. This analysis may vary in rigor and formality depending on the nature and type of the proposed reusable asset.

    For example, a proposed asset to provide sorting of values in a list may likely have the recurring problem analysis handled informally amongst a development team or perhaps across several teams. In contrast, a tax calculation service will likely require more formal coordination and verification of the problem, its context and the proposed solution.

    Steps
    Identify Recurring Problem

    To understand the problem, the asset producer needs to understand the impact of the problem on the users. When defining the problem, define the context within which the problem exists. Explain the context in business terms and in technical terms. Also, verify the problem and its context exist in multiple places.

    Identify Common Solution to Recurring Problem

    The temptation is to focus on describing the solution before having a solid definition of the problem. Fight this tendency and don't spend significant time on this step until step 1 is completed.

    The proposed solution should be relevant to the problem's context and assumptions.

    Verify the Existence of the Problem and Solution in Multiple Places

    A rule of thumb from the patterns community is the problem/solution combination should be verifiable in three places in order for it to be a candidate for a pattern. While this is not being strictly prescribed here, it is a very reasonable guideline to follow.

    It is critical to evaluate the combination of the problem and the solution. In some contexts the solution to the same problem may vary slightly. It is possible to have multiple implementations, or solutions, to the same problem. The variance is caused by changing contexts, target Asset Consumers and delivery channels for the assets.

    More Information