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

positives column

This commit is contained in:
Ryan Alder 2019-12-06 21:27:43 -08:00
parent cf2d81e586
commit 8843d1ecef
1 changed files with 46 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

61
retrospective.tex
View File

@ -31,7 +31,7 @@
\pagenumbering{gobble}
\begin{singlespace}
% 4. If you have a logo, use this includegraphics command to put it on the coversheet.
%\includegraphics[height=4cm]{CompanyLogo}
%\includegraphics[height=4cm]{CompanyLogo}
\par\vspace{.2in}
\centering
\scshape{
@ -46,7 +46,7 @@
{\large Prepared by }\par
Group\CapstoneTeamNumber\par
% 5. comment out the line below this one if you do not wish to name your team
\CapstoneTeamName\par
\CapstoneTeamName\par
\vspace{25pt}
}
\begin{abstract}
@ -58,7 +58,7 @@
changes to collars through an application built for Android mobile devices.
The MariaDB SQL database management system will be used to store the data
received from the collar for viewing and analysis.
\end{abstract}
\end{abstract}
\end{singlespace}
\end{titlepage}
@ -86,7 +86,7 @@ lends itself very well to division among the three group members, and all
team members' responsibilities have been explicitly defined and agreed upon.
The team members all successfully researched the components of the project that
they are responsible for, and their research has been incorporated into a thorough
design document.
design document.
Both the technical reviews produced by the individual team members and the
design document have been validated by the client, and there is consensus
@ -104,25 +104,25 @@ team members could meet with our client. As a result our interaction with our cl
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
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
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
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
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.
@ -178,7 +178,7 @@ is soon to be established. Each group member and the client provided the
times during which they are available, revealing that there were no
time slots during which each individual was available to meet. As such,
one of the group members will likely skip this meeting, and the rest
of the group members will fill them in.
of the group members will fill them in.
In preparation for the client meeting, team members have been doing further
research into their components of the project. This coincides well with the
@ -197,13 +197,44 @@ expectations were not significantly different.
% actions column: specific actions that will be implemented in order to create the necessary changes
\begin{tabular*}{\linewidth}{@{\extracolsep{\fill}}|p{0.3\linewidth}|p{0.3\linewidth}|p{0.3\linewidth}|@{}}
\hline
Positives & Deltas & Actions \\
\hline
\begin{itemize}
\item one
\item \emph{Week 3} This week included full completion of the requirements document rought draft and
we began merging our problem statements. The requirements document is very near
complete and we anticipate very little additional work to finish. Our team
reports good division of labour, and initial communication with client
went well.
\item \emph{Week 4} Good work has been put into researching the specific
hardware we will need for our project. Specifics into the protocol
and communication between modules has been decided on well prior
to the design document. Professor Hamdaoui is aware of our progress
and mentioned we are ready for funding. Lastly, we have completed
the requirements document and are pleased with our work on it.
\item \emph{Week 5} All team members have completed their tech reviews
with no problems to report. Our team met with our client, who was
pleased with our work so far and continued to mention funding, and
asked for some form of presentation in regards to our hardware
decisions.
\item \emph{Week 6} A biweekly meeting has been setup with our client
to discuss current status. All tech reviews have been completed,
and the meeting with our client went very well, with plans to talk
more in the future.
\item \emph{Week 7} Design document has been fully completed and
submitted, fully packed with specific information on how we will
complete our project.
\item \emph{Week 8} Design document has been sent to our client for
review. We are one step closer to funding as the question has been
posed to both our TA and the professors.
\item \emph{Week 9} We culminated our finalized work and sent it to our
client for review.
\item \emph{Week 10} We met with our client in regards to our submitted
documents. Our client, Professor Hamdaoui, was really receptive to
our work and is excited for us to get our hands on the hardware in
order to begin the actual project.
\end{itemize}
&
&
\begin{itemize}
\item two
\end{itemize}
@ -211,7 +242,7 @@ expectations were not significantly different.
\begin{itemize}
\item three
\end{itemize} \\
\end{tabular*}
\end{document}