Lecture 4 Project Management Continuation Dr Taysir Hassan

Lecture 4: Project Management (Continuation) Dr. Taysir Hassan Abdel Hamid November 3, 2013

Four Key Steps in Managing Projects 1. 2. 3. 4. Identifying project size Creating and managing the workplan Staffing the project Coordinating project activities

1. IDENTIFYING PROJECT SIZE

Project Manager’s Balancing Act Project Management involves making trade-offs… Project Size e m Ti ec t Pr oj ost ect C Proj Modifying one element requires adjusting the others

Project Time Estimation Using the Function Point Approach

Function Point • Is a measure of program size that is based on the number and complexity of inputs, outputs, queries, files, and program interfaces. • In addition to measuring output, Function Point Analysis is extremely useful in: – – Estimating projects, Managing change of scope, Measuring productivity, and Communicating functional requirements.

Calculate Function Points Step 4 - Calculate Total Adjusted Function Points (TAFP): Total Adjusted Function Points (TAFP) = Adjusted Project Complexity * TUFP Processing Complexity (PC): __7______ (From Step 2) Adjusted Processing Complexity (PCA) = 0. 65 + (0. 01 * __7_ ) Total Adjusted Function Points: _0. 72 * _338_ = 243 (TUFP -- From Step 1)

Converting Function Points to Lines of Code Language C COBOL JAVA C++ Turbo Pascal Visual Basic Power. Builder HTML Packages (e. g. , Access, Excel) Lines of Codes per Function Point 130 110 55 50 50 30 15 15 10 -40 Source: Capers Jones, Software Productivity Research

Converting Function Points to Lines of Code Calculate the lines of codes: Total Lines of Codes = Function points * Lines of code per function point in the chosen language Example: If you chose C, then 243 function Points times 130 lines of code = 31, 590 total lines of code

Function Point Estimation Step Two – Estimate Effort Required Function of size and production rate: • Effort is a function of the system size combined with production rates (how much work someone can complete in a given time). (Effort in = 1. 4 * thousands-of-lines-of-code Person Months) Example: If LOC = 10000 Then. . . Effort = (1. 4 * 10) = 14 Person Months

Examples • For small to moderate-size business software projects (i. e. , 100, 000 lines of code and 10 or fewer programmers), the model is: • effort (in person-months) = 1. 4 * thousands of lines of code • For example, let’s suppose that we were going to develop a business software system requiring 10, 000 lines of code. This project would typically take 14 personmonths of effort.

• Examples of tools computing lines of code for different programming languages: 1. CCC – “free” for C++ and Java 2. CLOC – “free” for C++, COBOL, Fortran, Javascript, Lisp, Perl, PHP, Python, Ruby, SQL 3. NDepend – “free” for C++, Java

Function Point Estimation Step Three - Schedule Time Rule of thumb for estimation Schedule Time (months) = 3. 0 * person-months (1/3 is the exponent) Example: Effort = 14 person-month Schedule time =3. 0*14^1/3=7. 2 months

• This equation is widely used, although the specific numbers vary (e. g. , some estimators may use 3. 5 or 2. 5 instead of 3. 0).

Estimation tips • • • Allow time for the estimate Use data from previous projects Use developer-based estimates Estimate by walk-through Estimate by categories Estimate at a low-level of detail Don’t omit common tasks Use software estimation tools Use several different techniques, and compare the results • Change estimation practices as the project progresses

2. CREATING AND MANAGING THE WORK PLAN

A Workplan Example

To create a workplan • The project manager identifies the tasks that need to be accomplished and determines how long each one will take. • Then the tasks are organized within a work breakdown structure.

• Remember that the overall objectives for the system were recorded on the system request, and the project manager’s job is to identify all the tasks that will be needed to accomplish those objectives. • The methodology that seems most appropriate for the project provides a list of steps and deliverables.

Identifying Tasks • Methodology – Using standard list of tasks • Top-down approach – Identify highest level tasks – Break them into increasingly smaller units – Organize into work breakdown structure

Project Workplan • List of all tasks in the work breakdown structure, plus üDuration of task üCurrent task status üTask dependencies üMilestone (dates): Key milestones, or important dates, are also identified on the work plan

Open/Complete

Margins of Error in Cost and Time Estimates

Managing Scope • • Scope creep JAD and prototyping Formal change approval Defer additional requirements as future system enhancements

Timeboxing • Fixed deadline • Reduced functionality, if necessary • Fewer “finishing touches”

Timeboxing Steps 1. 2. 3. 4. 5. 6. Set delivery date – Deadline should not be impossible – Should be set by development group Prioritize features by importance Build the system core Postpone unfinished functionality Deliver the system with core functionality Repeat steps 3 -5 to add refinements and enhancements

Tracking Project Tasks • Gantt Chart – Bar chart format – Useful to monitor project status at any point in time • PERT Chart – Flowchart format – Illustrate task dependencies and critical path

Tracking Tasks Using Gantt Chart Task Week 2 3 4 5 6 7 8 9 10 11 12 13

PERT Example

3. STAFFING THE PROJECT

Staffing the project • Determining how many people should be assigned to the project, • Matching people’s skills with the needs of the project • Motivating them to meet the project’s objectives, • Minimizing project team conflict that will occur over time.

• The deliverable for this part of project management is a staffing plan, which describes: – the number and kinds of people who will work on the project, – the overall reporting structure, – the project charter, which describes the project’s objectives and rules.

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

Increasing Complexity with Larger Teams

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

Reporting Structure

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

Handling Conflict • • • Clearly define project plans Recognize project importance to organization Project charter listing norms and groundrules Develop schedule commitments ahead of time Forecast other priorities and their possible impact on the project

4. COORDINATING PROJECT ACTIVITIES

CASE Tools Planning Analysis Upper CASE Design Implementation Lower CASE Integrated CASE (I-CASE)

CASE Components Diagrams Screen Designs CASE Repository Procedural Logic Metadata

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

Types of Standards

Managing Risk • Risk assessment • Actions to reduce risk • Revised assessment

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

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

Copyright © 2012 John Wiley & Sons, Inc. • All rights reserved. Reproduction or translation of this work beyond that permitted in Section 117 of the 1976 United States Copyright Act without the express written permission of the copyright owner is unlawful. • Request for further information should be addressed to the Permissions Department, John Wiley & Sons, Inc. • The purchaser may make back-up copies for his/her own use only and not for redistribution or resale. • The Publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these programs or from the use of the information contained herein.