Book title: Book title:

Demystifying Project Control Demystifying Project Control

Author: Dr. D. Antoniadis Author: Dr. D. Antoniadis
ISBN: 978-1-718063099 ISBN: 978-1-718063099
It is available for readers to purchase here or through my website: www.danton-progm.co.uk It is available for readers to purchase here or through my website: www.danton-progm.co.uk

Page
CONTENTS PAGE 8. Project Control Outputs 85
Page 1. The end user ………………………………………………………...…………………………………... 86
Acknowledgements 2. Rationale – The ‘Why’ ………………………………………………………………………………….. 87
List of Tables iv 3. How to bring information together ……………………………………………………………………... 88
List of Figures iv 4. Layering of the output levels ……………………………………….…………………………………... 89
List of Abbreviations vi 5. Identifying the required outputs ………………………………………………………………………... 90
About the Author vii 6. Setting the Reporting cycle ………………………………………...…………………………………... 92
1. Preface 1 7. The issue of ‘noise’/’filters’ in reporting / outputs ………………..…………………………………… 93
2. The basics from theory 5 9. Project Control and Issues to be considered 102
1. The Objectives and Defining Project Control ………………………………………………………… 5 1. Project control and the interfaces with ‘others’ ………………….…………………………………… 102
2. The reality and some basics ……………………………………….…………………………………... 8 2. The cultural issues ………………………………………………….…………………………………… 103
3. The Project Control functions ………………………………………………………………………….. 9 3. Is there a best practice project control? ………………………….…………………………………… 106
3. The Project Structures 15 4. The Issues with reporting and Complexity ……………………….…………………………………… 107
1. ‘WHY’ we need to use structures ………………………………….…………………………………... 16 10. Project Control and the Support it provides 119
2. Flexibility and adaptability of the structures ………………………………………………………….. 18 1. Project / Project Manager ………………………………………….…………………………………… 119
3. Structures and managing the effects of complexity …………………………………………………. 20 2. Programme Management Office (PMO) ……………………………………………………………… 119
4. The project management structures ………………………………………………………………….. 21 3. Other disciplines – Design, etc. …………………………………...…………………………………… 120
1. Work Breakdown Structure (WBS) ………………………………………………………………… 21 4. Directorate / Senior Management / Project Director …………….………………………………… 121
2. Cost Breakdown Structure (CBS) ………………………………………………………………….. 25 5. The Company ………………………………………………………..………………………………… 122
3. Organisational Breakdown Structure (OBS) ……………………………………………………… 29 11. Closing points 123
4. Programme Breakdown Structure (PgBS) ………………………………………………………... 33 12. Exercises 126
5. Project / Product Breakdown Structure (PBS) ……………………………………………………. 33 References 128
6. Risk Breakdown Structure (RBS) ………………………………………………………………….. 34 Bibliography 131
7. Document Breakdown Structure (DBS) …………………………………………………………… 37 Index 134
5. Combining project management structures …………………………………………………………... 39
1. Results from combining the structures ……………………………………………………………. 39
2. What do you get from WBS + OBS = RAM ……………………………………………………….. 39
3. Combining other structures …………………………………………………………………………. 40
6. Dealing with other project management processes …………………………………………………. 44
4. Is Project Control a department or something else? 47
1. Scenario 1 – A department of Planners/Project Controllers ………………………………………... 48
2. Scenario 2 – A combined department – Planners and Quantity Surveyors ……………………… 49
3. Scenario 3 – Separate disciplines performing project control ….…………………………………... 50
4. Scenario 4 – Decentralised approach led by the Project Manager ……………………………….. 51
5. Structure of the Department 53
1. The wider / integrated view ………………………………………..…………………………………… 53
2. The narrower / separatist view …………………………………………………………………………. 54
3. Other considerations ……………………………………………………………………………………. 55
6. The basic supporting documentation 56
1. Supporting the Project Management Plan (PMP) ……………………………………………………. 56
2. The Project Control Plan …………………………………………..…………………………………… 62
3. The Communications tools ……………………………………….…………………………………….. 70
7. Project Control Software Tools 74
1. Integrated or Separate software tools – ‘Systems thinking’ ………………………………………… 76
2. What to avoid ……………………………………………………….……………………………………. 80
3. Using one or more software tools ……………………………………………………………………… 80
4. Other reasons for integration …………………………………………………………………………... 82
5. Integration with other tools ……………………………………………………………………………... 83

i ii