3.4 Agile EAM and EAM Patterns Flashcards
How do you call a system of low dynamicity and low complexity?
predictable system
How do you call a system of medium dynamicity and medium complexity?
complex dynamic system
How do you call a system of high dynamicity and high complexity?
chaotic system
What is the system management approach for a predictable system?
Specialize & automate (taylorism)
What is the system management approach for a complex dynamic system?
agile, collaborative management (emergent structures)
What is the system management approach for a chaotic system?
Experiment & learn (MVP)
Are the agile EA management priciples rather connected to formal processes and tools or to individuals and interactions?
Rather to individuals and interactions.
Relationship-wise what do you strive for in EA management?
- ensure top management support
- maintain a good relationship to people from other management areas
How do you focus on demands of top stakeholders and speak their language?
- a single number of picture is more helpful than 1000 reports
- communication is key
- avoid waste (collect demand not information)
- benefit from existing model management processess
How do you reflect behavior and adapt to changes in the agile EA management principles?
- interative and incremental (one cycle around 12 months)
- use building blocks and patterns
- request 360° feedback
- adapt models and processes
- continuous collaboration
5 steps in lean management
- Specify value from the standpoint of the end customer by product family
- Identify all the steps in the value stream for each product family, eliminating whenever possible those steps that do not create value.
- Make the value-creating steps occur in tight sequence so that the product will flow smoothly toward the customer.
- As flow is introduced, let customers pull value from the next upstream activity.
- Begin the process again and continue it until a state of perfection is reached in which perfect value is created with no waste.
What is the risk of lean management?
Over-fitting of EA function to current demands
3 steps of collaborative EAM
Establish a lean set of processes and rules –> lean
Adopt evolutionary problem solving –> agile
Foster and moderate open participation –> enterprise 2.0
3 problems with EAM which are the motivation for the EAM initiative
Problems:
- lack of knowledge of EAM-fundamentals of EAM practitioners
- high entry barriers for beginners
- no common language and understanding
What is EAM initiative’s mission statement?
- accessible to broader community
- enhance it based on feedback and contributions of the community
- increase effectiveness
–> knowledge, transparency, community, foundations, best practices, themes
What is an enterprise architecture management pattern (EAM pattern)?
- general, reusable solution to a common problem
- in a given context (context dependent),
- identifies driving forces,
- known usages and
- consequences
Does an EAM pattern take an holistic perspecitve? And if yes how?
Yes
- it addresses problems at the enterprise level
- considers social, technical, and economic forces in a balanced manner
- discovers working solutions
- uses clear, accessible, and informal language
How much time does EA management spend on what?
75% on communicating etc
12.5% on model, collecting
12.5% on adaptating, reflecting
What are the core concepts of the EAM pattern catalog?
The EA team uses methods to address concerns of stakeholders by using specific visualization.
Draw structure of EAMPC (pattern catalog) VC
- Influence factors, Maturity levels
- Stakeholders
- Concerns
- Method patterns, Architecture principles
- Views: Viewpoint patterns, information model patterns
- Data collection patterns
Is an anti-pattern good?
No it is a bad pattern
What is the don’t boil the ocean anti-pattern about?
You should not create a meta-modle and then an create EA model by collection data
problem:
- data collection is expensive/ takes time
- neither in-depth nor broad will be sufficient
recommendation:
- start with a small model
- enlarge it when needed incrementally
What is the “Don’t build an ivory tower” anti-pattern about?
usual process:
- EA initiatives are set up as a project
- EA responsibilities and knowledge are centralized
observation:
- models are built without talking to other stakeholders
- terminology is unclear
- benefits not demonstrated
recommendation:
- establish a shared language
- connect demand and supply
- demonstrate quick wins
- establish EA processes
Steps in EAM being a sustainable management function
- Develop & describe
- Communicate & enact
- analyze & evaluate
- configure & adapt
What is develop & describe about?
- gather information and describe current state of EA
- develop long-term vision
- design medium-term
Communicate & Enact
- Communicate current state to the different stakeholders
- Enact planned states by influencing projects
Analyze & Evaluate
Assess current state of the EA and identify potentials for improvement
- Analyze the gaps between the current and target state & between planned and target state
Configure & Adapt
- measure performance of the EA management function
- adapt the EA management function by reassessing goals, environmental factors
