OSE Developers: Difference between revisions
No edit summary |
No edit summary |
||
Line 5: | Line 5: | ||
The OSE Developer is the highest status given to OSE collaborators, marking the official development team that is working actively on the [[OSE Roadmap]]. Otherwise, ad-hoc contributors are welcome to contribute to the [[OSE Wiki]], the official development platform of the OSE project. | The OSE Developer is the highest status given to OSE collaborators, marking the official development team that is working actively on the [[OSE Roadmap]]. Otherwise, ad-hoc contributors are welcome to contribute to the [[OSE Wiki]], the official development platform of the OSE project. | ||
Development Teams must include a [[Heavyweight Product Manager]], a [[Product Owner]], and a [[Process Manager]] to steward a [[Concurrent Engineering | Development Teams must include a [[Heavyweight Product Manager]], a [[Product Owner]], and a [[Process Manager]] to steward a [[Concurrent Engineering]] process. Development teams should have 12-24 people to show clear and visible development velocity. Development Sprints are run on a quarterly basis (90 days), with the intended outcome being a product release. If OSE Developers are required to contribute 10 hours per week, then the 12 person team is effectively a 3-person full time equivalent. This is the minimum required for significant progress. Once a high-performing team is established, new teams may form. The minimum for starting any development team is 12 OSE Devs. |
Revision as of 22:58, 29 December 2016
OSE Developers are those individuals who are part of the OSE Engineering or Documentation Teams. OSE developers commit a minimum of 10 hours per week to a coordinated development process on key OSE priorities. The duration of this team effort is 90 days, at which point OSE Developers have an option to continue to increase their team reputation.
OSE Developers are selected for participation pending an application. The application process is maintained by the HR Team, and the onboarding process is shown at the HR Operations Manual.
The OSE Developer is the highest status given to OSE collaborators, marking the official development team that is working actively on the OSE Roadmap. Otherwise, ad-hoc contributors are welcome to contribute to the OSE Wiki, the official development platform of the OSE project.
Development Teams must include a Heavyweight Product Manager, a Product Owner, and a Process Manager to steward a Concurrent Engineering process. Development teams should have 12-24 people to show clear and visible development velocity. Development Sprints are run on a quarterly basis (90 days), with the intended outcome being a product release. If OSE Developers are required to contribute 10 hours per week, then the 12 person team is effectively a 3-person full time equivalent. This is the minimum required for significant progress. Once a high-performing team is established, new teams may form. The minimum for starting any development team is 12 OSE Devs.