1 of 30

Project Management

Dr. Sangeeta Arora � (HOD, P.G dept of computer science & IT)�

2 of 30

Key Definitions

  • Project management is the process of planning and controlling the development of a system within a specified timeframe at a minimum cost with the right functionality.
  • A project manager has the primary responsibility for managing the hundreds of tasks and roles that need to be carefully coordinated.

3 of 30

CREATING THE WORK PLAN

4 of 30

A Workplan Example

Work Plan Information Example

Name of task Perform economic feasibility

Start date ` Jan 05, 2001

Completion date Jan 19, 2001

Person assigned Mary Smith, sponsor

Deliverable(s) Cost-benefit analysis

Completion status Open

Priority High

Resources needed Spreadsheet

Estimated time 16 hours

Actual time 14.5 hours

5 of 30

Identifying Tasks

  • Top-down approach
    • Identify highest level tasks
    • Break them into increasingly smaller units
  • Methodology
    • Using standard list of tasks

6 of 30

Top Down Task �Identification

Phases

Phases with

high level steps

Work Plan Deliverables Estimated Actual Assigned

hours hours To

*

*

*

*

7 of 30

Estimating a Project Based on Industry Information

Planning Analysis Design Implementation

Industry

Standard

For Web 15% 20% 35% 30%

Applications

Time

Required 4 5.33 9.33 8

in Person

Months

8 of 30

Time Estimation Using a More Complex Approach

9 of 30

Estimation Trade-offs

  • Size
    • Function points
    • Lines of code
  • Effort
    • Person-months
  • Time
    • Months

10 of 30

Getting the Right Numbers for Estimation

  • Prior projects
    • Past experience
    • Industry standards
  • Detailed analysis

11 of 30

Estimating Effort

  • Function of size and production rate
  • COCOMO model

12 of 30

COCOMO Estimation Calculation

Effort = 1.4 * thousands-of-

(in Person- lines-of-code

Months)

Example:

If LOC = 2000 Then...

Effort = (1.4 * 2000) = 28 Person Months

13 of 30

Estimating Schedule Time

  • Rule of thumb for estimation

Schedule Time (months)

=

3.0 * person-months1/3

14 of 30

Staffing Attributes

  • Staffing levels will change over a project’s lifetime
  • Adding staff may add more overhead than additional labor
  • Using teams of 8-10 reporting in a hierarchical structure can reduce complexity

15 of 30

STAFFING THE PROJECT

16 of 30

Key Definitions

  • The staffing plan describes the kinds of people working on the project
  • The project charter describes the project’s objectives and rules
  • A functional lead manages a group of analysts
  • A technical lead oversees progress of programmers and technical staff members

17 of 30

Motivation

  • Use monetary rewards cautiously
  • Use intrinsic rewards
    • Recognition
    • Achievement
    • The work itself
    • Responsibility
    • Advancement
    • Chance to learn new skills

18 of 30

Conflict Avoidance Strategies

  • Clearly define roles and project plans
  • Hold individuals accountable
  • Project charter listing norms and groundrules
  • Develop schedule commitments ahead of time
  • Forecast other priorities and their possible impact on the project

19 of 30

CONTROLLING AND DIRECTING THE PROJECT�

20 of 30

Margins of Error in �Cost and Time Estimates

Typical margins of Error for

Well-done Estimates

Phase Deliverable Cost (%) time (%)

Planning System Request 400 60

Project Plan 100 25

Analysis System Proposal 50 15

Design System Specification 25 10

Source: Boehm et al. (1995)

21 of 30

Tracking Tasks Using Gantt Chart

Action Week

2 3 4 5 6 7 8 9 10 11 12 13

22 of 30

CASE Tools

Initiation Analysis Design Implementation

Upper CASE Lower CASE

Integrated CASE (I-CASE)

23 of 30

CASE Components

Procedural Metadata

Logic

Diagrams Screen

Designs

CASE Repository

24 of 30

Standards

  • Examples
    • Formal rules for naming files
    • Forms indicating goals reached
    • Programming guidelines

25 of 30

Documentation

  • Project binder
  • Table of contents
  • Continual updating

26 of 30

Managing Scope

  • Scope creep -- a major cause of development problems
    • JAD and prototyping
    • Formal change approval
    • Charging for changes

27 of 30

Managing Risk

  • Risk assessment
  • Actions to reduce risk
  • Revised assessment

28 of 30

Classic Mistakes

  • Overly optimistic schedule
  • Failing to monitor schedule
  • Failing to update schedule
  • Adding people to a late project

29 of 30

Summary

  • Project management is critical to successful development of new systems
  • Project management involves planning, controlling and reporting on time, labor, and costs.

30 of 30