50 likes | 202 Views
WG3. (Software) Architecture Competency in relation to Practice. Grounded Theory. Individual Compentencies. Doing ”political” interactions Make technical decisions Making constraints clear Based on tradeoffs Listen to different types of stakeholders Educate himself/herself
E N D
WG3 (Software) Architecture Competency in relation to Practice
Individual Compentencies • Doing ”political” interactions • Make technical decisions • Making constraints clear • Based on tradeoffs • Listen to different types of stakeholders • Educate himself/herself • Communicate decisions and reasoning behind them • Enforce decisions • Come up with options • ”Sell” architecture • Mange personal relationship • Build up trust • Have a track record • Value-orientation • In contrast to product/manufacturing-orientation • Groom replacement • Grey-beard vs no-beard architects
Organizational Competencies • Who makes (architectural) decisions? Who has the authority? • Is the decision follows? Does it have an effect? • How do you ensure architectural conformance? • Towards development • Towards management • How does business and architect interact? • #Fights? • Are disagreements resolved • How does someone become an architect? • From the view of a person? • From the view of the organization? • Are there succeccesion plans for architects?