Implement Solution Architecture

(Activity) for Tier: Product

View Training

PURPOSE

This activity initiates and provides ongoing support to the implementation of architectural changes. Products are instantiations of a solution architecture in which the descriptions and diagrams that compose the solution architecture are replaced with real world organizational processes, hardware, and executable software in order to create a functioning system. Once the team has made a commitment to implement an updated architecture the team must follow through to ensure that the structures and patterns prescribed by the architecture are reflected in future development work. In some cases, they may also be applied to existing system components.

WHEN

A team commitment has been made to an updated solution architecture.

PARTICIPATING ROLES

ENTRY CRITERIA

Solution Architecture

SUB-ACTIVITIES

  1. Propose New Product Backlog Items as Needed

    • Determine how revisions in the architecture will be implemented in the actual product.
    • In most cases implementation is accomplished by building current and future product backlog items in a way that conforms with the patterns, interactions, and structures described in the architecture. In this case no new product backlog items need to be proposed.
    • In some cases, the revised architecture may call for creation of components that act as product infrastructure. When feasible, this work should also be accomplished while implementing future functional product backlog items that will make use of the infrastructure. In some circumstances the team, in accordance with team established criteria, may determine the scope, size, or complexity of the development effort required is best handled by the introduction of one or more new items into the Product Backlog.
    • In some cases, the revised architecture must be applied to existing product components in order to solve identified architectural concerns. The decision on if, when, and how to transition existing system components to the revised architecture is made on a case by case basis by the team in accordance with team established criteria. New product backlog items are proposed as needed based on these decisions.
    • In those cases, where the team determines new product backlog items are needed, initiate the creation and addition of those items in accordance with team norms and standards.
    • As needed, create or update team norms and standards for making architecture implementation decisions.
    • As needed, create or update team criteria for when product backlog items that implement architectural requirements directly are justified.
    • As needed, create or update team criteria for determining when to retroactively apply architectural changes to existing product components .
    • As needed, create or update team norms and standards for adding items to the product backlog that implement solutions to identified architectural concerns.

  2. Obtain Approval for Changes in Configuration Controlled Items

    • Create a Change Request in accordance with team norms and standards when needed. This is only required if implementing the revised solution architecture requires making a change in an item identified as under configuration control in the team’s Configuration Management Plan .
    • If the Change Request is not approved, decide in accordance with team norms and standards if the Create Conceptual Solutions activity should be re-initiated or if the originally identified architectural concern should be closed without being addressed.

EXIT CRITERIA

  • (Elective) Product backlog item. (should include: description of work needed to address architectural concerns)
  • (When Required) Change request (against the solution architecture).

SEE ALSO

NEXT ACTIVITY

Process Guidance Version: 10.4