Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 13 Next »

DoD for a typical User Story

  1. Code reviewed and Merged
  2. Release Notes updated
    1.  Add Jira reference to relevant section ('Features'). The slogan does NOT have to be identical to the Jira, it often could/should be a better  description of the change
    2. Highlight backward incompatible changes if applicable
  3. Latest Yaml files copied to /docs folder (see step2 on CPS Release Process)
  4. Acceptance Criteria of the User Story have been met
  5. New functionality Demoed to Team and Stakeholders
    1. Uploaded recording of demo to CPS User Story Demos

Additional checks for a Bug

  1. Consider cherry-pick for previous release(s)
  2. Add Jira reference to relevant section in read the docs (RTD) ('Bug Fixes' and possibly 'Security Notes'). The slogan does NOT have to be identical to the Jira, it often could/should be a better  description of the change

  3. Complete an Fault Slip-through Analysis (FSA) and add as a comment in Jira

  4. Agree with Customer the FSA especially if there are any follow-up actions needed BEFORE closing the bug

     FSA Comment Template

    Fault Slip Through Analysis

    • Bug Category: <choose option>
    • Reason for Slippage: <choose option>
    • Action needed to prevent slippage: <free text>
    • Phase it should have been found in: <choose option>
    • Category of test it should have been found in: <choose option>
    • Description of test it should have been found in: <free text>
    • Link(s) To JIRA improvement record:  <free text>
     FSA Fields and Options
    1. Bug Category:

      1. 3PP

      2. Critical Vulnerability

      3. Documentation

      4. Functional

      5. High Availability

      6. Install

      7. Logging

      8. Performance

      9. Robustness

      10. Rollback

      11. Scalability

      12. Security

      13. Testware/CI

      14. Upgrade
    2. Reason for Slippage: 
      1. Insufficient test coverage
      2. Intermittent Fault/Timing Issue
      3. Missed impact
      4. Missed in code review
      5. Missed in design analysis
      6. Missed in document review
      7. Missing requirement
      8. Unrealistic Development timeframe
      9. Late requirement: insufficient analysis
      10. Environment
    3. Action needed to prevent slippage: <free text>
    4. Phase it should have been found in: 
      1. Design
      2. Review
      3. Automated (unit) Test
      4. Microservice CI (CIST)
      5. Release
    5. Category of test it should have been found in:
      1. Unit
      2. Integration Test
      3. Performance
    6. Description of test it should have been found in: <free text>
    7. Link(s) To JIRA improvement record: <free text>
      (ensure there are linked JIra's for any follow-up/preventive actions)



  • No labels