Difference between revisions of "Talk:Business Architecture/Past Sessions"
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
* Should a Minimum Viable BA be defined outside the scope of EA? Within EA? Or both? | * Should a Minimum Viable BA be defined outside the scope of EA? Within EA? Or both? | ||
<br> | <br> | ||
− | + | ====Author and Contact Information==== | |
<br> | <br> | ||
− | Steven Bednikoff<br> | + | ''Steven Bednikoff<br> |
<br> | <br> | ||
Conseiller principal en architecture d’entreprise, Direction générale de la transformation numérique <br> | Conseiller principal en architecture d’entreprise, Direction générale de la transformation numérique <br> |
Revision as of 10:48, 3 May 2022
2022-04-25: Exploration - Minimal Viable Enterprise and Business Architecture Practice
Quick notes from the discussions
1- Clarifying the purpose and scoping the work:
- Is it worthy to pursue this effort of defining a MVEBA?
- What form should it take? What deliverable(s) / work package(s) should it include?
- How much effort can be put into it? Who’s willing to contribute?
2- Key questions raised during the 2022-04-25 session that should be further discussed:
- How should the EA/EBA practice support Product Management and agile transformation? What does that mean for a MVEBA?
- What is the right balance between EA “development” and EA as an internal consultancy service? In a general sense and specifically to each of the EA OM patterns
- Should a Minimum Viable BA be defined outside the scope of EA? Within EA? Or both?
Author and Contact Information
Steven Bednikoff
Conseiller principal en architecture d’entreprise, Direction générale de la transformation numérique
Santé Canada et Agence de la santé publique du Canada / Gouvernement du Canada
steven.bednikoff@hc-sc.gc.ca / Tél.: 438-355-8387
Senior advisor, enterprise architecture, Digital Transformation Branch
Health Canada and Public Health Agency of Canada / Government of Canada
steven.bednikoff@hc-sc.gc.ca / Tel.: 438-355-8387