|
Rating | |||||||||||
1 Horrible |
2 Bad |
3 Poor |
4 Below Average |
5 Average |
6 Above Average |
7 Good |
8 Very Good |
9 Superb |
10 Excellent |
|||
Did not respond to arbitration or was uncooperative |
x | |||||||||||
Did not complete project / lost arbitration | x | x | x | |||||||||
Completed project | x | x | x | x | x | x | x | |||||
Communication skills were good...requests were clear | x | x | x | x | x | x | ||||||
Hands on--made time during the project to provide feedback on questions and guide the project | x | x | x | x | x | |||||||
Accurate / Decisive: Answered questions thoroughly, accurately and completely | x | x | x | x | ||||||||
Stayed within specs (or paid extra for work outside of specs) | x | x | x | x | ||||||||
Understood and respected the principle of the software development triangle* | x | x | x | |||||||||
Accepted work promptly once fully completed | x | x | ||||||||||
Was open to suggestions from the coder | x |
*The principle of the software development triangle states that any project had three parts (like 3 sides to triangle). They are:
A buyer who puts
pressure on one or more of the 3 sides (for example, adds features), must allow
the coder to increase one of the other sides (give the coder more time or give
the coder more resources). Failure to do this shows a lack of respect for
the principle of the triangle.