... | ... | @@ -2,7 +2,7 @@ This is the initial draft of Ground rules for engagement for R3 which we hope ca |
|
|
|
|
|
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
|
|
|
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
|
|
|
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)
|
|
|
- Engage Enterprise Architecture, Information Security and Data Definition sub-committees as required
|
|
|
1. Transparency in plans, deliverables, risks, changes, decisions, …
|
... | ... | |