Interim Management Provider Types

This approach can be implemented in the closeout phase, with systematic reviews for each of the above factors. Doing so, project closure could receive the attention it

deserves and be a truly powerful method for continuous improvement within an organization. Finally, project closeout phase should be linked with PMI's Organizational

Project Management Maturity (OPM3) model Interim Management Provider where the lessons learned from one project are extremely valuable to other projects of the same program in order to achieve

the highest project management maturity height.

References

1. A Guide to Project Management Body of Knowledge, 2004, 3rd Edition, Project Management Institute, USA, p102

2. Arora M, 1995, Project management: One step beyond, Civil Engineering, 65, 10, [Electronic], pp 66-68

3. Barkley & Saylor, 2001, Customer-Driven Project Management, McGraw-Hill Professional, USA, p214

4. Bucero A, 2005, Project Know-How, PM Network, May 2005 issue, [Electronic], pp 20-22

5. Crawford K, 2002, The Strategic Project Office, Marcel Dekker, USA, p163

6. Department of Veteran Affairs, 2004, Project Management Guide, Office of Information and Technology - USA Government, p13

7. Dvir D, 2005, Transferring projects to their final users: The effect of planning and preparations for commissioning on project success, International Journal

of Project Management vol. 23, [Electronic], pp 257-265

8. Futrel R, Shafer D & Shafer L, 2002, Quality Software Project Management, Prentice Hall PTR, USA, p1078

9. Gannon, 1994, Project Management: an approach to accomplishing things, Records Management Quarterly, Vol. 28, Issue 3, [Electronic], pp 3-12

10. Heerkens G, 2002, Project Management, McGraw-Hill, USA, p229

11. Kempster S, 2005, The Need for Change, MSc in Project Management: Change Management module, Lancaster University, [Electronic], slide 16

12. Kerzner H, 2004, Advanced Project Management: Best Practices on Implementation, 2nd Edition, Wiley and Sons, p303

13. Kerzner H, 2001, Project Management - A Systems Approach to Planning, Scheduling and Controlling, 7th Edition, John Wiley & Sons, New York, p594

14. Kerzner H, 2001, Strategic Planning For Project Management Using A Project Management Maturity Model, Wiley and Sons, pp 110-111

15. Lecky-Thompson G, 2005, Corporate Software Project Management, Charles River Media, USA, p26

16. Loo R, 2002, Journaling: A learning tool for project management training and team-building, Project Management Journal; Dec 2002 issue, vol. 33, no. 4,

[Electronic], pp 61-66

17. Maylor H, 2005, Project Management, Third Edition with CD Microsoft Project, Prentice Hall, UK, p345

18. Mooz H, Forsberg K & Cotterman H, 2003, Communicating Project Management: The Integrated Vocabulary of Project Management and Systems Engineering, John Wiley

and Sons, USA, p160

19. Murray J, 2001, Recognizing the responsibility of a failed information technology project as a shared failure, Information Systems Management, Vol. 18, Issue

2, [Electronic], pp 25-29

20. Newell S, 2004, Enhancing Cross-Project Learning, Engineering Management Journal, Vol. 16, No.1, [Electronic], pp 12-20

21. Organizational Project Management Maturity (OPM3): Knowledge Foundation, 2003, 3rd Edition, Project Management Institute, USA

22. Pinkerton J, 2003, Project Management, McGraw-Hill, p329

23. Reed B, 2001, Making things happen (better) with project management, May/Jun 2001 issue, 21, 3, [Electronic], pp 42-46

24. Rosenau & Githens, 2005, Successful Project Management, 4th Edition, Wiley and Sons, USA, p300

25. Sowards D, 2005, The value of post project reviews, Contractor, 52, 8, [Electronic], p35

26. Thomset R, 2002, Radical Project Management, Prentice Hall PTR, USA, p260

27. Whitten N, 2003, From Good to Great, PM Network, October 2003 issue, [Electronic]