Conflict in Project based Environment
According to Ronald Reagan “Peace is not absence of conflict; it is the ability to handle conflict by peaceful means”. I have been working on various projects and developed an opinion that conflict is inevitable and in project based environment, it becomes even more visible. Projects being initiated today are complex, requiring collaboration from diverse stakeholders. A disciplined project team is not enough cultural, demographic, and power matrices impact on how every stakeholder behaves. Hence need for conflict management skills for project manager are indispensable.
Project Scenario and Conflict
The project I was working on was developing a cloud software for music management. The project was very dynamic we were really enjoying the concept as it was going to challenge the status quo. We never expected the project to go without hiccups so, place extensive risk management plan in place. However it was still a bumpy ride, the primary conflict area remained replicating customer requirements into product features. We were using Agile concept develop and project management technique with support from JIRA software.
The stakeholders wanted an algorithm that learns consumer takes and manages music for listener without even them knowing so that they are always delighted. The conflict arise on the presentation and prioritising features. Stakeholders had conflicting priorities however before I go in to conflict details I would like to categorise the conflict so that it is easier to follow and every reader can understand why this specific parameter was important. The conflict arise
- Due to Stakeholder’s Personality differentiation
- Due to Stakeholder’s differing opinions
- Due to presentation of some conflicting requirements
Detailing the Conflict
Targets were individual users but app was going to be offered to commercial and personalised space. To ensure commercial success project team and stakeholders had decided to primarily launch the services for restaurants where music gets customised according to the customers entering. The first phase was to gather requirement, which was most difficult part as it seemed impossible to make every one agree.
Firstly, conflict surfaced during initiation phase, there was a lot of differing opinions on the type of music that is going to be made available to individuals in the restaurants on a daily basis. Furthermore, the app design and algorithm preferences caused many issues. The philosophy behind was to engage stakeholder while channelizing their thoughts towards effectively defining the innovation that would truly satisfy them.
Secondly, conflict can occur between us, the project implementers and the management of some of the restaurants in which we intend to offer the updated music databases. Our investors wanted some thing totally autonomous that could learn the taste of the consumers and just blend in the environment to raise the taste. However, the restaurant owners wanted more control over what their visitors would hear during their dine in experience.
Lastly, the conflict occur on cultural grounds claiming that listeners’ culture must be adopted. In a diverse environment music would disengage rather than engaging consumers. Hence there was a need for extensive testing and planning to meet diverse requirements.
Conflict Resolution
The first approach towards resolving these issues will involve accepting that there is conflict and that there is need to have a common agreement. This has to be followed by identification of factors which might be leading to an escalationof the conflict. After creating a common ground, a way forward will have to be reached upon in which concepts from the two conflicting arguments will be merged in order to come up with a single common suggestion. In the case where the conflict will ensue between the implementing team and the restaurant management, the project manager can resolve it by agreeing to create the database as per the manager’s requirements. This will also be the same with customer playlists in which databases can be customized as per their specifications.
Quality Philosophy: Managing Conflict
Quality is not an act, it is a habit. Aristotle
I also believe that Quality is not an after thought rather a proactive attitude towards reducing waste in project environment.
Quality Issues
There is a need to make sure that the service delivered to both the customers in the restaurants as well as the managers is of top quality. To achieve this, the team will have to design a system that will be updated automatically. Thisis because, in the entertainment industry, trends play an important part as people always want to hear or listen to what is new on the market. Another issue that will have to be dealt with regarding quality is the ability of the restaurant managers and other employees to play or use the new database. This will be solved by integrating the database into the current system that is being used by the restaurant. This will mean that there will be no additional skills that will be needed.
Project Termination
Team Acknowledgement
First of all, while closing out the project, the project team would be acknowledged so that they could be encouraged for any future projects.
Client Acceptance
Project audit should be carried out to map project requirement with the project deliverables. Other than that, the deliverables would be handed over to client and would be cleared only after they are accepted by client. In case they are not accepted, close out of project could not be enabled. All cost accounts would be closed immediately and budget spent would be presented to management. Any contingency and management reserves left would be returned along with this. A party would be held out so as to acknowledge the end of project. Another important thing would be documentation of the project which would be placed in PMO for future referencing.
