Developer Engagement: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 9: | Line 9: | ||
=Scorecard= | =Scorecard= | ||
To help improve team performance overall, we have to track it - we do that here | To help improve team performance overall, we have to track it - we do that here: | ||
#% of Total Team who did work that logged hours | #% of Total Team who did work that logged hours | ||
| Line 15: | Line 15: | ||
#Of the people that logged, are they logging properly. | #Of the people that logged, are they logging properly. | ||
#% of Available Team that shows up to design sprint | #% of Available Team that shows up to design sprint | ||
#% of people who finish their task | #% of people who are allocated tasks | ||
#% of people who finish their allocated task | |||
=Scorecard Spreadsheet= | =Scorecard Spreadsheet= | ||
Revision as of 00:24, 30 August 2017
How do we know if a Developer is performing well. To assess developer engagement, the superior performers can be seen as:
- Has their Developer Test Score been verified?
- Are they meeting their weekly time quota at the 90% plus level?
- Have they posted a profile picture on the OSE Developers page?
- Did they set up their work log properly and do they have a 90%+ score on Work Log Checklist?
- Are they making regular and visible progress updates in their Work Log?
- Have they produced any instructional videos?
- Are they communicating on the email list?
Scorecard
To help improve team performance overall, we have to track it - we do that here:
- % of Total Team who did work that logged hours
- Of the people that logged, what % did their quota of 10%
- Of the people that logged, are they logging properly.
- % of Available Team that shows up to design sprint
- % of people who are allocated tasks
- % of people who finish their allocated task