Product/Project Grasp |
|
| Developed a clear vision of the end-user |
1
2
3
4
5 |
| Developed an accurate vision of the end-user |
1
2
3
4
5 |
|
Helpful at refining product/project goals
|
1
2
3
4
5 |
Architect (technical characteristics) |
|
|
As an overall systems architect
|
1
2
3
4
5 |
|
As a software-specific architect
|
1
2
3
4
5 |
|
Knows and respects his own limitations
|
1
2
3
4
5 |
|
Can understand and fairly balance multiple technical issues
|
1
2
3
4
5 |
|
Is technically consistent and coherent
|
1
2
3
4
5 |
|
Communicates architecture appropriately, effectively
|
1
2
3
4
5 |
|
Is open to/encourages team-driven architecture
|
1
2
3
4
5 |
Team Impact |
|
|
Honest representative (for team to management)
|
1
2
3
4
5 |
|
Listens well
|
1
2
3
4
5 |
|
Handles conflict well
|
1
2
3
4
5 |
|
Encourages team communication
|
1
2
3
4
5 |
|
Good decision maker for team
|
1
2
3
4
5 |
|
Helps the team come together
|
1
2
3
4
5 |
Business Characteristics |
|
|
Focused (respects engagement goals and boundaries)
|
1
2
3
4
5 |
|
Reliable (does what he says he will do)
|
1
2
3
4
5 |
|
Adaptable (good to work with as things change)
|
1
2
3
4
5 |
|
Timely (meets due dates)
|
1
2
3
4
5 |
Personal Characteristics |
|
|
Integrity (means what he says, says same to all)
|
1
2
3
4
5 |
|
Fun, energetic (enjoyable to work around)
|
1
2
3
4
5 |
|
I'd like to have a beer with him someday
|
1
2
3
4
5 |