• First draft of requirements document
  • Project synopsis (Jarryd/Kaleb)
  • Project plan (Jarryd)
  • Update the website to add the completed project synopsis (Kaleb)
  • Complete the project survey (Kaleb)
  • Process decision


  • Final draft of requirements document
  • Outline what the process entails (Bryon)
  • Submit the project plan (Jarryd)
  • Domain model
  • Pick a process metric (risk, SUMI score)
  • Update website with Domain Model, process metric, methodology (Kaleb)


  • Answers to the requirements questions
  • Feedback on the requirements document
  • Demo of current system


  • Lack of software engineering department deadlines might start to impact work output
  • Unknown non functional requirements (security standards, etc)