why_should_an_architect_collaborate_with_teams
Differences
This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
why_should_an_architect_collaborate_with_teams [2019/03/11 08:41] – created hpsamios | why_should_an_architect_collaborate_with_teams [2019/03/13 06:55] – [Collaboration] added gemba to collaboration hpsamios | ||
---|---|---|---|
Line 34: | Line 34: | ||
When Architects work directly with the Team on the Enterprise Asset it sets up a positive reinforcement loop. Architects working with Teams see their ideas implemented and increasing understand the Enterprise Asset. Teams working with Architects will be able to leverage the wider knowledge of the Architect and will see their impact on Architectural decisions. | When Architects work directly with the Team on the Enterprise Asset it sets up a positive reinforcement loop. Architects working with Teams see their ideas implemented and increasing understand the Enterprise Asset. Teams working with Architects will be able to leverage the wider knowledge of the Architect and will see their impact on Architectural decisions. | ||
+ | |||
+ | One note on the word “collaboration”. For many traditional organizations “collaboration” means “we have a meeting.” Meetings are certainly part of collaboration, | ||
+ | |||
+ | You might hear people refer to “going to the Gemba”. The Gemba is the place of work and this is the general notion that you can only have a real direct understanding of the work if you go to the place of work - sitting in your office doesn’t cut it. | ||
In reality, an Architect’s view of what should be standardized, | In reality, an Architect’s view of what should be standardized, |
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/why_should_an_architect_collaborate_with_teams.txt · Last modified: 2021/11/16 08:40 by hans