<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2d1 20170631//EN" "JATS-journalpublishing1.dtd">
      <JournalTitle>Allana Management Journal of Research, Pune</JournalTitle>
      <PISSN>? ?2581-3137 (</PISSN>
      <EISSN>) 2231 - 0290 (Print)</EISSN>
      <Volume-Issue>Volume 7, Issue 1</Volume-Issue>
      <Season>January 2017 - June 2017</Season>
      <ArticleType>Information Technology Management</ArticleType>
          <FirstName>Mr. Mir Mehdi Ali</FirstName>
          <FirstName>Dr. Manik</FirstName>
      <Abstract>Software projects get delayed or in extreme cases even gets aborted for various reasons which is major cause of losses. Software Project Managers need to monitor the progress of projects continuously and take precautions to see that these eventualities do not happen.&#13;
Apart from technical reasons like defects, failures of modules at software testing stage, there are several factors which can be tackled using the regular Software Engineering Principles, there are a few non tangible causes like conflicts which need to be properly handled by stakeholders to ensure the success of a project. Conflicts can arise between individuals, departments or organizations involved in the project. Stack holders should be proactive in the sense that they need to predict and resolve these to avoid financial risk, risk of inordinate delay or risk of abortion of projects.&#13;
The purpose of this article is to critically examine the Constraints and Causes of conflicts, delay, Types and dynamics of conflicts, Ways to resolving conflicts, Ways to predict and avoid conflicts in software development project scenarios using possibility indicator matrix.&#13;
Constraint, barrier, confliction, scope, time, quality, requirement, meeting, report, developer, programmer, TL, PM, designer, sponsor, client, funds, security, information.</Abstract>
        <Abstract>https://aimsjournal.org/ubijournal-v1copy/journals/abstract.php?article_id=13203&amp;title=CONSTRAINT ELIMINATION THROUGH CONFLICT POSSIBILITY INDICATOR MATRIX (CAM) IN SOFTWARE PROJECT MANAGEMENT</Abstract>