Add remaining weeks

retrospective.latex

@@ -188,7 +188,59 @@ research that the team will present to the client in the meeting.
 \subsection{Week 6}
 The highlight of this week was the first meeting with the client. This meeting
 was scheduled last-minute, but went very well. The team's plan and the client's
-expectations were not significantly different.
+expectations were not significantly different. To accomodate the team and
+the client's busy schedule, meetings were agreed to be bi-weekly, and made
+optional (to prevent wasted time in the event that no new information is
+required by the group). During this week, team members wanted to begin
+prototyping to accelerate the development and revision of an initial
+design. However, the issue of funding remained at this point; a team member noted
+"any kind of funding is a long way away" in their individual progress report.
+In retrospect, this was not a significant challenge at this time: many changes
+were made to the original design during the drafting of the Design Document,
+meaning that some purchased hardware might not have been used.
+
+\subsection{Week 7}
+During this week, the team completed an initial draft of the Design Document.
+This was not written in IEEE 1016-2009 compliant format, and generally
+consisted largely of information from the Tech Review. The team was aware
+of this, and planned to modify the document to be compliant to IEEE 1016-2009
+in the second draft. The first draft was submitted on time and with no other issues.
+
+Since the team was busy with the creation of the design (and the design document),
+the issue of funding was not significant at this time. The group member responsible
+for the hardware simulated some of the components of the initial design, in order
+to explore the implementation of the project. However, no significant insight
+was gained from this, with the exception of familiarity with the tooling.
+
+\subsection{Week 8}
+In this week, the design document was completely transitioned to IEEE 1016-2009 format.
+This took a significant amount of work for three reasons: the IEEE spec is very wordy
+and needlessly abstracted, the specified perspectives in the IEEE spec were not
+entirely covered by the first draft, and a medical emergency temporarily took out a team member.
+Despite the difficulties, the assignment was completed before the initial deadline (which
+was later postponed), and the team had a chance to verify the content of the design document
+with the course's instructors. This helped discover several minor issues with the format
+of the document, which were promptly corrected. At this point, the document was
+complete with the exception of UML diagrams, which were scheduled to be inserted
+during the weekened. 
+Other than the medical emergency and the design document, no significant problems
+or progress occured this week.
+
+\subsection{Week 9}
+This was a short week which ended in Thanksgiving, and no significant changes
+to the state of the project occured at this time. The team submitted all the
+generated documentation to the client / advisor, but did not receive a
+response during this week. No issues were encountered during this time.
+
+\subsection{Week 10}
+The entire team, as well as the client, had a chance to meet and discuss
+the submitted documents this week. The client was very satisfied with the results,
+but wanted a high-level overview of the system that was not "scattered through
+a big document".
+On the team level, a new system was introduced to help evenly distribute workload
+among team members. A Trello-style board will be used to plan for the tasks
+ahead and assign work to members, so that there is a larger degree of personal
+responsibility for parts of each assignment.
 
 \section{Retrospective}
 % TODO add retrospective