Comprehensive Project Management Report: SIM335 Managing Projects

This project management report for the SIM335 Managing Projects module details the key characteristics of projects, scope statements, work breakdown structures (WBS), Gantt charts, budget generation approaches, and risk management strategies. It includes a full project Gantt chart with a critical path analysis and outlines various responses to project risks. The report also addresses quality methods for ensuring successful project completion. Furthermore, it presents a case study involving the merger acquisition of ABC, PLC, and DEF Ltd, utilizing agile development methodology with specific sprints for initialization, structuring merged principles, inventory development, planning, and execution. The report covers project scope, milestone lists, project schedules, resource management plans, and cost budgets, concluding with a risk management plan to facilitate a successful merger. Desklib provides access to similar solved assignments and past papers for students.

Running head: PROJECT MANAGEMENT REPORT
Faculty of Business and Law
Module: SIM335 Managing Projects
Assignment Code: SIM335
Student Name:
Student ID:

1PROJECT MANAGEMENT REPORT
Table of Contents
Task 1...............................................................................................................................................2
Task 2...............................................................................................................................................7
Introduction and Background......................................................................................................7
1. Project Management Approach...............................................................................................7
2. Project Scope...........................................................................................................................8
3. Milestone List..........................................................................................................................8
4. Project Schedule and Work Breakdown Structure..................................................................9
5. Project Lifecycle....................................................................................................................13
6. Project Deliverables...............................................................................................................14
7. Resource Management Plan..................................................................................................14
8. Cost Budget...........................................................................................................................16
9. Risk Management Plan..........................................................................................................17
Conclusion.................................................................................................................................17
Bibliography..................................................................................................................................19

2PROJECT MANAGEMENT REPORT
Task 1
1) Define the key characteristics of any project.
The key characteristics of the project include the factors that are supportive for the
implication of the effective system development operations. The key characteristic factors for the
project are,
Exclusive requirements: The requirements of the project are exclusive and it is
completely different for each of the project. It is possible that the some of the project activities
might be same with other projects. However, most of the requirements are unique for each of the
projects.
Client Based: The project activities are aligned with the demands of the project client and
it is possible that the project can utilize the alignment of the specific requirements of the client.
The client’s final approval is required for the successful completion of the project. Hence,
aligning the project based on client’s demand is the primary requirement for the project.
Profit Dependent: The value of the project activities are aligned with value based
outcomes in terms of profit acquisition. The integration alignment of project activities would
align with the deployment of the effective profit generation for the project investors.
2) What is the Scope Statement for a project? What role does the Work Breakdown Structure
(WBS) have in such a statement?
The specific and detailed description of the project deliverables is pointed out in the short
scope statement for ensuring that the project objectives are explained clearly. The consideration
of the activities would support the simplification of the activities that are capable of integrating

3PROJECT MANAGEMENT REPORT
the project objectives. The scope statement would help in understanding the success criteria for
the project.
Work breakdown structure is the listing of the works required in the project for
developing the project activities. The project activities can be summarized into some specific
class or work package that would be required for the completion of the project. The work
packages would combine for listing the alignment of the specific work development for the
project and it is termed as work breakdown structure. The work breakdown structure of the
project would support the completion of the project activities. The specific objectives of the
project would combine with the alignment of the work packages developed.
3) Using the information below, plot out a full project Gantt chart and identify the critical path.
How many days does it take to complete the project?
The project Gantt chart is given below,
ID Task
Mode
Task Name Duration Start Finish Predecessors
0 Project Summary19 days Mon 7/9/18 Thu 8/2/18
1 a 5 days Mon 7/9/18 Fri 7/13/18
2 b 4 days Mon 7/16/18 Thu 7/19/18 1
3 c 2 days Fri 7/20/18 Mon 7/23/18 2
4 d 3 days Fri 7/20/18 Tue 7/24/18 2
5 e 5 days Tue 7/24/18 Mon 7/30/18 3
6 f 7 days Wed 7/25/18 Thu 8/2/18 4
T M F T S W S T M
Jul 1, '18 Jul 15, '18 Jul 29, '18
The critical tasks of the project are abdf and it is shown below,

4PROJECT MANAGEMENT REPORT
ID Task
Mode
Task Name Duration Start Finish Predecessors
0 Project Summary19 days Mon 7/9/18 Thu 8/2/18
1 a 5 days Mon 7/9/18 Fri 7/13/18
2 b 4 days Mon 7/16/18 Thu 7/19/18 1
3 c 2 days Fri 7/20/18 Mon 7/23/18 2
4 d 3 days Fri 7/20/18 Tue 7/24/18 2
5 e 5 days Tue 7/24/18 Mon 7/30/18 3
6 f 7 days Wed 7/25/18 Thu 8/2/18 4
T M F T S W S T M
Jul 1, '18 Jul 15, '18 Jul 29, '18
The project would exhaust a sum total of 19 days for the completion of the project. The
project duration summary is given below,
Task Duration
a 5
b 4
d 3
f 7
Tota
l
19
4) What approaches exist to generate a budget for a specific project budget?
The project budget estimation can be achieved using the bottom up approach as it would
involve the consideration of the effective documentation forming the alignment of the effective
process integration. The budget for the project would be developed using the following steps,
Step 1 Calculating the direct cost labour for the project
Step 2 Cost of materials is evaluated and estimated for the project
Step 3 Cost Expense for the transportation is evaluated for the completion of the project
Step 4 Salaries of human resources that would be involved in the project would be calculated

5PROJECT MANAGEMENT REPORT
Step 5 Cost expended on the equipments and the software would be considered
Step 6 All cost would be summed for calculating the total expenses of the project
Step 7 An infringement of +10% would be added for developing the total budget for the
project
5) How can project risk arise? Outline the various responses to risk that may be taken within
project management.
The project risk can result in forming the alignment of the major issues that would result
in forming the problems for the project execution. The implication of the risk analysis would
help in sorting out the major problems that the project might face due to the execution of the
project activities. The project risk analysis would include the process of identifying the risk,
evaluate its impact areas, and develop mitigation strategies for the execution of the project
successfully.
Causes of risk Risk response plan
Risk factors can be accidental or deliberate
depending upon the causes of the risk. The
various causes of the risk include lack of
documentation, absence of the resources, lack of
proper documentation, unskilled workers, and
communication noises, inaccurate estimation,
and poor development.
The response plan for the risk factors would include
the development of the risk mitigation planning and it
is started with the identification of the risk factors.
The impact analysis for the risk would be done for
understanding the root causes for the project. The
mitigation strategies would be developed for dealing
with the issues of the risk factors.

6PROJECT MANAGEMENT REPORT
6) What quality methods (project evaluation, monitoring and control) would you introduce to
ensure a project is completed successfully?
The project evaluation, monitoring and control would be deployed in the project for
easing the processes of the improved communication and deployment. The following methods
would be deployed in the project for ensuring the completion of the project,
Project Evaluation is developed for keeping whether the activities of the project would be
completed in the estimated time and budget. The analysis of the project activities would support
the implication of the proper documentation and the completion of the project
Monitoring and Control is deployed for making the required modification in the
completion of the effective project execution and deployment. The controlling of the project
activities would align with the successive formation of the operations.

7PROJECT MANAGEMENT REPORT
Task 2
Introduction and Background
The report would be developed for the analysis of the activities and aligning the
utilization of the operations for supporting the implication of the improved functional
development. The project report would be deployed for easing the processes of forming the
utilization of the project management principles. The effective use of the project management
principles would be helpful for easing the merger of ABC, PLC, and DEF Ltd. The report would
involve the utilization of the techniques of project lifecycle analysis, project management,
planning, cost management, quality management, resource management, scope management, and
controlling for the merger of the three organizations.
The project is merger acquisition based for the development of the effective support to
the utilization of the improved communication and development. The project is titled Merger
Acquisition Project for ABC, PLC, and DEF Ltd. The completion of the project would support
the utilization of the improved activities. The alignment would be helpful for the execution of the
improved communication and implication of the project management concepts for the project.
The completion of the merger would help the three organizations for supporting and developing
their specific factors for including the saint factors that would support the merger of the two
companies.
1. Project Management Approach
The project of Merger Acquisition Project for ABC, PLC, and DEF Ltd has been
completed using the agile development methodology and hence specific sprints are included in

8PROJECT MANAGEMENT REPORT
project. Each of the sprints would comprise of developing the project activities while supporting
the inclusion of a specific deliverable and a milestone for the project. The five sprints of the
project are initialization, structuring the merged principles, inventory development, planning, and
execution of activities. The use of the agile methodology would help in easing the project
execution and the development of the effective implication development.
2. Project Scope
The project of Merger Acquisition Project for ABC, PLC, and DEF Ltd is a merger
acquisition project and it involves the following points,
 Formation of the structure supporting the operations of the three organizations in
an integrated organizational structure
 Forming the inventory that would support the information processing for the
organizations
 Developing communication process, integration plan, and initiating the staff
retention activities
3. Milestone List
The project of Merger Acquisition Project for ABC, PLC, and DEF Ltd has been
completed using the agile development methodology and hence specific sprints are included in
project. Each of the sprints would comprise of developing the project activities while supporting
the inclusion of a specific deliverable and a milestone for the project. The milestones represent
the various initial and end points of a sprint for the project. The following are the milestones of
the project,

9PROJECT MANAGEMENT REPORT
WB
S Task Name Duration Start Finish
1 Initialization 11 days Tue 6/12/18 Tue 6/26/18
1.5 Project kick off 0 days Tue 6/26/18 Tue 6/26/18
2 Structuring the merged principles 13 days Wed
6/27/18 Fri 7/13/18
2.5 Structuring completed 0 days Fri 7/13/18 Fri 7/13/18
3 Inventory Development 13 days Mon
7/16/18 Wed 8/1/18
3.5 Inventory Integration 0 days Wed 8/1/18 Wed 8/1/18
4 Planning 20 days Thu 8/2/18 Wed 8/29/18
4.6 Approval of plans 0 days Wed
8/29/18 Wed 8/29/18
5 Execution of Activities 49 days Thu 8/30/18 Tue 11/6/18
5.5 Closure 0 days Tue 11/6/18 Tue 11/6/18
4. Project Schedule and Work Breakdown Structure
The schedule for the project of Merger Acquisition Project for ABC, PLC, and DEF Ltd
is given below,
WBS Task Name Duration Start Finish
0 Merger Acquisition Project for ABC, PLC, and
DEF Ltd. 106 days Tue 6/12/18 Tue 11/6/18
1 Initialization 11 days Tue 6/12/18 Tue 6/26/18
1.1 Requirement Analysis 3 days Tue 6/12/18 Thu 6/14/18
1.2 Development of documents 5 days Fri 6/15/18 Thu 6/21/18
1.3 Defining the objectives 2 days Fri 6/22/18 Mon 6/25/18

10PROJECT MANAGEMENT REPORT
1.4 Signing off the documents 1 day Tue 6/26/18 Tue 6/26/18
1.5 Project kick off 0 days Tue 6/26/18 Tue 6/26/18
2 Structuring the merged principles 13 days Wed 6/27/18 Fri 7/13/18
2.1 Guidelines are developed 3 days Wed 6/27/18 Fri 6/29/18
2.2 Merger Structure is developed 4 days Mon 7/2/18 Thu 7/5/18
2.3 Expanding the culture 3 days Fri 7/6/18 Tue 7/10/18
2.4 Business, Operations, and System analysis 3 days Wed 7/11/18 Fri 7/13/18
2.5 Structuring completed 0 days Fri 7/13/18 Fri 7/13/18
3 Inventory Development 13 days Mon 7/16/18 Wed 8/1/18
3.1 Pre Closure data backup 3 days Mon 7/16/18 Wed 7/18/18
3.2 Strategic meetings 5 days Thu 7/19/18 Wed 7/25/18
3.3 Support Plan development for tactical
problems 2 days Thu 7/26/18 Fri 7/27/18
3.4 Governance and Strategy is integrated 3 days Mon 7/30/18 Wed 8/1/18
3.5 Inventory Integration 0 days Wed 8/1/18 Wed 8/1/18
4 Planning 20 days Thu 8/2/18 Wed 8/29/18
4.1 Activities are listed 2 days Thu 8/2/18 Fri 8/3/18
4.2 Schedule is developed 3 days Mon 8/6/18 Wed 8/8/18
4.3 Complete Plan is developed 7 days Thu 8/9/18 Fri 8/17/18
4.4 Staff Retention plan 4 days Mon 8/20/18 Thu 8/23/18
4.5 Integration Plan 4 days Fri 8/24/18 Wed 8/29/18
4.6 Approval of plans 0 days Wed 8/29/18 Wed 8/29/18
5 Execution of Activities 49 days Thu 8/30/18 Tue 11/6/18
5.1 Planning the implementation 2 days Thu 8/30/18 Fri 8/31/18

11PROJECT MANAGEMENT REPORT
5.2 Executing the implementation process 14 days Mon 9/3/18 Thu 9/20/18
5.3 Business, Operations, and System analysis 30 days Fri 9/21/18 Thu 11/1/18
5.4 Documenting the lessons learnt 3 days Fri 11/2/18 Tue 11/6/18
5.5 Closure 0 days Tue 11/6/18 Tue 11/6/18
The following is the Gantt chart for the Merger Acquisition Project for ABC, PLC, and
DEF Ltd project,

12PROJECT MANAGEMENT REPORT
ID Task
Mode
WBS Task Name Duration Start Finish
0 0 Merger Acquisition Project for
ABC, PLC, and DEF Ltd.
106 days Tue 6/12/18 Tue 11/6/18
1 1 Initialization 11 days Tue 6/12/18 Tue 6/26/18
2 1.1 Requirment Analysis 3 days Tue 6/12/18 Thu 6/14/18
3 1.2 Development of documents 5 days Fri 6/15/18 Thu 6/21/18
4 1.3 Defining the objectives 2 days Fri 6/22/18 Mon 6/25/18
5 1.4 Signing off the documents 1 day Tue 6/26/18 Tue 6/26/18
6 1.5 Project kick off 0 days Tue 6/26/18 Tue 6/26/18
7 2 Structuring the merged principles13 days Wed 6/27/18 Fri 7/13/18
8 2.1 Guidelines are developed 3 days Wed 6/27/18 Fri 6/29/18
9 2.2 Merger Structure is developed 4 days Mon 7/2/18 Thu 7/5/18
10 2.3 Expanding the culture 3 days Fri 7/6/18 Tue 7/10/18
11 2.4 Business, Operations, and
System analysis
3 days Wed 7/11/18 Fri 7/13/18
12 2.5 Structuring completed 0 days Fri 7/13/18 Fri 7/13/18
13 3 Inventory Development 13 days Mon 7/16/18 Wed 8/1/18
14 3.1 Pre Closure data backup 3 days Mon 7/16/18 Wed 7/18/18
15 3.2 Strategic meetings 5 days Thu 7/19/18 Wed 7/25/18
16 3.3 Support Plan development for
tactical problems
2 days Thu 7/26/18 Fri 7/27/18
17 3.4 Governance and Strategy is
integrated
3 days Mon 7/30/18 Wed 8/1/18
18 3.5 Inventory Integration 0 days Wed 8/1/18 Wed 8/1/18
19 4 Planning 20 days Thu 8/2/18 Wed 8/29/18
20 4.1 Activities are listed 2 days Thu 8/2/18 Fri 8/3/18
21 4.2 Schedule is developed 3 days Mon 8/6/18 Wed 8/8/18
22 4.3 Complete Plan is developed 7 days Thu 8/9/18 Fri 8/17/18
23 4.4 Staff Retention plan 4 days Mon 8/20/18 Thu 8/23/18
24 4.5 Integration Plan 4 days Fri 8/24/18 Wed 8/29/18
25 4.6 Approval of plans 0 days Wed 8/29/18 Wed 8/29/18
26 5 Execution of Activities 49 days Thu 8/30/18 Tue 11/6/18
27 5.1 Planning the implementation 2 days Thu 8/30/18 Fri 8/31/18
28 5.2 Executing the implementation
process
14 days Mon 9/3/18 Thu 9/20/18
29 5.3 Business, Operations, and
System analysis
30 days Fri 9/21/18 Thu 11/1/18
30 5.4 Documenting the lessons learnt3 days Fri 11/2/18 Tue 11/6/18
31 5.5 Closure 0 days Tue 11/6/18 Tue 11/6/18
Analyst
Documenter
Analyst
Documenter
6/26
Negotiator
Acquisitor
Acquisitor
Negotiator
7/13
Database Admin
Executives
Acquisitor
Executives
8/1
Planner
Planner
Planner
HR Manager
Planner
8/29
Planner
Staff
Staff
Documenter
11/6
T F S S M T W T F S S M T W T F S S M T W T F
May 20, '18 Jun 10, '18 Jul 1, '18 Jul 22, '18 Aug 12, '18 Sep 2, '18 Sep 23, '18 Oct 14, '18 Nov 4, '18 Nov 25, '18
The following is the work breakdown structure for the project of Merger Acquisition
Project for ABC, PLC, and DEF Ltd,

13PROJECT MANAGEMENT REPORT
Merger Acquisition Project
for ABC, PLC, and DEF
Ltd.
Initialization
Requirment Analysis
Development of
documents
Defining the
objectives
Signing off the
documents
Project kick off
Structuring the merged
principles
Guidelines are
developed
Merger Structure is
developed
Expanding the
culture
Business,
Operations, and
System analysis
Structuring
completed
Inventory Development
Pre Closure data
backup
Strategic meetings
Support Plan
development for
tactical problems
Governance and
Strategy is
integrated
Inventory
Integration
Planning
Activities are listed
Schedule is
developed
Complete Plan is
developed
Staff Retention plan
Integration Plan
Approval of plans
Execution of Activities
Planning the
implementation
Executing the
implementation
process
Business,
Operations, and
System analysis
Documenting the
lessons learnt
Closure
5. Project Lifecycle
The project of Merger Acquisition Project for ABC, PLC, and DEF Ltd has been
completed using the agile development methodology and hence specific sprints are included in
project. Each of the sprints would comprise of developing the project activities while supporting
the inclusion of a specific deliverable and a milestone for the project. The five sprints of the
project are initialization, structuring the merged principles, inventory development, planning, and
execution of activities. These sprints have been explained below,
a) The initialization comprises of requirement analysis, development of documents,
defining the objectives, and signing off the documents. The deliverable for the
sprint is initial documents and the milestone for the sprint is project kick off.
b) The structuring the merged principles comprise of guidelines are developed,
merger structure is developed, expanding the culture, and business, operations,

14PROJECT MANAGEMENT REPORT
and system analysis. The sprint has the deliverable for specific merger structure
and the milestone of structuring completed.
c) The inventory development comprise of pre closure data backup, strategic
meetings, support plan development for tactical problems, governance and
strategy is integrated, and inventory integration.
d) The planning comprise of activities are listed, schedule is developed, complete
plan is developed, staff retention plan, and integration plan. The various plans
would act as the deliverable for the sprint and the approval of plans is the
milestone.
e) The execution of activities would comprise of planning the implementation,
executing the implementation process, business, operations, and system analysis,
documenting the lessons learnt, and closure.
6. Project Deliverables
The project of Merger Acquisition Project for ABC, PLC, and DEF Ltd has been
completed using the agile development methodology and hence specific sprints are included in
project. Each of the sprints would comprise of developing the project activities while supporting
the inclusion of a specific deliverable and a milestone for the project. The deliverables for the
project are initial documents, specific merger structure, pre closure data backup, various plans
(project plan, staff retention plan, and integration plan), and final reports.
7. Resource Management Plan

15PROJECT MANAGEMENT REPORT
The project of Merger Acquisition Project for ABC, PLC, and DEF Ltd would require a
number of human resources like analyst, documenter, negotiator, acquisitor, database admin,
executives, planner, hr manager, and staff.
Resource Name Activities Involved in Work
Analyst
Requirement Analysis 24 hrs
Defining the objectives 16 hrs
Documenter
Development of documents 40 hrs
Signing off the documents 8 hrs
Documenting the lessons learnt 24 hrs
Negotiator
Guidelines are developed 24 hrs
Business, Operations, and System analysis 24 hrs
Acquisitor
Merger Structure is developed 32 hrs
Expanding the culture 24 hrs
Support Plan development for tactical problems 16 hrs
Database Admin Pre Closure data backup 24 hrs
Executives
Strategic meetings 40 hrs
Governance and Strategy is integrated 24 hrs
Planner
Activities are listed 16 hrs
Schedule is developed 24 hrs
Complete Plan is developed 56 hrs
Integration Plan 32 hrs
Planning the implementation 16 hrs
HR Manager Staff Retention plan 32 hrs
Staff Executing the implementation process 112 hrs

16PROJECT MANAGEMENT REPORT
Business, Operations, and System analysis 240 hrs
ID Resource Name Work
1 Analyst 40 hrs
2 Documenter 72 hrs
3 Negotiator 48 hrs
4 Acquisitor 72 hrs
5 Database Admin 24 hrs
6 Executives 64 hrs
7 Planner 144 hrs
8 HR Manager 32 hrs
9 Staff 352 hrs
Details
Work
Work
Work
Work
Work
Work
Work
Work
Work
T T S F W M S T T S F W M S T
Jun 3, '18 Jul 1, '18 Jul 29, '18 Aug 26, '18 Sep 23, '18 Oct 21, '18 Nov 18, '18
24h 16h
16h 32h 24h
24h 16h 8h
56h 16h
24h
32h 32h
16h 80h 32h 16h
32h
48h 72h 72h 64h 64h 32h
8. Cost Budget
The project of Merger Acquisition Project for ABC, PLC, and DEF Ltd has the following
project budget plan,
Resource Name Work Standard Rate Cost
Analyst 40 hrs £50.00/hr £2,000.00
Documenter 72 hrs £70.00/hr £5,040.00
Negotiator 48 hrs £90.00/hr £4,320.00
Acquisitor 72 hrs £100.00/hr £7,200.00
Database Admin 24 hrs £120.00/hr £2,880.00
Executives 64 hrs £150.00/hr £9,600.00
Planner 144 £80.00/hr £11,520.00

17PROJECT MANAGEMENT REPORT
hrs
HR Manager 32 hrs £125.00/hr £4,000.00
Staff
352
hrs
£65.00/hr £22,880.00
9. Risk Management Plan
The risk management plan comprises of developing effective strategies for dealing with
the probable risk factors. The risk management plan comprises of identifying the risk factors,
analysing the impact of the risks, and developing the mitigation strategies. The Merger
Acquisition Project for ABC, PLC, and DEF Ltd would have the following risk management
plan,
Risk Identification Risk Analysis Risk Mitigation
The identification of the risk is
based on the consideration of
the probable risk factors that
would help in easing the
processing of the project and
identifying the possible issues
that the organization might
face in the due course for the
completion of the project.
The analysis of the risk factors
would result in forming the major
factor analysis for the project so
that the implication of the
probable risk would help them in
supporting the utilization of the
risk mitigation. The analysis
would help in listing the probable
reasons that would result in
forming the problems for the
execution of the project activities.
The mitigation of the risk is
initiated by forming some
strategies convenient for the
development of the support
strategies for the execution of the
project. The risk mitigation would
help them in forming the effective
listing of the operations. The risk
mitigation is also helpful for easing
the process of reducing the impact
on the project activities.
Conclusion
The report had been developed for the analysis of the activities and aligning the
utilization of the operations for supporting the implication of the improved functional

18PROJECT MANAGEMENT REPORT
development. The effective use of the project management principles had been helpful for easing
the merger of ABC, PLC, and DEF Ltd. The report had involve the utilization of the techniques
of project lifecycle analysis, project management, planning, cost management, quality
management, resource management, scope management, and controlling for the merger of the
three organizations. The completion of the project had support the utilization of the improved
activities. The alignment had been helpful for the execution of the improved communication and
implication of the project management concepts for the project. The completion of the merger
had help the three organizations for supporting and developing their specific factors for including
the saint factors that had support the merger of the two companies. The five sprints of the project
were initialization, structuring the merged principles, inventory development, planning, and
execution of activities. The use of the agile methodology had help in easing the project execution
and the development of the effective implication development. The deliverables for the project
were initial documents, specific merger structure, pre closure data backup, various plans (project
plan, staff retention plan, and integration plan), and final reports. The project of Merger
Acquisition Project for ABC, PLC, and DEF Ltd had require a number of human resources like
analyst, documenter, negotiator, acquisitor, database admin, executives, planner, HR manager,
and staff.

19PROJECT MANAGEMENT REPORT
Bibliography
Binder, J. 2016. Global project management: communication, collaboration and management
across borders. Routledge.
Brioso, X. 2015. Integrating ISO 21500 guidance on project management, lean construction and
PMBOK. Procedia Engineering, 123, 76-84.
Brooks, J., and King, N. 2014. Doing template analysis: evaluating an end of life care service.
Sage Research Methods Cases.
Cascante, I. L., Martin, F. M., Zubizarreta, J. P. O., and Aranburu, M. S. 2016, June. Three
Historic Stages in the Graphic Confection of Project Documentation. BIM: Meetings in the Third
Phase of the XXI Century. In Congreso Internacional de Expresión Gráfica Arquitectónica (pp.
1089-1097). Springer, Cham.
Chaves, M. S., Araújo, C. D., Teixeira, L., Rosa, D., Júnior, I., and Nogueira, C. 2016. A new
approach to managing Lessons Learned in PMBoK process groups: the Ballistic 2.0 Model.
International Journal of Information Systems and Project Management, 4(1), 27-45.
Coppola, D., D'Ambrogio, A., and Gianni, D. 2016. Bringing Model-based Systems Engineering
Capabilities to Project Management: an Application to PRINCE2. In CIISE (pp. 6-15).
Drouart, G., De Breuck, C., Vernet, J., Seymour, N., Lehnert, M., Barthel, P., ... and Hatch, N.
2014. Rapidly growing black holes and host galaxies in the distant Universe from the Herschel
Radio Galaxy Evolution Project. Astronomy & Astrophysics, 566, A53.

20PROJECT MANAGEMENT REPORT
Hines, E. E., and Landis, W. G. 2014. Regional risk assessment of the Puyallup River Watershed
and the evaluation of low impact deployment in meeting management goals. Integrated
environmental assessment and management, 10(2), 269-278.
Hussein, B. A., and Ravnå, R. 2015, September. A template for building adaptable project risk
management games. In Intelligent Data Acquisition and Advanced Computing Systems:
Technology and Applications (IDAACS), 2015 IEEE 8th International Conference on (Vol. 2, pp.
535-542). IEEE.
Jamali, G., and Oveisi, M. 2016. A Study on Project Management Based on PMBOK and
PRINCE2. Modern Applied Science, 10(6), 142.
Karaman, E., and Kurt, M. 2015. Comparison of project management methodologies: prince 2
versus PMBOK for it projects. Int. Journal of Applied Sciences and Engineering Research, 4(5),
657-664.
Kerzner, H., and Kerzner, H. R. 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Larson, E.W., Gray, C.F. and Irwin, M.H., 2016. University of Missouri–St.
Louis…………………. Syllabus LOGOM 6347... Project Management InfoSys 6847…
Financial and Project Management Fall 2016 A Blended Offering.
Lientz, B., and Rea, K. 2016. Breakthrough technology project management. Routledge.
Luo, Y., Melillo, J., Niu, S., Beier, C., Clark, J.S., Classen, A.T., Davidson, E., Dukes, J.S.,
Evans, R.D., Field, C.B. and Czimczik, C.I., 2011. Coordinated approaches to quantify long‐term
ecosystem dynamics in response to global change. Global Change Biology, 17(2), pp.843-854.

21PROJECT MANAGEMENT REPORT
Maylor, H., 2001. Beyond the Gantt chart:: Project management moving on. European
Management Journal, 19(1), pp.92-100.
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and
technology. Taylor & Francis.
Nicholas, J.M., 2004. Project management for business and engineering: Principles and
practice. Elsevier.
Oya, T., Mehdad, Y., Carenini, G., and Ng, R. 2014. A template-based abstractive meeting
summarization: Leveraging summary and source text relationships. In Proceedings of the 8th
International Natural Language Generation Conference (INLG) (pp. 45-53).
Pinto, J., 2010. Achieving Competitive Advantage. Prentice-Hall, Upper Saddle River, NJ.
Rekker, S. 2016. Converting planetary boundaries into action, a new approach to meeting global
greenhouse gas targets: A pitch. Accounting and Management Information Systems, 15(1), 160-
167.
Rybka, I., Bondar-Nowakowska, E., and Połoński, M. 2015. Management of Alterations to
Project Documentation–a Case Study of Water Supply and Sewerage Works. International
Journal of Contemporary Management, 2015Numer 14 ((3)), 41-57.
Schwalbe, K. 2015. Information technology project management. Cengage Learning.
Snyder, C. S. 2014. A guide to the project management body of knowledge: PMBOK (®) guide.
Project Management Institute: Newtown Square, PA, USA.
Snyder, C., and Dionisio, C. S. 2017. A project manager's book of forms: A companion to the
PMBOK guide. John Wiley & Sons.

22PROJECT MANAGEMENT REPORT
Spikol, D., Ehrenberg, N., Cuartielles, D., and Zbick, J. 2015. Design Strategies for developing a
Visual Platform for Physical Computing with Mobile Tools for Project Documentation and
Reflection.