I suggest focusing SOW 1 primarily around an "active" code review designed to increase our knowledge of the code and confidence in running and refactoring it. By "active," I'm referring to tasks that produce useful deliverables while exposing code structure.

I'm choosing a due date that allows for pre-existing commitments on the part of Sourcery staff and contracts and also allows time for staffing the project. Work will commence as soon as this SOW is approved by Radiasoft, and it's possible this iteration could finish sooner than the due date if our work mix and staffing allows.