Most software projects fail completely or partial failures because a small number of projects meet all their needs. These requirements may be the cost, time, quality requirements or goals. According to many studies, the failure rate of software projects is between 50% - 80%. This essay is a collection of causes of failure of software development projects; this paper summarizes several areas that play a vital role in the failure of a software project.
So, what is really the reason for the failure of the project software? The sad fact is that software projects fail , because we do not recognize that good engineering principles should be applied to software projects as they are for the construction of office buildings. We try to defend ourselves by saying that software construction is "different".
One of the most serious complaints against software failure is the inability
with acceptable precision estimate the cost, resources, and the timetable necessary
for a software project. Conventional methods of assessment have always produced
positive results that contribute to the cost too well known infested and
schedule slippage.
Over the last 20 years a lot of cost and schedule estimation techniques were
used with mixed feeling because of restrictions of the assessment models. An important
estimates the failure may be due to a lack of the development process
software and understanding the effect of the method used in the project
Plan, planning and cost estimates.
carelessness Studies
The following are some of the considered case studies, which will be analyzed to fetch
the main reasons for failure of the software system.
Northumbria University developed the accounting software to manage its day-to-day
business. The project could not come up with the desired results and failed to
meet deadlines. Te investigations have shown that the project management based
procedures were not followed. This case study referenced in this essay
different points if necessary. [1]
Thai subsidiary (SMTL) of a multinational company in Hong Kong (SMHK)
engaged in the manufacturing of electronic equipment. They implemented
integrated software package; which it was a failure to the various factors. These
factors were mostly type management. Such as a lack of correspondence between the companies
hypothesis of process inscribed in the software and business processes SMTL,
poor leadership at different levels, cultural, organizational differences
environment, and mismanagement of resources human.
St John's Hospital is a District General Hospital provides medical and
care services, including both general surgery and medicine.All these
services are supported by diagnostic imaging, laboratory, ambulance, pharmacy
and therapy services, which are all on site. As the largest hospital in a tourist
area, it deals with many visitors over the holiday period, generating a large
amount of non-booked admissions work.
Software Management and Leadership
It 'been proven time and again, that effective leadership is essential for the successful implementation of IT (Klenke, 1994). A leader must also have cultural sensitivity, communication skills, creativity, ability to delegate, and the ability to develop and retain the human resources (Luthans, 1994). The (SMHK) manager software was a Western, where as the lower managers were East. So there was a culture clash going on forever. Jack (Manager) always tries to introduce creative thoughts. And most of the time the lower management could not do them. So there was a clash going on all the time.
The employees also felt that the management almost never "heard" their concerns
or attempted to address them. As a result, many employees were eager to leave
of society, and has done so, as soon as they found alternative opportunities in other companies
.
Planning & project planning
design means creating work breakdown, and then assign responsibility to the developers over time. The planning of the project consists of the construction of various tasks, deadlines and essential pathways including Gantt and PERT charts and other written plans for various situations.
And 'quite common in the process of software development to work backwards from the end date
project that results in complete failure of a software project. And '
impossible that a project can be completed efficiently from the design stage
for the implementation phase.
division of roles and responsibilities must be clearly defined, and is
becomes crucial, while hiring outside stall. upper
university management did not apply the basic rules of project management, which paid to
failure of the project.
proper planning is also required before the project. And '
includes time scheduling, the planning teams. Project managers do not know what
that need to plan and program. They just only tell the programmer what to do
and programmers can find an appropriate solution.
The development has been moved to a new office and the office was not completely
equipped with the proper infrastructure. With the passage of time is also an important factor in the success
or failure of a project. So it delayed the development process and helped
to the failure of the project. Infrastructure has not been fully programmed and
management team did not know where and how development of the project will be
started.
The top secret of a successful software development project is to control the
quality and reduce risk. emergency plan is also the part of planning. In
case things went wrong, then this plan can be followed to reduce the effect of
failure of the project. The same was the case with the university's accounting software. The
management team did not have such a contingency plan or assess the risk
involved in the development of the new system. So caused more problems, no
the backup system or the backup plan.
The management just try to follow the methodologies such as SDLC or RAD, but I do not know that the methodology to be used and in that time you should apply the right technique.
Estimated costs
Estimated costs is principally involved the cost of effort to produce the software project. But it is not limited to the effort. It also includes the cost of hardware and software, training of employees and customers, traveling to customer costs, networking and communication. Estimated costs should be done as a part of the software process model.
Estimated costs must be done well before the start of the project
development. The lack of a budget for the cost of the project results in
complete disaster. As previously mentioned the cost of infrastructure, development tools
cost and hardware cost also need to be estimated before.
same thing happened for the development of the university's accounting system. They
purchased the new system well with any serious estimate of the cost and
sources of income.
Below are the reasons why you made the wrong estimate of the costs.
estimation methodology moderator
Another reason could be the use of a methodology for estimating the costs inadequately. No single methodology is better than others. Each method has its strengths and weaknesses that must be considered. book by Dr. Barry Boehm Software Engineering Economics lists seven methods of estimation. One or more of these methods can be used to estimate the cost of a project
"Good suggestion is that more than a methodology of software cost estimate
should be used for the accurate estimation".
for cost estimating tools
There are many disadvantages in manual cost estimate. This technique is almost obsolete now. These days the estimated costs of success includes the use of a suitable business tool estimation of software costs.
good software estimation tools do not always guarantee reliable software
estimates. Wrong input size of the software will result in the wrong estimate.
estimation software also needs to be customized for the specific needs of
organization. These customizations require the data of past projects like [1945005Input] for the estimation tool.
There are various reasons why these tools can go the wrong estimate.
Choosing the right tool for estimating
Choosing a right estimation tool is required for the correct estimate. The tool is not able to handle input and then can come up with the wrong estimate and hence cause the secure software project.
Easy customization
As mentioned above the selected tool should be customizable according to the organization needs, so that the organization can customize to suit your needs and to design data of the past.
Easy to use and learn
The cost estimation tool should be easy to use and learn. It should include help and examples, and simple user interface straight forward. It should require less training to learn the system and inputs must be well defined.
accurate estimate
The estimation tool must have the ability to analyze all the parameters and come up with an accurate estimate for the cost.
Risk Management
The risk management is an important factor in the failure of software projects, if not managed promptly and effectively. As nothing can be predicted what will happen in the future, so we must take the necessary measures in the present to take any situation of uncertainty for the future. Risk management means dealing with a problem before it becomes a crisis.
Risk Identification
According to the Universal Risk Project there are two types of conditions that can be a symbol of how risk.
- IF-THEN statements
- "If the technology is not available, then we will not meet the requirement"
- "if we can not hire enough engineers qualified the software, then we can not meet the planned development program
- Statement accordingly provided
- Given the "condition", there is a probability that the "consequence" will occur
- "Because this particular test fails (the condition), the consequence is that the expected slip" program
may influence the development of the project. the risk may be technical or
nontechnical managers. project must be aware of both the risks. the majority of
managers projects are not good in one of the two sides. A good manager with
programming skills can be good to identify the technical risk, but not in the technical risk is not
.
Risk Analysis
Once the risk is identified there is a need to make the categories of this risk . Risk analysis is the process of evaluating the results of the project and the supplies after the risk analysis and applying the technique to reduce the risk. After the risk analysis was completed, the correct plan of risk analysis should be made to deal with any uncertain situation. First identified risks are divided into categories and make the hierarchy of these risks. At this point the risk is classified as positive or negative risks.
Risk Prioritization
After that risk is analyzed, the next step is to prioritize risk. At first focus on more risk sever before; and Les sever later. These risk factors can worked from time to time so that the final project come out is risk free. So most of the time of the project management team is unable to identify the risk and sever the work on the risk less severe. This often results in the form of a crisis.
Risk Prevention
Dealing with risk is an art. Sometimes the management takes the projects with out adequate risk identification involved in the project. So, an experienced manager will have the project after proper risk analysis and avoid any risk involved in the project.
The risk control
The risk management to achieve the desired results and the supply is through the control of risk at its best. This is a pure intuitive process and depends on the experience of the project management team, or the risk already successful in previous projects that were done by the same organization.
Conclusions
This paper has presented three basic factors that may cause the project to the secure software development. Planning & Scheduling, cost estimating and risk management. All these factors need to be considered at management level and then transferred to the lower management.
Planning & Scheduling is at first, good planning and programming makes the
solid basis for the software project. The planning of the project consists of
construction of various tasks, deadlines and essential pathways including Gantt
charts and PERT charts and other written plans for various situations. If
these factors are not taken in part, then the software can meet
problems during development and the final product will be a failure.
Estimated costs depends on the budget of the project, type of customer and
size and the effort to be put into the project. Cost estimates are made many times
during the life cycle of a project. Affects the project in many ways, wrong
Complete estimated failure, influence the willingness of the organization if the
costs are not covered, stakeholders are concerned and waste of resources.
The risk management is a practical approach to reduce ambiguity and
possible loss related to a software development project. Possible measures
may be considered (positive risk) opportunity focused if their
consequences are favorable, or as (negative risk) focused threat if their consequences are [1945005unfavorable].
0 Komentar