Difference between revisions of "Business Architecture/MVP Sub Working Group"
Jump to navigation
Jump to search
(Added a Terms of Reference) |
m (→Operations) |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Terms of Reference == | == Terms of Reference == | ||
| − | === | + | === 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. | ||
| − | === | + | === 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. | ||
| + | ::'''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. | ||
| − | |||
| − | ''' | + | ::'''Expected Outcomes''' |
| − | * Increase the consistency of business architecture across the GC to | + | ::* 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. |
| − | === | + | === 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 92: | Line 55: | ||
Melissa Chow (SSC) | Melissa Chow (SSC) | ||
|} | |} | ||
| − | |||
| − | === | + | === Operations === |
| − | * The GC MVBA SubWG | + | * 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. | + | * 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. | ||
| − | === | + | === 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 108: | Line 70: | ||
* General oversight of the direction and delivery of the SubWG | * General oversight of the direction and delivery of the SubWG | ||
| − | === | + | === 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. | ||
| + | |||
| + | |||
| + | |||
| + | == Past and upcoming sessions == | ||
| + | {| class="wikitable" | ||
| + | !Date | ||
| + | !Key Area of Discussion | ||
| + | !Presentation | ||
| + | |- | ||
| + | |2022-11-15 | ||
| + | |'''Session 4''' | ||
| + | * | ||
| + | | | ||
| + | |- | ||
| + | |2022-09-20 | ||
| + | |'''Session 3''' | ||
| + | * | ||
| + | |[[:File:GC MVBA WG 2022-09-20 RoD.docx]] | ||
| + | [[:File:2022-09-20 Minimal Viable EBA GC BACoP.pptx]] | ||
| + | |||
| + | * | ||
| + | |- | ||
| + | |2022-07-26 | ||
| + | |'''Session 2''' | ||
| + | * | ||
| + | |[[:File:2022-07-27 Meeting Notes - GC Business Architecture Sub Working Group.pdf]] | ||
| + | |- | ||
| + | |2022-05-25 | ||
| + | |'''Session 1''' | ||
| + | * Introductions and expectations for this new sub-working group. | ||
| + | |[[:File:GC MVBA WG 2022-05-25 RoD.docx]] | ||
| + | |- | ||
| + | |2022-04-25 | ||
| + | |'''Kick Off''' | ||
| + | * Exploration - Minimal Viable Enterprise and Business Architecture Practice | ||
| + | |||
| + | (See "Discussion" tab for more information) | ||
| + | |[[:File:2022-04-25 Minimal Viable EBA GC BACoP.pptx]] | ||
| + | |} | ||
Latest revision as of 09:34, 15 January 2024
Terms of Reference
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.
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.
- 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.
- Expected Outcomes
- 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.
Membership
- Membership is comprised of organically-assembled members of the GC BA CoP.
- Membership is now closed so that the sub-Working group can focus on developing its work package.
- Members of the GC MVBA Sub-WG are as follow:
| Organization | Name |
| CIHR | Adam Eikenberry |
| CSA | Nadine Beaudin |
| CSC | James Cameron |
| DFO | Kareim Elattar |
| DND-CAF | Steven Bednikoff (Chair) |
| PSPC | Roy Acres (PSPC)
Anne Beausoleil (PSPC) Johanne Bottrill (PSPC) (to confirm) Len Parliament (PSPC) |
| SSC | Lily Au (SSC)
Melissa Chow (SSC) |
Operations
- 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. 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.
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:
- Agenda development;
- Administrative and logistical support for meetings and/or teleconferences, including the coordination and dissemination of meeting details and documentation;
- Overall document management related to group activities; and,
- General oversight of the direction and delivery of the SubWG
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.
Past and upcoming sessions
| Date | Key Area of Discussion | Presentation |
|---|---|---|
| 2022-11-15 | Session 4
|
|
| 2022-09-20 | Session 3
|
File:GC MVBA WG 2022-09-20 RoD.docx
File:2022-09-20 Minimal Viable EBA GC BACoP.pptx |
| 2022-07-26 | Session 2
|
File:2022-07-27 Meeting Notes - GC Business Architecture Sub Working Group.pdf |
| 2022-05-25 | Session 1
|
File:GC MVBA WG 2022-05-25 RoD.docx |
| 2022-04-25 | Kick Off
(See "Discussion" tab for more information) |
File:2022-04-25 Minimal Viable EBA GC BACoP.pptx |
