ISP640 CHAPTER 1 THE NATURE OF IT PROJECTS 2

Page 1: Introduction to Computing Project Management

• Course Title: ISP 640 - Computing Project Management

• Instructor: Ts. Dr. Hasiah Mohamed @ Omar

• Contact Information:

  • Phone: (+609-6216849)

  • Email: hasiahm@uitm.edu.my

Page 2: Syllabus Content

• 1. Nature of Information Technology Projects

  • Introduction to Project Management

  • The State of IT Project Management

  • Problem Areas in IT Projects

• 2. Project Methodologies and Processes

  • The Project Life Cycle

  • The Project Management Body of Knowledge (PMBOK)

  • PRINCE2

  • The System Development Life Cycle

  • Learning Cycles and Lessons Learned

• 3. Measurable Organizational Value and the Business Case

  • Measurable Organizational Value

  • The Business Case

  • Project Selection and Approval

• 4. Project Planning: The Project Infrastructure

  • Project Governance

  • The Project Team

  • The Organization and Project Planning

  • Procuring External Project Resources

  • The Project Environment

  • The Project Charter

Page 3: Course Structure

• Learning Objectives: Key takeaways for students

  • Introduction to Project Management Overview

  • PMBOK Guides Definition

  • What is Project Management?

  • Project Management in Information Technology

  • The State of IT Project Management

  • Factors Contributing to Project Failure

  • Question & Answer session

Page 4: Learning Objectives

• Understand IT projects as organizational investments.

• Recognize the need for projects to align with business strategy.

• Define a project and its attributes.

• Define project management as a discipline.

• Understand the relationship among portfolios, programs, and projects.

• Comprehend the synergy between IT and project management evolution.

• Assess the current state of IT project management.

• Identify reasons for project failure and strategies for success.

Page 5: Overview of IT Projects

• IT projects are significant investments involving:

  • Time, Money, Resources (people, technology, facilities, etc.).

• Organizations anticipate a return on investment.

• IT projects facilitate technology integration in products, services, and processes, influencing relationships.

Page 6: PMBOK Definitions

• Project: A temporary endeavor to create a unique product, service, or result.

• Project Manager: Individual assigned to achieve project objectives by the performing organization.

Page 7: Attributes of Projects

• Attributes include:

  • Time Frame: Duration of the project.

  • Purpose: Projects should deliver value.

  • Ownership: Assigned roles.

  • Resources: Triple constraint (time, cost, scope).

  • Roles: Include Project Manager, Project Sponsor, Subject Matter Expert (SME), Technical Expert (TE).

  • Risk & Assumptions: Factors influencing project outcomes.

  • Interdependent Tasks: Progressive elaboration of tasks.

  • Planned Organizational Change: Alterations in the organization via project implementation.

  • Broader Environment: Projects operate within larger organizational contexts.

Page 8: Understanding Project Management

• Definition: Project management utilizes knowledge, skills, tools, and techniques to meet project requirements.

• Project Portfolio: Collection of projects aligned with organizational strategy for competitive advantage.

• Program: Group of interrelated projects managed collectively to enhance benefits.

Page 9: Evolution of IT Project Management

• Timeline of IT evolution influencing project management:

  • 1940s: First Electronic Computer

  • 1950s: EDP Era

  • 1960s: PC Era

  • 1970s: Network Era

  • 1980s-2010s: Globalization and beyond

Page 10: Current State of IT Project Management

• Studies: Conducted by the Standish Group and others.

• Successful Projects: Defined by completion on time, within budget, meeting all requirements.

• Challenges: The majority of projects are either failed or challenged compared to successful ones.

Page 11: Standish Group Report (1994)

• Findings:

  • 31% of IT projects were cancelled.

  • 53% exceeded budget by 200%.

Page 12: Standish Group Report (2004)

• Findings:

  • 30% total failure rate.

  • 50% of projects were over budget.

  • 90% were late in delivery.

Page 13: Standish Group Report (2014)

• Findings:

  • 31.1% total failure rate.

  • 52.7% over budget.

  • Average of 16.2% completed successfully.

  • 9% met the criteria of on-time and within budget.

Page 14: Reasons for Project Failure

• Categories of Project Failure:

  1. People: Stakeholders with various roles and interests leading to misalignment.

  2. Processes: Lack of structured project management practices.

  3. Technology: Failures attributable to non-compatible or outdated technologies.

  4. Organization: Absence of clear direction can impact project objectives.

Page 15: Examples of Project Failure

• Detailed examples illustrating failures within each of the four categories:

  • People, Processes, Technology, and Organization.

Page 16: Recap of Learning Objectives

• Review of significant points covered:

  • Understanding IT projects as investments.

  • Necessity of project alignment with organizational strategy.

  • Defining a project and key attributes.

  • Important project management definitions.

  • Interplay between project portfolios, programs, and projects.

  • Evolving practices in IT and project management.

  • Current challenges in IT project management and ways to enhance success rates.

Page 17: Conclusion

• Thanks and Engagement: Encouragement for active participation in discussions and applying lessons learned.