Learning software process with UPEDU Slide 9-1 2000 École Polytechnique de Montréal & Rational Software Project Management - Outline Defining the Project.

Learning software process with UPEDU Slide 9-1 2000 École Polytechnique de Montréal & Rational Software

Project Management - OutlineProject Management - OutlineProject Management - OutlineProject Management - Outline

Defining the Project Manager RoleDefining the Project Manager Role The Project Manager The Project Artifacts and Milestones

Planning ProjectsPlanning Projects

Managing IterationsManaging Iterations

Managing RisksManaging Risks


Plans and ControlsPlans and ControlsPlans and ControlsPlans and Controls

Start1/97

LCO3/97

Build

#1

Build

#2

5/97

LCS5/97

IOC12/97

2/984/97

Planning

Completed(% of total)

100

75

50

25

InceptionElaboration

Construction Transition

Controlling


Managing ExpectationsManaging Expectations

Why manage expectations?Why manage expectations?1. People are not perfect.

2. People are not logical.

3. People perceive things differently.

4. Software engineers are people too.

5. Things happen.

Gause & Weinberg, 1989

A new car!

A new car!


Project Management DisciplineProject Management DisciplineProject Management DisciplineProject Management Discipline

SoftwareDevelopment

Plan

MeasurementPlan

Project PlanningReviewReviewer

WorkOrder

Project Manager

DevelopMeasurement

Plan

Plan Phasesand Iterations

Risk List


Software Development PlanSoftware Development PlanSoftware Development PlanSoftware Development Plan

Project Manager Software

Development Plan

Measurement Measurement PlanPlan

ProjectProjectPlanPlanRisk ListRisk List

UPEDU GUIDELINE: Project PlanUPEDU GUIDELINE: Risk list


Major MilestonesMajor MilestonesMajor MilestonesMajor Milestones

Inception Elaboration Construction Transition

Commit resources for the elaboration phase

Lifecycle Objective Milestone

Commit resources for construction

Lifecycle Architecture

Milestone

Product sufficiently mature for customers

Initial Operational Capability Milestone

Customer acceptanceor end of life

Product Release

time



Defining the Project Manager RoleDefining the Project Manager Role


Project Organization The Planning strategies The Project Plan Artifact




Influenced by Many FactorsInfluenced by Many FactorsInfluenced by Many FactorsInfluenced by Many Factors

The Size of the Software Development EffortThe Size of the Software Development Effort Formality, Standards, Process Rigidity.

The Degree of NoveltyThe Degree of Novelty First of its Kind, Evolution Cycle, Maintenance

Type of ApplicationType of Application Mission-critical, Performance,Memory constraints,

The Current Development ProcessThe Current Development Process Process Maturity, Experience of the Developers and Managers

Organizational FactorsOrganizational Factors Team attitudes toward changes, Team enthusiasm toward the project

Technical and Managerial ComplexityTechnical and Managerial Complexity Size of the team vs size of the project


Top-down and Bottom-up Planning Top-down and Bottom-up Planning

Current

Iteration Plan

Phases and major milestones What and when

Project Plan

Iterations for each phase Number of iterations Objectives DurationStaffing profile

Fine-Grained PlansIntra iteration

Coarse-Grained PlanInter iteration

Next

TasksAllocation to individuals/teamsMajor builds


Project PlanProject PlanProject PlanProject Plan

Project Plan

Iteration Plan

4/02

Start1/02

LCO3/02

5/02

LCA7/02

IOC12/02

2/034/02

IT1 IT2

ArchitectureReview

ProjectPlanning

ß1 ß2ProductRelease

IT3 IT4 IT5

DesignReview

Build#1

Build#2


Work Structure, Schedule, & BudgetWork Structure, Schedule, & BudgetWork Structure, Schedule, & BudgetWork Structure, Schedule, & Budget

Resource

Paul

Mary

Joe

Sylvia

Stefan

Role

Designer

Use-Case Specifier

System Analyst

Implementer

Architect

Activities

Define Operations

Detail a Use Case

Find Actors and Use Cases

Perform Unit Tests

Identify Design Mechanisms

$$$



Defining the Project Manager RoleDefining the Project Manager RolePlanning ProjectsPlanning Projects


The Definition of an Iteration Scope on an Iteration Iteration assessment



Project ManagementProject Management

Engineering Workflow

Implementation

Test

Analysis & Design

Process Disciplines

Supporting Workflows

Config. & Change Mgmt

Requirements

Elaboration TransitionInception Construction

Iterations

An iterationAn iterationAn iterationAn iteration


Scope of an Iteration depends on FactorsScope of an Iteration depends on FactorsScope of an Iteration depends on FactorsScope of an Iteration depends on Factors

How many iterations should be included in the project plan?How many iterations should be included in the project plan?

How long should each iteration take?How long should each iteration take? Depends on a number of factors:

• Size of the system being built: The larger the system, the longer the duration.

• Number of people: The larger the number of people, the longer the duration.

Low 3 0 1 1 1

Typical 6 1 2 2 1

High 9 1 3 3 2

Total I E C T

UPEDU Concept: ITERATION


Progress

Stability

Modularity

Quality

Maturity

Expenditures

Based on MetricsBased on Metrics

Size and complexity

Rate of change in the project’s complexity or size

Scope of change

Number of errors

Frequency of errors

Project expenditures against plan

Metric Meaning



Defining the Project Manager RoleDefining the Project Manager Role




Risk Definition Risk Strategies Risk Assessments


Concepts Associated with Defining RiskConcepts Associated with Defining RiskConcepts Associated with Defining RiskConcepts Associated with Defining Risk

Risk: Risk: Information missing on a given subjectInformation missing on a given subject

Indirect risk:Indirect risk: Project has little or no controlProject has little or no control

Direct riskDirect risk Project has a large degree of controlProject has a large degree of control

Risk attributes:Risk attributes: Probability of occurrenceProbability of occurrence

Risk magnitude indicator:Risk magnitude indicator: High, Significant, Moderate, Minor, LowHigh, Significant, Moderate, Minor, Low

UPEDU Concept: RISK


Risk StrategiesRisk Strategies Risk StrategiesRisk Strategies Risk acceptanceRisk acceptance

live with itlive with it

Risk avoidanceRisk avoidancereorganize to eliminate the riskreorganize to eliminate the risk

Risk mitigationRisk mitigation reduce the probability or impactreduce the probability or impact

Risk contingencyRisk contingency plan “Plan B”plan “Plan B”

Risk transferRisk transfer sub-contract the risksub-contract the risk


Measurements and MetricsMeasurements and Metrics

5% 20% 65% 10%

ResourceEffort

Time

Inception Elaboration Construction Transition

0

20

40

60

80

1 2 3 4Iteration

# s

cen

ario

s

A B C D E FR é a lisé

E stimé

0

5

10

15

20

25

30

Estimated vs real time

Learning software process with UPEDU Slide 9-1 2000 École Polytechnique de Montréal & Rational Software Project Management - Outline Defining the Project.

Documents

project slide

learning software process

upedu slide

software engineers

project plan iterations

project plan upedu guideline

project plan artifact

cole polytechnique