|
This is the initial draft of Ground rules for engagement for R3 which we hope can be carried forward beyond R3 as well. It is important to balance Agility and Governance to deliver a working model for OSDU platform development.
|
|
This is the initial draft of Ground rules for engagement for R3 which we hope can be carried forward beyond R3 as well. It is important to balance Agility and Governance to deliver a working model for OSDU platform development.
|
|
|
|
|
|
1. Review and align on business drivers and relative priority – Force rank if required
|
|
1. Review and align on business drivers and relative priority – Force rank if required
|
|
|
|
|
|
- Work closely with OMC and the release workstream leads to pick out the ‘essence’ for a release
|
|
- Work closely with OMC and the release workstream leads to pick out the ‘essence’ for a release
|
|
|
|
|
|
1. Establish a clear definition of done across all contributors – [R2](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-(C)/Roadmap/OSDU-Release-2-Details/Done) example, [R3 proposed done](https://community.opengroup.org/osdu/platform/home/-/wikis/Planning/R3/Done)
|
|
1. Establish a clear definition of done across all contributors – [R2](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-(C)/Roadmap/OSDU-Release-2-Details/Done) example, [R3 proposed done](https://community.opengroup.org/osdu/platform/home/-/wikis/Planning/R3/Done)
|
|
|
|
|
|
1. Review and align on key Architecture Decision Records – [ADR examples](https://community.opengroup.org/groups/osdu/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name%5b%5d=ADR%3A%3AApproved)
|
|
1. Review and align on key Architecture Decision Records – [ADR examples](https://community.opengroup.org/groups/osdu/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name%5b%5d=ADR%3A%3AApproved)
|
|
|
|
|
|
- Engage Enterprise Architecture, Information Security and Data Definition sub-committees as required
|
|
- Engage Enterprise Architecture, Information Security and Data Definition sub-committees as required
|
|
|
|
|
|
1. Transparency in plans, deliverables, risks, changes, decisions, …
|
|
1. Transparency in plans, deliverables, risks, changes, decisions, …
|
|
- Build in an Open Source Environment based on community GitLab
|
|
- Build in an Open Source Environment based on community GitLab
|
|
- Work with program managers to conduct reviews to forum, OMC, PMC teams regularly
|
|
- Work with program managers to conduct reviews to forum, OMC, PMC teams regularly
|
... | | ... | |