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

use parcolumns

This commit is contained in:
sessionm21 2019-12-06 21:56:28 -08:00
parent 87aef94282
commit 000352444c
1 changed files with 56 additions and 60 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

116
retrospective.tex
View File

@ -8,7 +8,7 @@
\usepackage{caption}
\usepackage{pgfgantt}
\usepackage{setspace}
\usepackage{longtable}
\usepackage{parcolumns}
\linespread{1}
\def \CapstoneTeamName{Automated Fenceless Grazing}
@ -248,67 +248,63 @@ responsibility for parts of each assignment.
% positives column: anything good that happened
% deltas column: changes that need to be implemented
% actions column: specific actions that will be implemented in order to create the necessary changes
\begin{longtable}{| p{.30\textwidth} | p{.30\textwidth} | p{.30\textwidth}|}
\hline
Positives & Deltas & Actions \\
\hline
\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.
&
\setlength{\columnseprule}{0.4pt}
\begin{parcolumns}[colwidths={1=0.3\textwidth}]{3}
\colchunk{
\subsection{Positives}
\emph{Week 3} This week included full completion of the requirements document rough 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.
\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.
\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.
\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.
\emph{Week 7} Design document has been fully completed and
submitted, fully packed with specific information on how we will
complete our project.
\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.
\emph{Week 9} We culminated our finalized work and sent it to our
client for review.
\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.
}
\colchunk{
\subsection{Deltas}
Eventually the project will need to be funded in order to get the hardware that is needed to prototype
the device that is the focus of this project.
& c \\
\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.
&
Document requirements need to be more thoroughly processed such that they satisfy all requirements as are appropriate.
& c \\
\hline
\pagebreak
\hline
Positives & Deltas & Actions \\
\hline
\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.
\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.
&
Across the team tasks need to be more evenly distributed and properly managed such that deadlines can be met in a more efficient manner.
& c \\
\emph{Week 7} Design document has been fully completed and
submitted, fully packed with specific information on how we will
complete our project.
& b & c \\
\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.
& b & c \\
\emph{Week 9} We culminated our finalized work and sent it to our
client for review.
& b & c \\
\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.
& b & c \\
\hline
\end{longtable}
Document requirements need to be more thoroughly processed such that they satisfy all requirements as are appropriate.
Across the team tasks need to be more evenly distributed and properly managed such that deadlines can be met in a more efficient manner.
}
\colchunk{
\subsection{Actions}
Add some text
}
\end{parcolumns}
\end{document}