OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
Software Project Management:
MONITORING AND CONTROL
SPIN - Agilent 5 April 2001
© OSEL
Slide 2001
1.1
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
Contents
1. Monitoring and control model
2. Activity data (monitoring)
3. Instructions (control)
4. Activity
5. Control
© OSEL
Slide 2001
1.2
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
ACTIVITY
requirements
&
resources
product
© OSEL
Slide 2001
1.3
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
ACTIVITY
requirements
&
resources
product
© OSEL
Slide 2001
1.4
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
activity data
(monitoring)
ACTIVITY
requirements
&
resources
product
© OSEL
Slide 2001
1.5
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
instructions
(control)
activity data
(monitoring)
ACTIVITY
requirements
&
resources
product
© OSEL
Slide 2001
1.6
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
a feedback loop
CONTROL
instructions
(control)
activity data
(monitoring)
ACTIVITY
requirements
&
resources
product
© OSEL
Slide 2001
1.7
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
• Monitoring and control is a feedback loop
– it is not planning, estimating, progress reporting or the CMM L2
– most like (change control)2
• Examples of feedback loops / control mechanisms:
– cistern and ball cock
– governor on a steam engine
• Project feedback loop is not mechanical
• Many dimensions to control
• Heuristic not algorithmic
– project - not production (but would like to be)
© OSEL
Slide 2001
1.8
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
• There are defective feedback mechanisms
(identify your favourite pathological projects)
© OSEL
Slide 2001
1.9
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
instructions
(control)
ACTIVITY
requirements
&
resources
product
© Slide
OSEL1.10
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
activity data
(monitoring)
ACTIVITY
requirements
&
resources
product
© OSEL
Slide 1.11
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
ACTIVITY
requirements
&
resources
product
© Slide
OSEL1.12
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
activity data
(monitoring)
ACTIVITY
requirements
&
resources
product
© Slide
OSEL1.13
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
CONTROL
instructions
(control)
activity data
(monitoring)
ACTIVITY
requirements
&
resources
product
© Slide
OSEL1.14
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
CONTROL
ACTIVITY
requirements
&
resources
product
© Slide
OSEL1.15
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
instructions
(control)
activity data
(monitoring)
ACTIVITY
requirements
&
resources
CONTROL
product
© Slide
OSEL1.16
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
• It can be adapted to operate hierarchically (programme management)
• It can be adapted to operate with supply chains
– but the nature of activity data and instructions information does change
© Slide
OSEL1.17
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
instructions
(control)
modified
activity data
(monitoring)
© Slide
OSEL1.18
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
instructions
(control)
What is this?
ACTIVITY
© Slide
OSEL1.19
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
• Communication of activity data should be:
–
–
–
–
–
–
–
in place (available - now)
timely (real time)
simple
structured
complete
conventional (a standard to make life simple)
consistent
• because...
© Slide
OSEL1.20
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
• Communication of activity data should typically describe :
– work completed (and not completed)
• w.r.t. schedule
– quality (usually unreported)
– changes
– risks
– defects
– actions and issues (what is an issue?)
– others - e.g. resources, requirements in/satisfied, customer satisfaction….
• individually and collectively
– signal stress points and potential problems
© Slide
OSEL1.21
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
• Example…..
© Slide
OSEL1.22
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
activity data
(monitoring)
What is this?
ACTIVITY
© Slide
OSEL1.23
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
• Control instructions should be
– accountable
– informed by detailed activity data
• individual and collective
• for all indicators
– justifiable - w.r.t. activity data
– re-align control parameters
• Shown as decisions and change in emphasis in decisions in activity
data
– communicated (available now)
– be well judged !
• (heuristic not algorithmic)
© Slide
OSEL1.24
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
• Example…..
© Slide
OSEL1.25
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
CONTROL
instructions
(control)
activity data
(monitoring)
What is this ?
requirements
&
resources
product
© Slide
OSEL1.26
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
Plans
Copyright OSEL 1998
WBS
PBS
schedule
to Track and Report Work
reviewed work product
status reports
and issues
corrective action requests
Do Work
Formal Technical
Review (or test)
status reports
Store Work
Products (library)
review records
1
completed work product
2
released product
3
change control
rejected work product
(revise and re-eview))
CIs booked out for reference
© Slide
OSEL1.27
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
What
is this?
instructions
(control)
activity data
(monitoring)
ACTIVITY
requirements
&
resources
product
© Slide
OSEL1.28
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
allocated requirements
Manage
Requirements
1
FTR &
library
Plan Work
approval to
change requirements
requirements to be refined
requirements for planning
change authorities
change requests
Change Control
4
Plan Work
approval to change
plans
(replan)
Copyright OSEL 1998
draft plans to SQA for
approval
SQA approval of
plans
plans
Track and Report
Work
2
3
FTR &
library
progress reports
to senior management
change request (replan)
corrective action
requests
to Produce
Software
decision
to
proceed
to Do Work
from Do Work and Store Work Products
status reports
and issues
SQA project reports
Milestone
Review
5
© Slide
OSEL1.29
2001
OXFORD SOFTWARE ENGINEERING
Software Engineering Services & Consultancy
OXFORD
S O FTWAR E E N G I N E E R I N G
LIMITED
9 Spinners Court, 53 West End,
Witney,
Oxfordshire
OX28 1NH
www.osel.co.uk
shelley@osel.netkonect.co.uk
Tel. +44 (0) 1993 700878
© Slide
OSEL1.30
2001