Architectural Knowledge Sharing
(Rik Farenhorst, Patricia Lago and Hans van Vliet)
Architectural knowledge not shared eventually dissipates. Sharing:
- Prevents loss of crucial architectural knowledge.
- Enables exchange of experiences.
- Enables reuse of expertise.
- Assists to train juniors.
- Costs time and effort.
- Lack of perceived short-term benefits.
- Establishment of social ties - leading to increased transparency and trust.
- More efficient decision making.
- Knowledge internalisation - ownership of explicit knowledge; control, stored in own mind.
- Context and environment.
- Description.
- Decisiveness.
- Stakeholders roles and responsibilities.
- Lack of consistency between architecture and design documents.
- Communication overhead between stakeholders - not properly-documented decisions.
- No explicit collaboration with maintenance teams.
- No feedback from developers to architects - architects may lack up-to-date technology knowledge.
- No up-tp-date knowledge from development teams in repository.
- No up-to-date knowledge from main customer in repository - reference architecture used by organisation.
- Alignment between design artifacts -> [create] higher-quality knowledge -> [incentive] knowledge internalisation.
- Traceability between architectural decisions and descriptions -> [as above].
- Architect fulfil a central role -> minimise competition -> establishment of social ties.
- Central architectural knowledge repository -> creates feedback loop -> more efficient decision making.
0 Comments:
Post a Comment
<< Home