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

Finalize team review

Browse Source
This commit is contained in:
Danila Fedorin
2020-01-07 18:13:57 -08:00
parent 52d4ed09cc
commit 799a676785
3 changed files with 89 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

56
teamreview.html
View File

@@ -18,30 +18,55 @@
</tr>
<tr class="nested-row">
<td>Responsibility for Alloted Work</td>
<td>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.</td>
</tr>
<tr class="nested-row">
<td>Timely Communication of Incomplete Work</td>
<td>Ryan has not missed any assignments or projects.
Therefore, there has been no need to communicate
incomplete work.</td>
</tr>
<tr>
<td>Work Quality</td>
<td>Ryan's work was always of good quality, and was
frequently directly added to the final
project without needed revisions.</td>
</tr>
<tr>
<td>Meeting Attendence</td>
</tr>
<tr class="nested-row">
<td>Presence in Meetings</td>
<td>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.</td>
</tr>
<tr class="nested-row">
<td>Timely Notice of Absence</td>
<td>Ryan notified us of the absence earlier in the
day, which was satisfactory for the low-stakes
TA meeting.</td>
</tr>
<tr>
<td>Meeting Preparation</td>
<td>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.</td>
</tr>
<tr>
<td>Conflict Management (Civil Behavior)</td>
<td>Ryan handled conflicts in a completely
approriatematter.</td>
</tr>
<tr>
<td>Other</td>
<td>Work was distributed in a somewhat uneven fashion,
but this has been addressed in a discussion.</td>
</tr>
</tbody>
</table>
@@ -61,30 +86,61 @@
</tr>
<tr class="nested-row">
<td>Responsibility for Alloted Work</td>
<td>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.</td>
</tr>
<tr class="nested-row">
<td>Timely Communication of Incomplete Work</td>
<td>Matt did not miss any assignments or work,
and therefore did not need to communicate
about such things to us.</td>
</tr>
<tr>
<td>Work Quality</td>
<td>Matt's quality of work was satisfactory,
though he particularly shone in researching
the hardware for the project, which was
done thoroughly and critically.</td>
</tr>
<tr>
<td>Meeting Attendence</td>
</tr>
<tr class="nested-row">
<td>Presence in Meetings</td>
<td>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.</td>
</tr>
<tr class="nested-row">
<td>Timely Notice of Absence</td>
<td>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.
</tr>
<tr>
<td>Meeting Preparation</td>
<td>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.</td>
</tr>
<tr>
<td>Conflict Management (Civil Behavior)</td>
<td>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.</td>
</tr>
<tr>
<td>Other</td>
<td>Work was distributed in a somewhat uneven fashion,
but this has been addressed in a discussion.</td>
</tr>
</tbody>
</table>