Project Planning and Monitoring

1
Project Planning and Monitoring

• Colin Potts
• CS3302

2
Agenda

• Planning Scheduling Tools
• Work Breakdown Structure effort profiles
• Dependency networks (PERT charts)
• Timelines (Gantt charts)
• Not effort estimation
• Responsibility Allocation
• Team structure
• Monitoring

3
Project Plan Instantiated Process Model
4
Work-Breakdown Structure (WBS)
5
Typical Lifecycle Effort Expenditures
Planning incl. reqts., design, project
planning, etc.
Planning
Planning
Testing
Coding
Coding
Other
Brooks
Yourdon
6
START
Request permits
Surveying
Activities on arcs
Excavation
Dependency Network
Buy materials
Lay foundation
Build outside wall
Install exterior plumbing
Install interior electrical
Install interior plumbing
Install exterior electrical
Install exterior siding
Install wallboard
Paint interior
Install flooring
Paint exterior
Install roofing
Install interior doors fixtures
Install exterior doors and fixtures
FINISH
7
START
15
3
Estimated durations (Zero-length dummy activities)
10
10
15
20
10
12
15
10
9
8
11
18
5
9
7
0
6
0
0
0
FINISH
8
What does a dependency network (PERT chart)
show/hide?
5
2
6
3
2
8
4
3
2
START
FINISH
A
2
3
5
3
4
3
1
9
Earliest start (ES max EF of precursors) Earlies
t finish (EF max(ESduration)) Latest
finish Latest start (LS LF-duration) Slack
LF-EF Critical path (Slack0)
5
2
3
3
3
1
2
4
FINISH
A
START
5
2
2
2
4
3
6
10
Dependencies

• In a software project, what do dependencies
  really mean?
• You cant start BC until youve finished AB?
• You really shouldnt?
• You are prohibited from doing so?
• When have you finished an activity?
• When you say so?
• When the calendar says you should have?
• When some independent criterion is met?

11
Gantt charts What do they show/hide?
Early Date
Late Date
Jan 1
Jan 8
Jan 15
Jan 22
Jan 29
Feb 5
Feb 12
Feb 17
Feb 24
Description
Test of phase 1 Define test cases Write test
plan Inspect test plan Integration
testing Interface testing Document
results System testing Performance
tests Configuration tests Document results
1 Jan 99 1 Jan 99 9 Jan 99 9 Jan 99 23 Jan
99 23 Jan 99 23 Jan 99 2 Feb 99 2 Feb 99 2
Feb 99 17 Feb 99
5 Feb 99 8 Jan 99 22 Jan 99 22 Jan 99 1 Feb
99 1 Feb 99 1 Feb 99 17 Feb 99 17 Feb 99 17
Feb 99 24 Feb 99

----FFFFFFFF
----FFFFFFFFF

12
TODAY
ACTIVITY NUMBER DESCRIPTION
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
DEC
WBS 1.0 SYSTEM PLANNING
Specification approved
1.1 Review specification
1.2 Review budget
Budget approved
Schedule approved
1.3 Review schedule
1.4 Develop plan
Plan approved
WBS 2.0 SYSTEM DESIGN
Design approved
2.1 Top-level design
2.2 Prototyping
2.3 User interface
Design approved
2.4 Detailed design
Completed
Duration
Float
Critical
Start task
Slippage
Finish task
13
Team Organization

• How should you organize your teams?

14
Chief Programmer Teams
15
1 line of communication
Two people
3 lines of communication
Three people
Team Communication
Four people
6 lines of communication
10 lines of communication
Five people
n(n-1)/2 lines of communication
n people
16
Monitoring

• When should you plan?
• How do you know youre meeting the plan?