When teams work together with a common goal and a passion for success, their projects succeed. When the opposite occurs, everyone loses, including the team, the employer and their customers.
In the course of my normal consulting assignments, I'm often told that there's something wrong with the data or with the process models being prepared by the team architects, but what I often find is that there is a significant disconnect between what the architects are doing and what the rest of the team expects them to do.
In this paper, I will look at some of the problems that project data and process architects face in working with other IT roles and seven easy and inexpensive steps they can take to ensure a collaborative team environment.
Information Security Research Library
