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

Finish initial draft of columns

Browse Source
This commit is contained in:
Danila Fedorin 2019-12-06 22:25:30 -08:00
parent 000352444c
commit 8027596daf
1 changed files with 38 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
retrospective.tex
View File

@ -243,6 +243,7 @@ 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.
\pagebreak
\section{Retrospective}
% TODO add retrospective
% positives column: anything good that happened
@ -252,59 +253,79 @@ responsibility for parts of each assignment.
\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
\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
\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
\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
\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
\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
\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
\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
\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.
The product still needs to acquire funding from Senior Capstone. Collars make up a big part of the
Fenceless Grazing System, which are entirely implemented using embedded hardware, and the client
wants to have a functioning collar prototype by the end of the year. As such, funding is needed
to purchase components for the collars, as well as for the API server that will power the Android
application component of the project.
Document requirements need to be more thoroughly processed such that they satisfy all requirements as are appropriate.
The team must do a better job of understanding the CS46x-specific requirements for each document. Quite some
points were lost on the assignments, in ways that were not anticipated.
Across the team tasks need to be more evenly distributed and properly managed such that deadlines can be met in a more efficient manner.
The team must change the means of distributing tasks. The method used in this term,
which was heavily based on individual initiative, led to an improper distribution of
work and time.
}
\colchunk{
\subsection{Actions}
In order to secure funding, we will directly reach out to Dr. Winters at the beginning
of the next term.
Add some text
To address the issue of misunderstood assignments, the team will aim to complete
them a week before they are due, when possible. This way, an individual appointment
can be scheduled with Dr. Winters, and feedback can be acquired on existing drafts.
In order to make sure that the assignments are done a week before they are due,
the new work-mangement system (described below) will be used.
The poor distribution of work will be solved by using task-management software, and
assigning team members to individual tasks. The team anticipates using Trello
for this purpose (or alternatively GitHub projects). A team member will be chosen
to assign and manage tasks. This way, a specific person will be responsible for
assigning tasks, rather than relying on initiative like was done before. Assigning
team members to individual task will serve the same purpose.
}
\end{parcolumns}
\end{document}