When the business needs change and are not managed properly then the result is softwarefailure. Business Needs should also be defined clearly in Software Requirementsdocuments.
Deadlines are unrealistic.
This happens when the deadlines of software change unexpectedly. If not managedproperly, software fails.
The project team lacks people with appropriate skills.
As we know that software engineers work on projects that do not belong to their domain.So, when the software engineer could not understand the domain of the softwarecorrectly, then it results in project failures. Even if succeeded, software includes lot of bugs which are fixed time to time, and thus cost of software project increases.
Miscommunication among Project members
Miscommunication among Project Staff also leads to software failures. When softwaredevelopers do not interact with each other to solve problems that they face, then thesoftware development usually takes more time then it should.
Inadequate software Testing
In many cases software testing is left to users who are not able to fully exercise thesystem. Regression testing is not performed at each release and functionality formerlypresent in the software is not verified and can be lost.
Frequent or large changes to project scope
.Scope changes can significantly impact the cost, schedule, risks and quality of the entireeffort. Software Project managers should watch out for early and frequent changes to thesoftware project scope.
Risk management is an important factor towards software project failure if it's notmanaged timely and effectively. As nothing can be predicted that what will happen infuture so we have to take the necessary steps in the present to take any uncertain situationin the future. Risk management means dealing with a concern before it becomes a crisis.
Q No.2: Give the recommendation in order to avoid the failure.
Starting on the right Path: