 |
 |
Hi I am writting a paper for PHCSG for Cambridge in which I am discussing differing project methodologies for developing NHS clinical computing systems. I need some help. This can come in the form of private e-mail or e-mail to GP-UK. I would like to discuss PRINCE with those with experience as:- -Senior User (Project Board) -Senior Technical (Project Board) -Stage Manager -Technical Assurance Co-ordinator (Project Assurance Team) -User Assurance Co-ordinator (Project Assurance Team) The hypotheses that are generally thrown about are:- - projects are so focussed on their own products they do not notice other projects in the same domain - technically projects are pretty good but often fall down as there is not enough pragmatism inserted by the suppliers who have to deliver - technical products are usually paper specifications - there is scant user input into projects and although Senior User and UAC try their best they give up (or have limited effect) due to lack of energy when "fighting" the bureaucracy These comments are those that I hear regularly. Are they true ? Are there other comments ? If they are true do not feel limited in commenting as it would be hitting at PRINCE (sacred cow) as having read the manuals this weekend (sad person) it is clear this should not happen. I have some theories (no they will come out at Cambridge) but I would like not to come at it with the above biases if they are untrue or not always true. Thanks in anticipation Ian Press note: The above comments are unattributable hearsay they are not necessarily my own experiences. I am trying to explore the "truth" ..... please do not phone me. Dr Ian Purves (Director) Sowerby Unit for Primary Care Informatics University of Newcastle, UK Phone: +44 (0)191 222 7884 Fax: +44 (0)191 222 6043 http://www.ncl.ac.uk/~nphcare/Sowerby//ian.html PGP Key on Web or finger [log in to unmask] %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%