... | ... | @@ -260,10 +260,10 @@ This table summarises the cadence or cycles of the main events of the Oniro Plat |
|
|
|
|
|
| Event | Cadence | Purpose | Group | Notes |
|
|
|
| ------ | ------ | ------ | ------ | ------ |
|
|
|
| Initiative.Evaluation | bi-weekly | Coordination, reviews and approvals | | |
|
|
|
| Initiative.Assessment | monthly | evaluation done by the Oniro WG SC on monthly basis of the proposed initiatives | | 10% of new features coming from the community |
|
|
|
| Initiative.Approval | bi-monthly | Strategic/pivoting functionalities reviewed, risks/opportunities evaluated | | |
|
|
|
| Release evaluation | on every major milestone | Feature delivered, tests passed, lessons learnt | | done by the Oniro WG SC based on the Roadmap Team report. |
|
|
|
| Initiative.Evaluation | bi-weekly | Coordination, reviews and approvals | Roadmap Team | |
|
|
|
| Initiative.Assessment | monthly | evaluation done by the Oniro WG SC on monthly basis of the proposed initiatives | Roadmap Team + Oniro WG SC | 10% of new features coming from the community |
|
|
|
| Initiative.Approval | bi-monthly | Strategic/pivoting functionalities reviewed, risks/opportunities evaluated | | Oniro WG SC |
|
|
|
| Release evaluation | on every major milestone | Feature delivered, tests passed, lessons learnt | Roadmap Team + Oniro WG SC + Owners + Sponsors | done by the Oniro WG SC based on the Roadmap Team report. |
|
|
|
|
|
|
These cadences should be shorten, when possible, by applying measures that partly move the process away from being committee driven into a more asynchronous approach.
|
|
|
|
... | ... | |