Professional Documents
Culture Documents
CC5001 Week 12 Implementation 2012
CC5001 Week 12 Implementation 2012
Implementation stage
Inputs to implementation stage: Baseline plans Authorisation to proceed Details of next formal review point
Project completion
Project Life-Cycle:
Conceptualisation Planning Implementation Completion
Implementation stage
Level of effort
Con.
Plan
Impl.
Comp.
Implementation stage
Monitoring and controlling progress
Quality management Human resource management Scope management and change control Risk management
Cost
Quality
on progress to:
Report honestly Report everything
Dont be over-optimistic
0005
22/10/12
50
45
12
review Smith paper Interview subjects set q's for questionnaire issue questionnaire Analyse data from q'naire have report proof read Write report Submit report
14
review Smith paper Interview subjects set q's for questionnaire issue questionnaire Analyse data from q'naire have report proof read Write report Submit report
o
d a y
started on time finished on time
15
review Smith paper Interview subjects set q's for questionnaire issue questionnaire Analyse data from q'naire have report proof read Write report Submit report
o
d a y
16
review Smith paper Interview subjects set q's for questionnaire issue questionnaire Analyse data from q'naire have report proof read Write report Submit report
o
d a y
17
week 6
week 7
week 8
review Smith paper Interview subjects set q's for questionnaire issue questionnaire Analyse data from q'naire have report proof read Write report Submit report
o
d a y
started on time finished late delay to start of next activity
18
week 10
week 1
week 2
week 3
week 4
week 5
week 9
review Smith paper Interview subjects set q's for questionnaire issue questionnaire Analyse data from q'naire have report proof read Write report Submit report
o
d a y
started late delayed by previous activity finished late delay to start of next activity
19
review Smith paper Interview subjects set q's for questionnaire issue questionnaire Analyse data from q'naire have report proof read Write report Submit report
o
d a y
not yet started delayed by previous activity
20
Interview subjects
set q's for questionnaire
issue questionnaire
Analyse data from q'naire have report proof read
Write report
Submit report
21 back on schedule
Schedule variance: difference between BCWP & BCWS Cost variance: difference between BCWP & ACWP
For many projects it is enough to measure effort to date revised estimate to complete Update plan after each tracking cycle
Modify scope
Accept slippage
Quality management
The project manager must ensure that all products
Quality management
Quality plan forms part of baseline plan, and includes:
Standards to be used Processes and procedures to be used Who ensures procedures and standards are followed When checks are to be made
Quality management
Quality monitoring can take place at various stages
Each product can be checked once complete Products can be checked at different stages in
development
Random checking can take place e.g. sampling
Quality management
Monitoring can take the form of: Self-checking Reviews Walkthroughs (group review) Detailed inspection (formal walkthrough) Full audit (process and product)
Configuration management
BS8488 (1984) definition
the discipline of identifying the components of a continuously evolving system (taking into account relevant system interfaces) for the purposes of controlling changes to these components and maintaining integrity and traceability
from Cadle & Yeates (2001)
Change control: managing changes to an IS, including impact analysis, authorisation and documentation
understanding
dependencies between different components compatibility of different versions of components
of an Information System
Configuration management
Configuration management ensures that all elements needed to make up a system are recorded and controlled Configuration items subject to change, must be authorized and audited include specifications and documentation
Configuration management
Configuration management ensure configuration items needed to make up a system are complete and consistent must ensure that changes to configuration items are subject to appropriate change control mechanisms
Change control
Change control ensure changes only occur after
often confused
Risk management
Risk analysis / management cycle: Overall approach to risk management must be planned (in baseline plan) Risks need to be identified and analysed Risks need to be monitored and managed Repeat the steps, tuning the process to the changing project environment
Risk management
PRINCE (e.g. CCTA, 1997) separates risk analysis
Risk evaluation
Risk management
PRINCE (e.g. CCTA, 1997) lists 4 major activities
Monitoring
Controlling
Summary
Implementation carrying out the plan monitoring performance rescheduling if necessary managing change managing risk
Further reading
Burke, R (1999) Project Management: Planning and Control
Techniques, Chichester: Wiley (or more recent editions) Central Computer & Telecommunications Agency (1997) PRINCE 2: An Outline, London: The Stationery Office Maylor H (1999) Project Management (2nd Edition), London: Pitman Publishing Yeates D & Cadle J (1996) Project Management for Information Systems, London: Pitman Publishing Lockyer K & Gordon J (1996) Project Management and Project Network Techniques (6th Edition), Harlow: Prentice-Hall