Line 35: |
Line 35: |
| à venir | | à venir |
| | | |
− | </multilang> | + | </multilang>'''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? |
| + | |
| + | |
| + | <Deck> |