Good Standing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
=For OSE Fellows= | =For OSE Fellows= | ||
Good standing for OSE Fellows involves | Good standing for OSE Fellows involves | ||
*Successful running of OSE Extreme Learning and Extreme Manufacturing workshops | *Successful running of OSE Extreme Learning and Extreme Manufacturing workshops - which means meeting the monthly participant training quotas as well as receiving a minimum of 3 of 5 star average reviews from participants. | ||
*Quarterly product release to 100% burndown on the product or enterprise aspects of a given project | *Quarterly product release to 100% burndown on the product or enterprise aspects of a given project | ||
=For OSE Developers= | =For OSE Developers= | ||
To remain in good standing, a Developer must complete 120 hours of effort in a 90 day period. For achieving this, the Developer gets a star on their badge. | To remain in good standing, a Developer must complete 120 hours of effort in a 90 day period. For achieving this, the Developer gets a star on their badge. | ||
Latest revision as of 19:02, 9 July 2018
For OSE Fellows
Good standing for OSE Fellows involves
- Successful running of OSE Extreme Learning and Extreme Manufacturing workshops - which means meeting the monthly participant training quotas as well as receiving a minimum of 3 of 5 star average reviews from participants.
- Quarterly product release to 100% burndown on the product or enterprise aspects of a given project
For OSE Developers
To remain in good standing, a Developer must complete 120 hours of effort in a 90 day period. For achieving this, the Developer gets a star on their badge.