The following two scenarios are likely to occur to teams working on their product deliverable. Each scenario has its own workflow. The first scenario is a simple fix and does not require a product change. The second scenario is a replacement and requires a branch creation and replacement.
GPS fix
A team is working on the first release of a GPS configuration and runs into a problem with the touch screen digitizer. The team performs an analysis of the touch screen digitizer child product to find out which artifacts are associated with the product. The team needs to know what artifacts must change to support the fix. The impact analysis results diagram shows all associated artifacts. The team updates the associated artifacts--the work items, requirements, design models, and test cases, by opening the artifacts from the analysis results. The team continues to work on the GPS product without changing the product structure.
Reflector replacement
A team is working on the bike configuration that was recalled for safety because the reflector on the back wheel falls off. The reflector is attached with adhesive, but needs to be reworked to be attached by a screw.
The wheel product has a child product called reflector, and reflector has a child product called adhesive. The team knows that the reflector product is used in other bikes.
The team lead performs a Find Use operation to create a list of other bikes that use the reflector product. The lead might look at the history to find a contact for the other bike teams. The team notifies the other bike teams about the fix.
The team lead performs an analysis of the reflector child product to find out which artifacts are associated with the product before they begin updates to the associated artifacts.
The team lead checks out a branch called reflector (affix=screw) with a new screw child product and then performs a replace branch operation.
The following steps use the Reflector replacement scenario.