Skip to content

Technical Debt Stand down

John Holt edited this page Jul 26, 2018 · 24 revisions

A technical debt stand-down day is a day devoted to fixing technical debt in the system. The format is:

  1. Choose a day where most people are free
  2. Choose a topic: examples
    • Squish tests
    • Eclipse/CSS interaction
    • Tech debt tickets
    • Block server exception handling
    • Deployment/release process
      • Automatically add release numbers based on the name of the release branch
      • On install if only one component is release then fall back to later components e.g. if only 4.4.1 GUI is available install 4.4.0 server and genie_python
    • Bugs
    • Emulator/IOC tests
    • Excess logging
    • Dataweb/dashboard improvements

People pick up tickets when they get in often working in pairs. There is an extra standup at 4pm to discuss what has been done. This is the moment to choose to either:

  • stop working on a ticket (commit everything to a branch and add it to the ticket to be picked up later)
  • move it into the current sprint
  • ensure a ticket is reviewed

Try to make sure all tickets by the end of the day are in a good state.

Clone this wiki locally