Daffodil International University

Faculty of Science and Information Technology => Software Engineering => Topic started by: farzanaSadia on April 20, 2017, 02:37:34 PM

Title: The Most Common Reasons Why Software Projects Fail
Post by: farzanaSadia on April 20, 2017, 02:37:34 PM
When launching a new software project, best practices suggest enlisting the help of a subject matter expert, who is knowledgeable about software development and can assist in the early stages of project planning. This strategy has proven to greatly improve the project outcome, yet at the end of the project you’re staring at a failure. How did this happen?

Project failure can be defined as one or a combination of cost overruns, late deliveries, poor quality, and/or developing a product that does not get used. Regardless of their involvement during the planning stages, more often than not, software developers bear the brunt of the responsibility for such situations; after all, they’re the ones who built the application. However, closer examinations of the projects do not always show evidence of incompetence.
When assessing these failed projects some of these perform “reasonably” when compared with industry trends, yet to the organization they are deemed failures. The reason is that overwhelming majority of the problems can be tied to flawed estimation or poor business decision making at the very outset of the project.

To avoid this, first organizations need to use a standardized set of estimation terms. We often find that individuals and organizations use a number of key terms interchangeably when they each have a unique meaning.

    Target – A goal, what we would like to do or achieve.
    Constraint – Some internal or external limitation on what we are able to do.
    Estimate – A technical calculation of what we might be able to do at a defined level of scope, cost, schedule, staff, and probability.
    Commitment – A business decision made by selecting one estimate scenario and assigning appropriate resources to meet a target within a set of constraints.
    Plan – A set of project tasks and activities that will give us some probability of meeting a commitment at a defined level of scope, budget, schedule, and staff.
Title: Re: The Most Common Reasons Why Software Projects Fail
Post by: afsana.swe on April 20, 2017, 02:45:17 PM
Madam,

Can we arrange a seminer on it ?