Please enable JavaScript.

Coggle requires JavaScript to display documents.

Continuous Software Engineering, Context - Coggle Diagram

- - - - (In)Experience with Tool
      - Reported knowledge of automation mechanism(s) and infrastructure configuration
      - Reported effectiveness of job feedback
      - Reported job weight in decision making
    - - Intra-task context switching
      - Developer/Module/Process Interactivity Matrix
      - Reported job skipping
      - Reported tendency to delegate to job
      - Reported description(s) of onboarding process
  - - - Incoming change velocity
      - Incoming change granularity
    - - Use of feature toggles as throttles
- - - - Not yet explored
    - - Commit frequency
      - Commit size/complexity
      - Frequency of broken commits
    - - Test execution strategy (parallel/serial/hybrid)
      - Types of testing conducted (reported and observed)
      - Test coverage
      - Test process complexity (external services/APIs/etc.)
    - - Pull/Merge request lifetime
      - Review depth/usefulness
      - Reviewer/Product manager's issue queue length
      - External reviewer required to sign-off on changes
    - - Release frequency
      - Release batch size
      - Hotfix release frequency
      - Reported fixing/hotfix/rollback procedures (includes degree of automation involved)
    - - Deployment frequency
      - Deployment batch size
      - Rollback/Fix/Hotfix deployment frequency
      - Reported developer deployment privileges
      - Reported role siloing between dev and ops
      - Reported rollback/fix/hotfix procedures
    - - Automation tool complexity (possible proxy?)
      - Reported ease of maintenance
      - Modules most subject to maintenance (reported and observed)
    - - Reported descriptions of onboarding process
      - Reported use of automation scripts
      - Scripts as documentation (see documentation)
    - - Frequency of job configuration issues
      - Job issue complexity (reported and observed)
      - Job issue granularity (reported and observed)
    - - Merge conflict frequency (reported/observed)
      - Nature of merge conflicts (reported and observed)
      - Issue post-merge idle time
      - Reported mainline locking procedures
      - Changess merged by developer or different person
  - - - Issue/Feature time to production
      - Issue/Feature throughput
      - Issue/Feature completion time (mediated by task complexity)
    - - Traceability
        
        Artifact Documentation (see Documentation)
        
        Artifact Linkage
        
        Issue to pull/merge request
        
        Issue to commit
        
        Pull/Merge request to commit
        
        Commit to job
      - Reported notification utility
      - Automated job status notifications
      - Reported knowledge of development process
      - Automated deployment status notifications