Skip to main content

Checklists

Sprint Planning Preflight

  • There are enough topics/technologies so that everyone has something to do?
  • Sprint goal:
    • does not have external dependencies
    • can be achieved if any one developer is sick
    • has no topics which are too unclear/too dangerous to commit to

MR checklist:

  • Acceptance Criteria fulfilled
  • Potential security issues considered?
  • Code performance considered?
  • Potential API compatibility issues considered?
  • Integration test implemented if useful?
  • Documentation is up-to-date (javadoc, dev-tools, etc.)
  • How to test added if necessary
    • List of affected code paths (to avoid bugs in untested edge cases)
  • Manual tests done: