Integrate Changes

(Activity) for Tier: Sprint

PURPOSE

All code changes and associated unit tests must be integrated into the main source for the product. Proper code integration will ensure the code is placed within the proper repository, the appropriate code reviews have been performed, and the code is bi-directionally traceable to the statement of work. In doing so, we make certain the code meets established quality standards and supports customer/contractual expectations.

WHEN

Occurs once code is written and passes code review.

PARTICIPATING ROLES

• ACCOUNTABLE

  • Developer

• RESPONSIBLE

  • Developer

INPUTS

• Pull Request
• Product Integration Plan (PIP)

ENTRY CRITERIA

• Pull request policies have all been satisfied
• Pull request does NOT have any merge conflicts.

SUB-ACTIVITIES

1. Ensure Traceability to Statement of Work (SOW)

   • Ensure that the code change is linked to the correct work item within the current sprint.

2. Complete Pull request

   • Verify the pull request description has all instructions and checks completed.
   • Customize the merge commit message if directed to by team procedures or PIP.
   • Complete the Pull Request so branch edits are merged into the target branch.

3. Update Work Item / Board

   • Update relevant work item and/or move the work item to the correct lane on the project team’s board based on team procedures.
   • Close any associated tasking.

OUTPUTS

• commit to target branch
• Work Item
• Task Work Item

EXIT CRITERIA

Source code has been integrated into target branch.

NEXT ACTIVITY

• Perform Continuous Integration
• Review Architectural Conformance

SEE ALSO

• Vulnerability Score

Process Guidance Version: 10.4