A practical use of key success factors to improve the effectiveness of project management

International Journal of Project Management

Volumn 17, Issue 3, 1999, Pages 139-145

  Clarke, Angela ^a  

^a UNIVERSITY OF WARWICK   (United Kingdom)

Author keywords

[No Author keywords available]

Indexed keywords

COST EFFECTIVENESS; PROBLEM SOLVING; QUALITY ASSURANCE;

KEY SUCCESS FACTORS;

PROJECT MANAGEMENT;

EID: 0033150104     PISSN: 02637863     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0263-7863(98)00031-3     Document Type: Article

References (57)

1. Caparelli D. Leading the company through the chokepoints of change. Information Strategy: the Executive's Journal, 12(3):1991;36-44.
2. Pinto J., Kharbanda D. P. How to fail in project management (without really trying). Business Horizons. 39(4):1996;45-53.
3. King, I., The road to continuous improvement: BPR and project management. IIE Solutions, Oct. 1996.
4. Lock, D., Project Management, 6th Edition. Gower, 1996.
5. Morris, C., Quantitative Approaches in Business Studies. Pitman Publishing, 4th Edition, 1996.
6. Peattie K. The teaching company scheme: effecting organizational change through academic/practitioner collaboration. Journal of Management Development. 12(4):1993;59-72.
7. Oakland, J., Total Quality Management. Butterworth Heinemann, 1989.
8. Newman M., Saberwal R. Determinants of commitment to information systems development: a longitudinal investigation. MIS Quarterly. 20(1):1996;23-24.
9. Clarke J. Corporate Change. Accountancy Ireland. 29(2):1997;10-14.
10. Kahn W. A. Facilitating and undermining organizational change: a case study. Journal of Applied Behavioural Science. 29(1):1993;32-55.
11. Burke, D., Project Management, Planning and Control, 2nd Edition, 1994.
12. Pinto J. K., Slevin D. P. Critical success factors in R&D projects. Research Technology Management. 32(1):1989;31-33.
13. Clarke, A., The key success factors in project management. Proceedings of a Teaching Company Seminar, London, December 1995.
14. Dieckmann M. Making new technology investments pay off. Managing Office Technology. 41(7):1996;11-14.
15. Toney, F. and Powers, R., Best practices of project management groups in large functional organizations. Project Management Journal, 1997, 33.
16. Pardu, W., Managing change in a project environment. CMA Magazine, May 1996, 6.
17. Orr, A. J. and McKenzie, P., Programme and project management in BT. British Telecommunications Engineering, Jan. 1992, 10.
18. Feiner, A. and Howard, K. A., An overview of quality and project management processes at AT&T. AT&T Technical Journal, May/Jun. 1992.
19. Meredith, J. and Mantel, S. J., Project Management: A Managerial Approach, Wiley and Sons, 1995.
20. Beavers D. Communication breakdown. Supply Management. 2(12):1997;34-35.
21. Lanfer A., Kusek J., Cohenca-Zall D. Taking the sting out of project surprises. Optimum. 27(3):1997;1-7.
22. Dahle S. Something to talk about. CIO. 10(18):1997;30-33.
23. Gannon, A., Project management: an approach to accomplishing things. Records Management Quarterly, July 1994, 28(3).
24. Neal R. A. The soft systems approach. International Journal of Project Management. 13(1):1995;5-9.
25. Reiss, G., Project Management Demystified: Today's Tools and Techniques, Chapman and Hall, 1994.
26. Schill R. L., Bertodo R. G., McArthur D. N. Achieving success in technology alliances: the Rover-Honda strategic collaboration. R&D Management. 24(3):1993;261-277.
27. Randolph, W. A. and Posner, B. Z., Effective Project Planning and Management, Prentice Hall International, 1994.
28. Ward J. A. Project pitfalls. Information Systems Management. 12(1):1995;74-76.
29. LaPlante A. Scope grope. Computerworld. 29(12):1995;81-84.
30. Bentley, D. and Rafferty, G., Project management: keys to success. Civil Engineering, April 1992.
31. Richardson T. Project management pitfalls. Business Communications Review. 25(8):1995;49.
32. Lexington: Hello world, Economist, Nov. 1996, 341(7992), 30.
33. Lewis R. Take the 'big' out of big projects: break them into manageable chunks. InfoWorld. 18(20):1996;24.
34. Bates, W. S., Strong leadership crucial. Computing Canada, Oct. 1994, 20(22).
35. Gilbreath, R. D., Winning at Project Management: What Works, What Fails and Why, John Wiley and Sons, 1986.
36. Keane, J.F., A holistic view of project management. Systems Management 3X/400, 1996, 24(6), 58-61.
37. Belassi W., Tukel O. I. A new framework for determining critical success/failure factors in projects. International Journal of Project Management. 14(3):1996;141-151.
38. The Roots of Bad Management, Civil Engineering, Jan. 1997, 67(1), 12-14.
39. Conroy G. Managing information and systems risks. Chartered Accounts Journal of New Zealand. 75(5):1996;6-9.
40. Phan D., Vogel D., Nunamaker J. The search for perfect project management. Computerworld. 22(39):1988;95-100.
41. Tangible Benefits Drive the Move to Standardization, PEM: Plant Engineering and Maintenance, April 1994, 17(2), 2.
42. Avery S. Standardizing on controls melts 'Iceberg' costs at Kodak. Purchasing. 120(3):1996;44-46.
43. Arora M. L. Project management: one step beyond. Civil Engineering. 65(10):1995;66-68.
44. Applegate D. B., Bergman L. G., Didis S. K. Measuring success. Internal Auditor. 54(2):1997;62-67.
45. Cox J. P. Waking a sleeping giant - the planning for success of a large project process at a large urban teaching hospital. IEEE Transactions on Professional Communication. 36(1):1993;20-23.
46. Aitkin A. Vision only works if communicated. People Management. 1(25):1995;28-29.
47. Ingoldsby, T., Time waits for no man(ufacturer). Systems, 1991, 4-20.
48. Dauphinais, W., When bad things happen to good projects. Across the Board, Nov/Dec. 1995, 46-50.
49. Jackson S. Re-engineering the Post Office. New Technology Work and Employment. 10(2):1995;142-146.
50. Rakos J. The multiproject problem. Computing Canada. 18(13):1992;22.
51. Society of British Aerospace (SBAC) Report entitled Best practice business process re-engineering. DTI Publication, Oct. 1995.
52. Powers, V. J., Benchmarking study illustrates how best in class achieve alignment, communicate change. Communication World, Dec. 1996/Jan. 1997, 14(1), 30-33.
53. Garner R. Captain of Crunch. Computerworld. 31(40):1997;81-82.
54. Baba M. L., Falkenburg D. R., Hill D. H. Technology management and American culture: implications for business process redesign. Research-Technology Management. 39(6):1996;44-54.
55. Pinto J. K. The power of project management. Industry Week. 246(15):1997;138-140.
56. Wojciak P. J. Don't force change - facilitate it! Materiel Management Quarterly. 19(1):1997;26-30.
57. Larkin, T. J. and Larkin, S., Reaching and changing frontline employees. Harvard Business Review, 1996, 74(3).