pm 3

IT Project Management Overview

The content covers the fundamentals of project management with an emphasis on project scope management. By the end of the lesson, students are expected to comprehend crucial aspects of project management necessary for successful project execution.

Learning Objectives

By the end of the lesson, students should be able to:

  1. Identify the four cornerstones of project management.

  2. Define project scope and explain its importance in project management.

  3. Understand the components of project scope management.

  4. Apply tools and techniques for managing scope effectively, including the Work Breakdown Structure (WBS).

  5. Identify challenges in scope management and strategies to overcome them.

Four Cornerstones of Project Management

The four cornerstones of project management are:

  1. Scope

  2. Schedule/Time

  3. Cost

  4. Quality
    These cornerstones represent the fundamental elements that must be balanced for project success.

Project Scope
Definition

Project scope refers to the part of project planning that involves the necessary work to deliver a project product, service, or result with defined features and functions. It incorporates:

  • Specific goals

  • Deliverables

  • Tasks

  • Costs

  • Deadlines
    This is crucial for setting clear expectations and objectives.

Importance

Defining the project scope is vital as it provides a framework that guides the project team in delivering the expected outcomes. It outlines what is included in the project as well as what is explicitly excluded, ensuring all stakeholders are aligned.

Project Scoping

Scoping involves distinguishing between what is included and excluded in terms of project work.

Scope Creep

Scope creep refers to uncontrolled changes or continuous growth in a project’s scope without appropriate documentation of the consequences on time, costs, and resources. It can manifest as:

  • Requirement creep

  • Function creep

  • Feature creep

Major Causes of Scope Creep

Common reasons for scope creep include:

  • Poorly detailed project scope statements within initial documents

  • Ineffective project management resulting in unmet requirements

  • Weak leadership from project managers

  • Indecision among stakeholders

  • A large number of stakeholders with conflicting priorities

Management Strategies for Scope Creep

Strategies to manage scope creep effectively include:

  • Strict adherence to project management processes

  • Building strong relationships with stakeholders

  • Proactive management of expectations

  • Accurate initial estimating and thorough planning

Project Scope Management Processes

The project scope management processes can be classified into two major categories: Planning and Monitoring & Controlling.

Planning Process

  1. Plan Scope Management

    • Outputs: A scope management plan and requirements management plan.

  2. Collect Requirements

    • Outputs: Requirements documentation and traceability matrix.

  3. Define Scope

    • Outputs: A project scope statement and updates to relevant project documents.

  4. Create Work Breakdown Structure (WBS)

    • Outputs: Scope baseline and updates to project documents.

Monitoring and Controlling Process

  1. Validate Scope

    • Outputs: Accepted deliverables, change requests, work performance information, and updates to project documents.

  2. Control Scope

    • Outputs: Work performance information, change requests, updates to the project management plan, and organizational process assets updates.

Plan Scope Management

The initial step involves developing a detailed Scope Management Plan that outlines:

  • How to prepare the project scope statement

  • Creation and maintenance of the WBS

  • Processes for obtaining acceptance of deliverables

  • Control measures for scope change requests

Collecting Requirements
Importance of Eliciting Requirements

Dividing requirement development into categories such as elicitation, analysis, specification, and validation facilitates clear communication and refined project outcomes.

Methods for Collecting Requirements

Common methods include:

  • Interviewing

  • Questionnaires and surveys

  • Observation

  • Prototyping

  • Focus groups and workshops

  • Group decision-making techniques

  • Benchmarking, which involves comparing practices across projects.

Requirements Traceability Matrix

A requirements traceability matrix is crucial for documenting:

  • Requirements

  • Attributes of each requirement

  • Current status of requirements
    This ensures all project requirements are acknowledged throughout the project lifecycle.

Defining Scope
Steps Involved

Defining scope entails managing project expectations by:

  1. Clearly stating the project scope's inclusions and exclusions.

  2. Outlining project deliverables beyond just a list; explanations should indicate the purpose of each deliverable.

  3. Establishing acceptance criteria for deliverables, which should delineate responsibilities, measuring techniques, and acceptance processes.

  4. Producing a comprehensive Scope Statement identifying objectives, requirements, boundaries, deliverables, acceptance criteria, and underlying assumptions/constraints.

Sample Project Scope Statement

This outlines a user-friendly web application for tracking employee time entries as part of the Timesheet Reporting Tool project:

Project Justification

The application automates daily time tracking for global IT employees, enhancing efficiency.

Project Objectives

  • To track timesheet entries for all IT employees effectively.

High-Level Requirements

  • User access for all employees and admin access to the support team.

  • Report-generation capability for project managers.

  • Remote user access.
    This project scope distinguishes in-scope functionalities such as multi-level approvals and timesheet management from exclusions.

Create Work Breakdown Structure (WBS)
Definition

The Work Breakdown Structure (WBS) is an essential method for dividing projects into manageable components. It offers a structural view that helps in defining the work required for project completion. It is crucial for planning project schedules, costs, and managing changes.

Benefits of WBS

The widely recognized advantages of using WBS include:

  • Enhancing project organization

  • Facilitating responsibility assignment

  • Demonstrating control points and milestones

  • Enabling accurate estimation of costs, risks, and timelines

Example Structures of WBS

Several examples illustrate WBS structures, including phase-based, deliverable-based, and tabular views that categorize project components across various levels of task breakdown, from initiation to project completion.

Validate Scope
Approach

Validation involves formalizing the acceptance of project deliverables and defining timelines and processes for review. Establishing a turnaround process for dealing with any issues encountered is also essential. This should include clear criteria for interim acceptance to facilitate prompt corrections.

Control Scope
Goals of Scope Control

Goals center around managing scope changes, influencing factors that lead to such changes, and ensuring any adjustments follow established integrated change control procedures.

Challenges and Resolution Strategies

Common challenges in scope management include:

  • Uncontrolled scope changes (scope creep)

  • Vague requirements

  • Miscommunication among project stakeholders

Best Practices

To mitigate these challenges, best practices include:

  • Precise documentation of project scope

  • Early involvement of stakeholders

  • Utilization of tools such as WBS and scope statements

  • Implementing stringent change control processes.

Conclusion

The foundational concepts of project scope and scope management are integral for ensuring the success of IT projects. A solid understanding of these principles, along with practical application of tools and techniques discussed, will lead to better project outcomes.