IT Project Management (ITPM): Teaching & Practice Dr Colin Ash School of Computing, Information & Mathematica

1. IT Project Management (ITPM): Teaching & Practice Dr Colin AshSchool of Computing, Information & Mathematical Sciences, USPash_c@usp.ac.fj 31 May 2006, SPACS, @The University of South Pacific Colin Ash1

2. AGENDA Part A: Teaching about IT-PM includes • Project Management and IT • Strategic Planning & Project Selection • Management of Scope, Time & Cost • Quality, Human resources, Communications, & Risk Management • Project Procurement Management Part B: Industry Projects for developing CS/IS prototypes through partnerships with USP • CS492 Industry Projects, commences 2006/S2 31 May 2006, SPACS, @The University of South Pacific Colin Ash2

3. 1. Project Management and IT • Why projects need to be managed? • To improve the likelihood of success • Why Projects fail? • Controlling cost/time/resources • What IT is need to support projects? • Communication of activities • How do IT projects differ other kind of projects? see PMBoK • Project life cycle and IT development 31 May 2006, SPACS, @The University of South Pacific Colin Ash3

4. 2. Strategic Planning & Project Selection • Information Technology Project Methodology (ITPM) – “generic” Phase1: Conceptualise & Initialise Phase2: Develop charter & plan Phase3: Execute & Control Phase4: Project Closure Phase5: Evaluate project success • Business Case • Project Selection & Approval • PM Processes - 5 attributes above 31 May 2006, SPACS, @The University of South Pacific Colin Ash4

5. 3. Management of Scope, Time & Cost The PM balancing act Time Costs Resources (for Scope) 31 May 2006, SPACS, @The University of South Pacific Colin Ash5

6. 4. Quality, Human resources, Communications, & Risk Management • Managing Scope • Managing Risk • Project Schedule and Budget • Project Communication, Tracking and Reporting • Managing organisational change, resistance and conflict - the human side of PM 31 May 2006, SPACS, @The University of South Pacific Colin Ash6

7. 5. Procurement Management • Project procurement management • Outsourcing • Core business v’s non-core • Back office v’s front office 31 May 2006, SPACS, @The University of South Pacific Colin Ash7

8. Part B: Industry Projects Industry Projects for developing CS/IS prototypes through partnerships with USP CS492 Industry Projects in CS & IS (see handout) Course description: • The courses requires students to conduct an industry-based project in an area of interest and expertise within the stream of specialization. An informal design and development methodology will be used in the project. • This course combines the study of project management in the context of computer Science/information systems related areas with discovery of real-life ethical dilemmas through their project. Students are expected to examine incidents of professional practice in the project and to develop communication skills appropriate to the development and conduct of the project. 31 May 2006, SPACS, @The University of South Pacific Colin Ash8

9. Course Management • Always on the look out for project opportunities • Hold an information evening for invited business owners or senior managers, Don’t advertise! • Project selection/matching based on students interests and academic studies: • Software development • Database and data mining solutions • Web site and applications development. • Project teams 2(min) to 4 (max) students 31 May 2006, SPACS, @The University of South Pacific Colin Ash9

10. Limitations • Limited to on campus students within Suva district. • Projects are prototypes (10 weeks) usually without any implementation • Projects are limited by the risk of confidential • Project costings are too theoretical 31 May 2006, SPACS, @The University of South Pacific Colin Ash10

11. Benefits • Able to add value to CV for job hunting & interviews – personal confidence • Gaining PM skills and knowledge • Gaining PM insights into balancing Cost v’s Time v’s Human Resources • Greater awareness of ethical (trust) behaviour in business 31 May 2006, SPACS, @The University of South Pacific Colin Ash11

12. Common Barriers • Lack of awareness of core curriculum - CBoK. • Lack supporting technology and education. • High cost of training – born by the Lecturer. • Lack of 1st hand cases studies. • Lack of political will and rewards. • No immediate awareness in society for industry projects. 31 May 2006, SPACS, @The University of South Pacific Colin Ash12

13. Conclusions • IT PM teaching and Practice is mandatory • Industry needs government financial incentives for companies to become project clients • CIS needs a team of academic specialists in • Software development • Database and data mining solutions • Web site and applications development • Network Security 31 May 2006, SPACS, @The University of South Pacific Colin Ash13

14. Audience Recommendations? • Continue to develop PM teaching and training as a SPACS focus activity 31 May 2006, SPACS, @The University of South Pacific Colin Ash14