diff --git a/style.scss b/style.scss
index 4afe82e..edeb842 100644
--- a/style.scss
+++ b/style.scss
@@ -41,4 +41,5 @@ tr.nested-row {
section {
margin-bottom: 3em;
+ page-break-after: always;
}
diff --git a/teamreview.html b/teamreview.html
index 12ac9db..1e9eca1 100644
--- a/teamreview.html
+++ b/teamreview.html
@@ -18,30 +18,55 @@
| Responsibility for Alloted Work |
+ Ryan always completed the work assigned to him,
+ despite a busy schedule. His full schedule
+ meant that some work was done pretty late,
+ but this has not been a problem for the
+ group. |
| Timely Communication of Incomplete Work |
+ Ryan has not missed any assignments or projects.
+ Therefore, there has been no need to communicate
+ incomplete work. |
| Work Quality |
+ Ryan's work was always of good quality, and was
+ frequently directly added to the final
+ project without needed revisions. |
| Meeting Attendence |
| Presence in Meetings |
+ Ryan was unable to attend one of the meetings,
+ but otherwise was active and present. He spoke
+ a lot of the time in TA meetings. |
| Timely Notice of Absence |
+ Ryan notified us of the absence earlier in the
+ day, which was satisfactory for the low-stakes
+ TA meeting. |
| Meeting Preparation |
+ Ryan was active during all the meetings
+ with the TA and the client. He demonstrated
+ a consistent knowledge of the project,
+ and was alays able to answer questions. |
| Conflict Management (Civil Behavior) |
+ Ryan handled conflicts in a completely
+ approriatematter. |
| Other |
+ Work was distributed in a somewhat uneven fashion,
+ but this has been addressed in a discussion. |
@@ -61,30 +86,61 @@
| Responsibility for Alloted Work |
+ Matt completed all the work that he was
+ assigned. Since he is one of the few
+ people in the group who understand hardware,
+ his continued contributions were very valuable. |
| Timely Communication of Incomplete Work |
+ Matt did not miss any assignments or work,
+ and therefore did not need to communicate
+ about such things to us. |
| Work Quality |
+ Matt's quality of work was satisfactory,
+ though he particularly shone in researching
+ the hardware for the project, which was
+ done thoroughly and critically. |
| Meeting Attendence |
| Presence in Meetings |
+ Matt accidentally missed one meeting in the beginning
+ of the term, having accidentally double-booked
+ it with another commitment. This was not
+ a significant problem for us, and did
+ not repeat. |
| Timely Notice of Absence |
+ Matt's only missed meeting was unintented, and
+ thus, he was unable to notify us
+ of the absence. Since he missed no further work,
+ he did not need to further notify us of absence.
|
| Meeting Preparation |
+ Matt was exceptionally well-prepared for meetings,
+ being the only hardware-oriented person in the
+ group. He was able to easily answer the client's
+ and TA's questions, and had a clear understanding
+ of the design of the project as a whole. |
| Conflict Management (Civil Behavior) |
+ In the only "conflict" that occured in the
+ group, he communicated in a civil manner
+ and worked with other group members
+ to resolve the situation. |
| Other |
+ Work was distributed in a somewhat uneven fashion,
+ but this has been addressed in a discussion. |
diff --git a/teamreview.latex b/teamreview.latex
new file mode 100644
index 0000000..f022fdf
--- /dev/null
+++ b/teamreview.latex
@@ -0,0 +1,32 @@
+\documentclass{article}
+\title{Team Review}
+\author{Danila Fedorin}
+
+\begin{document}
+\maketitle
+
+The Fenceless Grazing Collar project aims to reduce the manual labor required from farmers to maintain large herds of livestock. It does
+so by providing a GPS-enabled collar, which, when placed onto livestock, enables farmers to monitor their location
+and enforce grazing boundaries through the use of auditory and electric stimuli. Additionally, the Fenceless Grazing Collar
+project aims to collect livestock grazing information, for use in visualization tools and data analysis. In addition
+to the collar, the project includes an API server and an Android application to manage the collars remotely.
+
+The feedback from other group members regarding my performance is not surprising; it appears as though my team members
+have given an accurate assessment of my contribution to the project. It was true that I did a significant amount of work, and,
+because I wanted to get an A in the class, my work was of the highest level of quality I could maintain. It's clear
+from the feedback I received that there are no negative feelings from any group members towards myself or other group members (otherwise, there
+would likely be a lot more effort put into trying to lower everyone else's grades). This is not surprising.
+Our team had, and continues to have, good communication, so it's pretty clear how each group member feels about the others.
+
+I think that I contributed a significant amount. I drafted the majority of the design document, since I was the only one to have properly
+read the entire IEEE specification. My requirements document was used for the group submission, and I made significant contributions
+to other group assignments in the class. I think my group members feel the same way, since one of them gave me a "gold medal emoji" on
+the evaluations, and the other spoke very well of my work and presence. Thus, I think the evaluations reflect
+the reality of my contribution pretty well, and neither "more" nor "less".
+
+Although I felt like a good team member last term, I also put in more work than I would have liked into the class. The Capstone
+is not my only commitment, and thus, I have a variety of other areas where my time can be spent. That isn't to say that
+I would like to cease contributing to the project whatsoever - I simply would like to reduce my portion of work to more
+closely match the 33\% ideal that our group has set.
+
+\end{document}