Software Project Management: Planning, Tracking, & Measurement, Slides of Software Engineering

An overview of software project management, focusing on planning, tracking, and measurement dimensions. It covers topics such as determining requirements, resources, and lifecycle models, tracking cost, effort, and schedule, and measuring product features, complexity, and productivity. The document also outlines a generic planning process, including identifying project scope and objectives, infrastructure, and products and activities, estimating effort, identifying risks, allocating resources, and executing the plan.

Typology: Slides

2011/2012

Uploaded on 07/17/2012

baisakhi
baisakhi 🇮🇳

4

(25)

94 documents

1 / 13

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Software Project
Management
Planning, Tracking, & Measurement
docsity.com
pf3
pf4
pf5
pf8
pf9
pfa
pfd

Partial preview of the text

Download Software Project Management: Planning, Tracking, & Measurement and more Slides Software Engineering in PDF only on Docsity!

Software Project

Management

Planning, Tracking, & Measurement

Project Management Dimensions

 Planning  Tracking  Measurements

Tracking

 Cost, effort, schedule  Planned vs. Actual  How to handle when things go off plan?

Measurements

 To date and projected  Cost  Schedule  Effort  Product features  Alternatives  Earned value analysis  Defect rates  Productivity ( LOC)  Complexity ( function points)

1. Identify project scope and

objectives

 Identify objectives & measures ofeffectiveness in meeting them  Establish a project authority  Identify stakeholders  Modify objectives in light of stakeholderanalysis  Establish methods of communications with allparties

2. Identify project infrastructure

 Establish relationship between project andstrategic planning  Identify installation standards and procedures  Identify project team organization

4. Identify project products and

activities

 Identify and describe project products(including quality criteria)  Document generic product flows  Recognize product instances  Produce ideal activity network  Modify ideal to take into account need forstages and checkpoints

5. Estimate effort for each activity

 Carry out bottom up estimates  Revise plan to create controllable activities

7. Allocate resources

 Identify and allocate resources  Revise plans and estimates to account forresource constraints

8. review/ publicize plan

 Review quality aspects of project plan 

Document plans and obtain agreement 9/10 execute plan/ lower levels of

planning