Software project planning

[Pages:43]Software project planning

The Plan, project estimation, decomposition, tools

(Pressman / Software Engineering / Chapter 5)

2012

P 1

Effective team meetings

? Use an AGENDA, distributed in advance

? People should know what is to be discussed

? Use team meeting for

? Analyzing, reporting what has been done ? Plan what should be done next ? Making decisions ? NOT FOR DOING THE WORK

? Exception: "brain-storming activities"

2012

P 2

Simple AGENDA

GROUP A MEETING, DC 3101 Nov 7. at 10.15 Present: NN, NN, NN, NN AGENDA:

* Code status (dev manager) * Decision on testing tools * The documentation templates (process manager) * Test plan (testing manager) * Next meeting

Agenda distributed 1-10 days before meeting

2012

P 3

The process

? Some process is normally ;) used for generating software

? linear ? prototyping ? RAD ? incremental ? spiral ? WINWIN ? component-based ? formal methods

2012

P 4

Process / product

? Example: Software process involving

? Customer communication ? Planning ? Risk analysis ? Engineering ? Construction and release ? Customer evaluation

? Map each of these activities to the product functions

2012

P 5

Project lifecycle relationships

Sales process

Software process

2012

P 6

Project planning

? Provides a framework for the project

? Software scope ? Resources ? Expectations

? Make it possible to make reasonable estimates for

? Resources ? Schedules ? Costs

2012

P 7

Why a project plan?

? Forces the making of necessary decisions

? Estimates, scheduling, budgeting

? Communicates decisions to other ? Checklist / action plan ? Who, what, when, why, where, how ? The "rules" of the project written in text, no

misinterpretation

2012

P 8

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download