The attached pages are an attempt at documenting MIT Thalia teams processes during the software development lifecycle. What's documented is the current process the team is following along with some suggestions to enhance.
Please comment freely and contact me if I'm unclear or the intention isn't understood. I thought this could be helpful for future team members and for slight revisions as changes are made going forward.
Builds should be provided periodically during the course of a given Sprint. The rule of thumb has been to provide builds when major functionality/changes are completed. This has proven helpful, even giving QA builds early in the Sprint to get a jump on testing/feedback.
...