Saturday, 15 October 2011

Oct 16 - Literature Review (3)

********************************
Today: 3 hours
Literature review.

Deadline 5 months
Deadline march 30th 2012

********************************

Have to create structure/chapters of the final report.

Training Mon and Tue GG - Must monitor user feedback.

Perhaps we can tap into the answers initially there.

Plan was try to fix as much bugs as possible so when Actual users test Mon and Tue they will get the issues additional bugs.
 Maybe we can introduce support at this time to listen, set the expectations this is a testing session not a training session.

Initial reaction can cloud later and spread rumors.
Hence it is important to send the right message and get it right the first time. positive message so positive messages can be spread.

file:///C:/Users/owner/Desktop/user%20acceptance%20thur%2025th%202011/Failed%20IT%20Projects%20(The%20Human%20Factor)%20paper.htm


Most software development projects fail because of failures within the team running them. Before a team project can be labeled as failed, the term failed must be defined. For the purpose of this research, a failed software development project is defined as (1) being over-scheduled by more than 30% and/or, (2) being over-budget by more than 30% and/or, (3) the end product did not meet user requirements. These three criteria cover the schedule, budget, and requirement, all surrounded by quality that should comprise all projects. A failed project does not include canceled projects relating to changes in requirements that resulted from changes in business needs. The focus of this research is on the project team problems of these failed projects, thus resulting in team failure.

http://www.it-cortex.com/Stat_Failure_Cause.htm

The main reasons why systems fail to meet their objectives were identified as:
bulletLack of attention to the human and organizational aspects of IT.
bulletPoor project management.
bulletPoor articulation of user requirements.
bulletInadequate attention to business needs and goals.
bulletFailure to involve users appropriately.

I want to stress on last one to some extent not just user involvement but using it appropriately


http://goldpractice.thedacs.com/practices/mr/index.php






this is important.

how does the strategy support this?

No comments:

Post a Comment