Monday, 14 March 2011

Cultural Resistance while Managing Projects

Culture is defined based on the context.  For example, culture of a nation. National culture is based on the beliefs and traditions followed in that nation. Think about culture in an organization, it is the way in which an organization performs a process. How about a work group culture? It is the behaviour of a small work group in an organization.

Based on the above classification of the culture, resistance raises while managing projects, which may lead to the failure of projects.
National Culture which can also be considered as demographic culture may create a sub group in a project team in turn creates the difficulty in managing the team. For example, consider a team consists of six people, three of them speak same language, the other two speak another language and all the remaining speaks their own different languages. What do you think about the communication and coordination in that project team?

Organization Cultural resistance come in to existence, when a company is took over by other company or an employee from one organization works as an employee in another organization as a contract employee. For example, consider the technical documentation scenario, a writer from company X works for company Y as a contract employee. In company X, the culture of documentation is the following. The writer sits next to developer or programmer and documents the product. But, in company Y, the developer sits in one location and programmer sits in other location. Based on this scenario, how is the performance of that employee? Is there any chance of cultural resistance in this situation?

Work group cultural resistance is the discomfort happening when a member of a team joins another team in the same organization as a part of resource allocation. For example, in a project team A, developer writes only programs and testing person writes the design document and does the testing of the product. This developer as part of another project requirement, moved to a project team B, where the developer writes both the programmes and design documents and the testing person tests the product.What do you think about this situation?

No comments:

Post a Comment