Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Things We Should Keep Doing

  • (SPH) New sub-task approach seems to work very well.
  • (JJKP) I enjoyed sitting in B23 one day/week. It led to some good working discussions.
  •  (TGG)  automated regression testing continues to pay off, especially automation of system GUI tests.
  • (JJKP)  Working more closely with missions has been very successful.

Things We Should Change

Do Better

...

  • (DJC) As an addition to this, we could have simplified the code freeze piece by merging into production before building RC1, and then doing all testing and RC fixes in the production branch, rather than making the RC's off of master with a merge after the release was complete.  Ongoing work could then proceed in master with no code freeze needed, and production would contain only contain the RC's and the final release.  This would require some adaptation in the test and build systems.

...

  • (SPH)  Make sure nothing slips throught the cracks
  • (SPH)  Send out status reports of what issues are being encountered and who is working them.
  • (SPH)  Assuming we don't go to a more agile release process, and we keep a large annual release schedule, we probably need to define a few higher level roles with clear responsibilities.    Release manager,  build packager, script test lead, GUI test lead, triage lead, and those key people need to be available and in the office during release staging.   Backups should have gone through process successfully.
  • (SPH) Consider having developers build installers.  Engineers have lots of testing/analysis to do during RC phase so taking this off their plate would help.
  • (JJKP) Some proposed role definitions:
    • Release Manager (RM): "owns" release, initiates process, creates tracking page, sends daily status updates, tracks issues to completion, makes sure everyone gets their stuff done, brings decisions to CCB/team, maintains tracking page, collects lessons learned, documents process improvements for next release
    • Build Manager (BM): controls build system, creates RCs, sends RC availability announcements
    • Test Managers (TM): control GUI/script testing for each RC

...

Start Doing

...

  • beta period before release
  • more rapid releases

...

Stop Doing

...