Line 1: |
Line 1: |
− | == 1. Terms of Reference == | + | == Terms of Reference == |
| | | |
− | === 1.1 Scope === | + | === Scope === |
| The GC MVBA Sub-Working Group is a “task force”-type endeavor under the GC Business Architecture Community of Practice (GC BA CoP) focused on the development of a proposed minimal viable business architecture practice in a GC context. Resulting work product will be brought in front of the GC BA CoP for consultation on its content and next steps. | | The GC MVBA Sub-Working Group is a “task force”-type endeavor under the GC Business Architecture Community of Practice (GC BA CoP) focused on the development of a proposed minimal viable business architecture practice in a GC context. Resulting work product will be brought in front of the GC BA CoP for consultation on its content and next steps. |
| | | |
− | === 1.2 Mandate === | + | === Mandate === |
| The objective of GC MVBA SubWG is to define and document a proposed '''''Minimum Viable Business Architecture Practice''''' in the GC context – a business architecture ''common denominator'' that would apply to small, medium and large Organizations across the GC. | | The objective of GC MVBA SubWG is to define and document a proposed '''''Minimum Viable Business Architecture Practice''''' in the GC context – a business architecture ''common denominator'' that would apply to small, medium and large Organizations across the GC. |
| | | |
− | ::'''1.2.1 Output''' | + | ::'''Output''' |
| | | |
| ::The proposed MVBA will be inserted into the GC Business Architecture ''Playbook'', a best practice / guidance-type reference published by TBS. GC organizations would be able to adopt the MVBA in part or as a whole and at their own pace. The GC Business Architecture Playbook and overall practice could be revised based on the GC MVBA proposition. | | ::The proposed MVBA will be inserted into the GC Business Architecture ''Playbook'', a best practice / guidance-type reference published by TBS. GC organizations would be able to adopt the MVBA in part or as a whole and at their own pace. The GC Business Architecture Playbook and overall practice could be revised based on the GC MVBA proposition. |
| | | |
− | ::'''1.2.2 Expected Outcomes''' | + | ::'''Expected Outcomes''' |
| | | |
− | ::* Increase the consistency of business architecture across the GC to favor collaboration and reuse among business and enterprise architecture stakeholders. | + | ::* Increase the consistency of business architecture across the GC to favour collaboration and reuse among business and enterprise architecture stakeholders. |
| ::* Accelerate the establishment of a valuable and sustainable business architecture practice in smaller / less mature GC Organizations and across the GC as a whole. | | ::* Accelerate the establishment of a valuable and sustainable business architecture practice in smaller / less mature GC Organizations and across the GC as a whole. |
| | | |
− | === 1.3 Membership === | + | === Membership === |
| | | |
| * Membership is comprised of organically-assembled members of the GC BA CoP. | | * Membership is comprised of organically-assembled members of the GC BA CoP. |
Line 55: |
Line 55: |
| Melissa Chow (SSC) | | Melissa Chow (SSC) |
| |} | | |} |
− |
| |
| | | |
− | === 1.4 Operations === | + | === Operations === |
| | | |
− | * The GC MVBA SubWG [CJ(8] [B9] will meet every 6-8 weeks. The group may call for ad hoc meetings on an as per need basis. | + | * The GC MVBA SubWG will meet every 6-8 weeks. The group may call for ad hoc meetings on an as per need basis. |
− | * The GC MVBA SubWG will be advancing its work through individual task assignment and secretarial coordination, in parallel of its meetings. A[CJ(10] ctivities and tasks will be managed and tracked through a centralized task list. [Insert link to the Task list] | + | * The GC MVBA SubWG will be advancing its work through individual task assignment and secretarial coordination, in parallel of its meetings. Activities and tasks will be managed and tracked through a centralized task list. [Insert link to the Task list] |
| * The agenda will be provided at least five business days in advance of meetings. | | * The agenda will be provided at least five business days in advance of meetings. |
| | | |
− | === 1.5 Secretariat Services === | + | === Secretariat Services === |
| The GC MVBA SubWG is self-managed on a best effort mode. Secretariat services will be provided by the sitting Chair and will include the following services: | | The GC MVBA SubWG is self-managed on a best effort mode. Secretariat services will be provided by the sitting Chair and will include the following services: |
| | | |
Line 71: |
Line 70: |
| * General oversight of the direction and delivery of the SubWG | | * General oversight of the direction and delivery of the SubWG |
| | | |
− | === 1.6 Terms of Reference Approval and Review === | + | === Terms of Reference Approval and Review === |
| The Terms of Reference will be approved by the sub-Working Group members and will be reviewed once a first version of a GC MVBA is delivered, so that the SubWG can be expanded, extended, reshaped or discontinued. | | The Terms of Reference will be approved by the sub-Working Group members and will be reviewed once a first version of a GC MVBA is delivered, so that the SubWG can be expanded, extended, reshaped or discontinued. |
| | | |
| | | |
| | | |
− | == 2. Past and upcoming sessions == | + | == Past and upcoming sessions == |
| {| class="wikitable" | | {| class="wikitable" |
| !Date | | !Date |