CS-46X/retrospective
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge branch 'master' of dev.danilafe.com:CS-46X/retrospective

Browse Source
This commit is contained in:
Danila Fedorin 2019-12-06 00:07:45 -08:00
commit dea9ee0e4b
1 changed files with 26 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
retrospective.latex
View File

@ -99,7 +99,32 @@ specified in the design document, work can begin on implementing an initial
prototype. prototype.
\section{Problems} \section{Problems}
% TODO describe any problems that have impeded our progress, with any solutions we have One of the few problems we had this term was difficulty scheduling meetings in which all
team members could meet with our client. As a result our interaction with our client was
minimal at times, and resulted in only a few meetings over the course of the term. While
this did not prove to be a significant blocker for our work, it did result in some necessary
clarification recently with our client in regards to our vision on how we planned to move forward.
We plan on fixing this problem by scheduling a biweekly meeting with our client at the beginning
of next term. The best way to ensure that our team can keep our client up to date is to have a
definite meeting time, and the best way to schedule this meeting would be as soon as all class
schedules have been finalized.
Another problem we encountered was lack of funding. While this was not an issue at the
beginning of the term, it is looking to be a serious blocker in the near future as our next step
the moment we get back from winter break is to purchase hardware. Ideally, this hardware would be
purchased prior to even returning to school to allow our team to start work on the physical
aspect of our project immediately. Our client has approved our hardware proposal, which was the
last step before purchasing. Our team has discussed this funding with our TA, who in turn has
brought it up to Professors Winters and Fairbanks. In an effort to ensure funding will be secured
as soon as possible, we will continue to follow up with our TA and the professors if necessary.
Our last small problem we came across was in regards to formatting for our different submissions.
One of our documents was incorrectly formatted as a result of our misunderstanding of the
requirements. Also, towards the beginning of the term we named our files incorrectly, resulting
in the loss of points. In order to ensure that all style guidelines are met in the future, we
will communicate with our TA, other students, and our professors as needed. Prior to asking
others, we will peruse the online documents provided to us on Canvas to ensure that we are
not asking questions that have already been answered.
\section{Weekly Progress} \section{Weekly Progress}
% TODO The document should include a detailed, week-by-week summary of activities, % TODO The document should include a detailed, week-by-week summary of activities,