As with most reasonable sized organizations, the current organization has an operational team and a project team which drive varying degree of initiatives.
Unlike any other organization i have worked for, there is very little understanding of the deliverables each team is responsible for which has a bearing on the next initiative. For example there is a constant battle between the teams regarding ownership of documentation. When a project is initiated, there is very little by the way of understanding the current state. The project is told to bring all documentation concerning the said initiative up to scratch. This happens seldom since the project team does not see it as its responsibility to update operational documentation which should provide sufficient information about the current state.
I sit between these teams and am attempting to bridge the gap however am unsure how best to do so since there is much in the way of historical contention. Being the new kid on the block, i would like to bridge this gap. Attempting for the teams to share a common goal hasn't succeeded nor being open about specific issues and concerns. This often leads to finger pointing further deepening the already sour relationships.
Is there a specific methodology i can adopt and adapt as i imagine the situation being a common theme in a number of organizations around the globe?
To help answer the question raised by Tobias
Role: The role i play is that of an Enterprise Architect. The key challenge i have is that there is no consistency in standards, information and knowledge is tacit and people are unwilling to share information.
The teams include project managers, business analysts, server & administration, networks & help desk. All other roles are supported by vendors.