...
Reduce risk via phasing - sample a variety of less-critical things first
+1: [Dave]: I think the phasing of this was really well done, so props on that part. 😃
Keep scope to a minimum by moving some things as they are and not blocking on harder long-term solutions (e.g. Paragon, edx-platform CI)
Don’t try to clean up old junk, just move it and clean up later
Keep good notes and spreadsheets about what needs to happen.
One person doing the in-the-moment work, another to manage communications in the moment.
Create a cross-org slack channel for comms
well-written scripts to tackle individual aspects of the overall job, unix-style
swarming was good
Specialized scripts where each does one thing well was really nice.
Snapshot data
Makes it easier to build other tools using the data
Keeps history
Many communication channels with regular but not too many updates.
Slack (cross-org slack channel for comms)
e-mail to edX managers.
Stupid Questions beat Stupid Actions every time
click is awesome
...