13.7 Why Do Technology Projects Fail?
A process-improvement approach IS useful for but not limited to WHAT
software engineering projects
How much did the NASA Mars Observer mistake by Lockheed Martin cost?
$125 million
in the United States alone.the yearly tab for failed and troubled software conservatively runs somewhere from WHERE
$60 to $70 billion
Sometimes technology itself is to blame, other times it's a failure to test systems adequately, and sometimes it's a breakdown of process and procedures used to DO WHAT 2 things
1. set specifications 2. manage projects.
The most common factors include the following: (PG, WL, LC, PR, PC<
1. Poor goal setting, including a lack of clarity or ability to achieve goals 2.Weak project leadership and project management 3.Non-existent or limited executive commitment 4..Poorly forecast resource needs and inadequate access to required resources 5.Project complexity 6."Scope Creep" or changing and increasing requirements during project development 7 Ineffective project reporting and poor communication across constituents that include the project customer, end users, developers, and others in firm and IS operations 8 Inappropriate technical choices, including immature technical offerings 9Inadequate testing and deployment procedures 10 Internal and external politics, squabbling, and misalignment of priorities among stakeholders 11 Time and delivery pressures
Time and delivery pressures that encourage three bad things
1. corner cutting 2. ethical lapses 3. design weaknesses
ineffective project reporting and poor communication across constituents that include five groups of people
1. project customer 2 end users 3 developers 4 in firm and 5 IS operations
what could 60 to 70 billion buy you (Yes, I think this is interesting)
For that money, you could launch the space shuttle one hundred times, build and deploy the entire twenty-four-satellite Global Positioning System, and develop the Boeing 777 from scratch—and still have a few billion left over.
Why do tech projects fail? sometimes technology itself is to blame, other times it's a failure to WHAT systems adequately,
TEST
When methodologies are applied to projects that are framed with clear business goals and business metrics, and that engage committed executive leadership, success rates can WHAT
can improve dramatically.
Mechanisms for quality improvement include WHAT
capability maturity model integration (CMMI)
Inadequate testing and deployment procedures that should do WHAT
catch flaws before major rollout
"Scope Creep" is Doing WHat 2 things during project development
changing and increasing requirements during project development
What mistake was made on NASA Mars Observer by Lockheed Martin
contractors using English measurements, while the folks at NASA used the metric system.
Firms are also well served to leverage established project planning (bp, s) and software development methodologies that outline what 2 things when executing large-scale software development projects.
critical business processes and stages
But there is hope. Information systems organizations can work to implement procedures to improve the overall quality of their WHAT
development practices.
information systems represent WHAT portion of capital spending at most firms
largest
How many technology development projects fails to be successfully deployed
one in three!!!!!!!
Managers need to understand the complexity involved in their technology investments, and that achieving success rarely lies with the strength of the WHAT alone.
technology
established project planning and software development methodologies that outline critical business processes and stages when executing large-scale software development projects are idea whose these methodologies is straightforward just like the saying...
why reinvent the wheel when there is an opportunity to learn from and follow blueprints used by those who have executed successful efforts.?
