Project Closure and Evaluation Plan

The assignment focuses on establishing a comprehensive framework for project closure. It includes a detailed checklist ensuring all project deliverables are captured, from initial charters to final test results. Additionally, the assignment delves into an evaluation plan outlining key criteria for assessing project success, encompassing performance metrics, adherence to requirements, timeliness, and overall quality.

Project Charter and Management Plan
Project Client Organisation:
Contact:
System Name <<To be created by team and client>>
Date of Charter <<Date of this version>>
Document Status Draft / Approved <<delete one>>
Document
Reference
<<FileName.doc>>
Version Number Version 1<<update as necessary, in whole
tmp51sgqbl1.doc 1 of 24

numbers>>
Prepared by <<Technical Writer>>
Team Members << Names of other team members>>
tmp51sgqbl1.doc 2 of 24

1. Change History
All changes to the Project Charter must be recorded in the Change History, and a new version of the charter must be approved by the client.
Date Description of
Change
Reason for
Change
Author of
Change
Version No.
dd/mm/06 Initial draft N/A Version 1
Version 2
Version 3
2. Authorised by:
<<Name of client representative authorising this charter & plan>>
Name: ________________________
Signature: ________________________
Date: ________________________
tmp51sgqbl1.doc 3 of 24

Table of Contents
1. CHANGE HISTORY............................................................................................................................................................................................................................................3
2. AUTHORISED BY:...............................................................................................................................................................................................................................................3
3. PART 1 - PROJECT CHARTER.........................................................................................................................................................................................................................6
3.1. MEASURABLE ORGANIZATIONAL VALUE.......................................................................................................................................................................................................6
3.2. DESIRED AREA OF IMPACT..............................................................................................................................................................................................................................6
3.3. VALUE OF THE PROJECT.................................................................................................................................................................................................................................7
3.4. STAKEHOLDER TARGET AND EXPECTATION....................................................................................................................................................................................................7
3.5. DETERMINING THE TIMEFRAME FOR ACHIEVING THE MEASURABLE ORGANIZATIONAL VALUE...................................................................................................................8
3.6. SUMMARIZING THE MEASURABLE ORGANIZATIONAL VALUE.......................................................................................................................................................................9
4. PART 2 – SCOPE MANAGEMENT PLAN (A BRIEF VERSION)..............................................................................................................................................................10
4.1. SCOPE OF THE PROJECT................................................................................................................................................................................................................................10
4.2. LIST OF RESOURCES.....................................................................................................................................................................................................................................11
5. PART THREE: WORK BREAKDOWN STRUCTURE OF PROJECT......................................................................................................................................................12
5.1. WORK BREAKDOWN STRUCTURE OF THE PROJECT.......................................................................................................................................................................................12
5. 2. PROJECT MILESTONES.............................................................................................................................................................................................................................19
6. PART FOUR: PROJECT RISK ANALYSIS AND PLAN..............................................................................................................................................................................20
6.1. ASSUMPTIONS...............................................................................................................................................................................................................................................20
6.2. RISK ASSESSMENT........................................................................................................................................................................................................................................20
6.2.1 Risk Rating..............................................................................................................................................................................................................................................20
6.2.2 Risk Mitigation........................................................................................................................................................................................................................................21
7. PART FIVE: QUALITY MANAGEMENT PLAN..........................................................................................................................................................................................21
7.1. PHILOSOPHY OF THE TEAM...........................................................................................................................................................................................................................21
7.2. ENSURING QUALITY......................................................................................................................................................................................................................................21
7.2.1 A set of verification activities..................................................................................................................................................................................................................21
7.2.2 A set of validation activities....................................................................................................................................................................................................................21
8. PART SIX: PROJECT CLOSURE AND EVALUATION..............................................................................................................................................................................22
tmp51sgqbl1.doc 4 of 24

8.1. ANNOTATED BIBLIOGRAPHY........................................................................................................................................................................................................................22
8.2. CLOSURE CHECKLIST....................................................................................................................................................................................................................................22
8.3. EVALUATION PLAN.......................................................................................................................................................................................................................................23
9. References..............................................................................................................................................................................................................................................................24
tmp51sgqbl1.doc 5 of 24

3. PART 1 - Project Charter
In this report, it mainly discussed about the detailed information related with the RALS Roistering project that mainly undertaken by Virtucon from
Globex.
3.1. Measurable Organizational Value
The Rivererina Agriculture and Lifestyle Show held by BT & Sons Farming Equipments on November 2009. This particular show is mainly pre-
arranged to display different agricultural equipments, products and so forth. From few years, RALS increases the business much in size and also
requires having the active participation of numbers of volunteers to have successful demonstration. Numbers of professionals appointed by Globex
managed all the data and information that mainly linked with all volunteers manually. On the other hand, managing all information becomes more
time consuming process as volunteer numbers get increased in rapid manner. Hence, Globex undertook all tasks to develop the roistering system to
store all details of volunteers who are participating in RALS.
3.2. Desired area of impact
The impact of project that observed in this project is mainly discussed below:
a. Operations: Successful implementation of roster system would create the task to maintain all details of RALS employees in much easier
manner.
b. Strategy: the implementation of RALS system leads to facilitate the tracking process of volunteers who mainly participate in this show.
c. Financial: the system also requires much initial investments that also expect the long run Globex to obtain the benefits of same.
d. Customers: the system mainly designed to do the internal usage of Globex and also created the considerable impact on customers.
e. Social: the project causes no impact on society at any large extent.
tmp51sgqbl1.doc 6 of 24

3.3. Value of the Project
Sl. No Value Project Attribute
1 Better Quality concern of project
Data security
2 Faster Response time
3 Cheaper Resource cost
4 Do more Storing of contact details of volunteers
Storage of previous work experience of volunteers
3.4. Stakeholder target and expectation
The following table provides an extensive analysis all the stakeholders associated with the project
Sl.
No
Stakeholder Target Expectation
Organizational Increase of business profit, More profit
tmp51sgqbl1.doc 7 of 24

head retention of employees outcomes
Project
Management team
Proper management of project
resources, time management to
deliver the project on-time
Proper delivery of
the project
depending on
given time, costs
etc
Volunteers Customers Helps them to
have the proper
understanding
about the
Roistering system
Employees Business Take active part to
run the business
and also in the
earning of profit
under guidance of
project
management team
3.5. Determining the timeframe for achieving the Measurable Organizational Value
The estimated required time frame to achieve the measurable organizational value provided in the below table:
Task Name Duration Start Finish
RALS Roster Project 260 days Mon
01/02/17 Fri 12/29/17
Project starts 0 days Mon
01/02/17
Mon
01/02/17
tmp51sgqbl1.doc 8 of 24

Phase 1: Project Startup 25 days Mon
01/02/17 Fri 02/03/17
Phase 2: Solution Requirements Analysis 36 days Mon
02/06/17
Mon
03/27/17
Phase 3: Solution Design 47 days Tue
03/28/17
Wed
05/31/17
Phase 4: Prototype 38 days Thu
06/01/17
Mon
07/24/17
Phase 5: Iteration 1 35 days Tue
07/25/17
Mon
09/11/17
Phase 6: Iteration 2 18 days Tue
09/12/17
Thu
10/05/17
Phase 7:Iteration 3 18 days Fri 10/06/17 Tue
10/31/17
Phase 8: Final Release 10 days Wed
11/01/17
Tue
11/14/17
Phase 9: Project Completion 33 days Wed
11/15/17 Fri 12/29/17
End of project 0 days Fri 12/29/17 Fri 12/29/17
3.6. Summarizing the Measurable Organizational Value
The below table mainly discussed about the summarization of MOV of the selected project:
Sl.
No
Measurable Organizational
Value
Attribute
tmp51sgqbl1.doc 9 of 24

1 Goal of the project Development of an automated roster system to
record all volunteers details who mainly
participated in the RALS
2 Area of impact Operational impact, Strategy, Financial,
customer, society
3 Stakeholder All employees of Globex including the
organizational heads manage the all records of
volunteers who mainly participated in RALS,
and also the project team that mainly appointed
by Virtucon
4 Time schedule to achieve the
MOV value
260 day
4. PART 2 – Scope Management Plan (a brief version)
4.1. Scope of the Project
In Scope Includes
System Functions The system mainly designed that allows to maintain the
volunteers records who participated in RALS based on
the below aspects:
i. Names of Volunteers
ii. Contact details
iii. The organization who offers the services
iv. Qualifications of volunteers
System Documentation i. Use case models of system
ii. Elaborated functional descriptions of system
iii. Various hardware requirements to run the
system
tmp51sgqbl1.doc 10 of 24

The project will not provide:
Out of Scope Includes
System support and
enhancements
Provide after sales support to client (installation of
system)
Training Giving training to all Globex employees who use the
roistering system
System maintenance The proper maintenance of system where the roster
system are installed will not be taken in consideration
within the scope of project
4.2.List of Resources
Table 1: Resources required for the project
Resource Name Type Material
Label Initials Group Max.
Units Std. Rate
Project Manager Work P 100% $150.00/hr
Business analyst Work B 200% $80.00/hr
System designer Work S 500% $70.00/hr
System developer Work S 1,000% $70.00/hr
System Tester Work S 600% $70.00/hr
Technical writers Work T 300% $50.00/hr
Hardware components
required for
developing the ICT
Material H $10,000.00
tmp51sgqbl1.doc 11 of 24

system
Software components
required for
developing the ICT
system
Work S 100% $0.00/hr
Testing manager Work T 100% $105.00/hr
Development manager Work D 100% $105.00/hr
5. Part Three: Work Breakdown Structure of project
5.1.Work breakdown structure of the project
Table 1: Work breakdown structure of the project
Outline
Number Task Name Duration Start Finish Predecessors Resource Names Cost
0 RALS Rostering Project 260 days Mon
01/02/17
Fri
12/29/17 $290,600.00
1 Project starts 0 days Mon
01/02/17
Mon
01/02/17 Project Manager $0.00
2 Phase 1: Project Startup 25 days Mon
01/02/17
Fri
02/03/17 $19,840.00
2.1 Gathering information regarding the client
requirements 5 days Mon
01/02/17
Fri
01/06/17 1 Business analyst $3,200.00
2.2 Developing a project charter 3 days Mon Wed 3 Business analyst, $3,120.00
tmp51sgqbl1.doc 12 of 24

01/09/17 01/11/17 Technical writers
2.3 Developing an initial management plan of the
project 5 days Thu
01/12/17
Wed
01/18/17 4 Business analyst,
Technical writers $5,200.00
2.4 Identification of the resources that would be
required for the project 4 days Thu
01/19/17
Tue
01/24/17 5 Business analyst $2,560.00
2.5 Estimation of budgetary requirements 4 days Wed
01/25/17
Mon
01/30/17 6 Business analyst,
Technical writers $4,160.00
2.6 Estimation of time requirements 4 days Tue
01/31/17
Fri
02/03/17 7 Technical writers $1,600.00
2.7 End of project startup phase 0 days Fri
02/03/17
Fri
02/03/17 8 $0.00
3 Phase 2: Solution Requirements Analysis 36 days Mon
02/06/17
Mon
03/27/17 $41,240.00
3.1
Communication with the representatives of
the client to gather information regarding the
specific requirements of the client
7 days Mon
02/06/17
Tue
02/14/17 9
Project Manager,
System designer,
System developer
$16,240.00
3.2 Developing use case models of the system 7 days Wed
02/15/17
Thu
02/23/17 11 System designer $3,920.00
3.3 Review of the use case models by the
representatives of the client 10 days Fri
02/24/17
Thu
03/09/17 12 Project Manager $12,000.00
3.4 Developing the test strategy to be utilized
after the rostering system has been implemented 7 days Fri
03/10/17
Mon
03/20/17 13 Testing manager $5,880.00
3.5 Updating the project plan 5 days Tue
03/21/17
Mon
03/27/17 14 Business analyst $3,200.00
3.6 End of requirement analysis phase 0 days Mon
03/27/17
Mon
03/27/17 15 $0.00
4 Phase 3: Solution Design 47 days Tue
03/28/17
Wed
05/31/17 $35,000.00
4.1 Developing the architectural plan of the 7 days Tue Wed 16 Development $9,800.00
tmp51sgqbl1.doc 13 of 24

proposed system 03/28/17 04/05/17 manager, System
designer
4.2 Architectural plan reviewed by the
representatives of the client 10 days Thu
04/06/17
Wed
04/19/17 18 Development
manager $8,400.00
4.3 Developing detailed architectural plans 15 days Thu
04/20/17
Wed
05/10/17 19 System designer $8,400.00
4.4 Developing the test plan in details 15 days Thu
05/11/17
Wed
05/31/17 20 System Tester $8,400.00
4.5 End of solution design phase 0 days Wed
05/31/17
Wed
05/31/17 21 Project Manager $0.00
5 Phase 4: Prototype 38 days Thu
06/01/17
Mon
07/24/17 $64,320.00
5.1 Developing a prototype of the proposed
solution 20 days Thu
06/01/17
Wed
06/28/17 22
Development
manager, Software
components
required for
developing the ICT
system, System
designer, System
developer,
Hardware
components
required for
developing the ICT
system[1]
$49,200.00
5.2 Making the prototype available to the clients 15 days Thu
06/29/17
Wed
07/19/17 24 Development
manager $12,600.00
5.3 Client accepts system design after reviewing
the prototype 3 days Thu
07/20/17
Mon
07/24/17 25 Development
manager $2,520.00
5.4 End of prototype phase 0 days Mon Mon 26 Project Manager $0.00
tmp51sgqbl1.doc 14 of 24

07/24/17 07/24/17
6 Phase 5: Iteration 1 35 days Tue
07/25/17
Mon
09/11/17 $50,600.00
6.1 Including all functionalities in the prototype
accepted by the client 30 days Tue
07/25/17
Mon
09/04/17 27
System designer,
System developer,
Hardware
components
required for
developing the ICT
system[1],Software
components
required for
developing the ICT
system
$43,600.00
6.2
Designing the test cases that would be
utilized for verifying the operational activities of
the ICT system
5 days Tue
09/05/17
Mon
09/11/17 29
System Tester,
Testing manager,
Software
components
required for
developing the ICT
system
$7,000.00
6.3 End of iteration 1 0 days Mon
09/11/17
Mon
09/11/17 30 Project Manager $0.00
7 Phase 6: Iteration 2 18 days Tue
09/12/17
Thu
10/05/17 $23,520.00
7.1 Conducting tests on the ICT system based in
adherence to the test cases defined in the last
phase
15 days Tue
09/12/17
Mon
10/02/17
31 System Tester,
Testing manager,
Software
components
required for
$21,000.00
tmp51sgqbl1.doc 15 of 24

developing the ICT
system
7.2 Publishing the results of the test cases 3 days Tue
10/03/17
Thu
10/05/17 33 Testing manager $2,520.00
7.3 End of Iteration 2 0 days Thu
10/05/17
Thu
10/05/17 34 Project Manager $0.00
8 Phase 7:Iteration 3 18 days Fri
10/06/17
Tue
10/31/17 35 $26,520.00
8.1 Including changes in the application in
accordance to results of the test cases 10 days Fri
10/06/17
Thu
10/19/17
System designer,
System developer,
Hardware
components
required for
developing the ICT
system[1],Software
components
required for
developing the ICT
system
$21,200.00
8.2 Conducting tests on the application 5 days Fri
10/20/17
Thu
10/26/17 37
System Tester,
Software
components
required for
developing the ICT
system
$2,800.00
8.3 Publishing the results of the testing activities 3 days Fri
10/27/17
Tue
10/31/17 38 Testing manager $2,520.00
8.4 End of Iteration 3 0 days Tue
10/31/17
Tue
10/31/17 39 Project Manager $0.00
9 Phase 8: Final Release 10 days Wed Tue $13,960.00
tmp51sgqbl1.doc 16 of 24

11/01/17 11/14/17
9.1 Developing all necessary documents 7 days Wed
11/01/17
Thu
11/09/17 40 Business analyst,
Testing manager $10,360.00
9.2 Delivering the application and project
documents to the client 3 days Fri
11/10/17
Tue
11/14/17 42 Project Manager $3,600.00
9.3 End of final release phase 0 days Tue
11/14/17
Tue
11/14/17 43 Project Manager $0.00
10 Phase 9: Project Completion 33 days Wed
11/15/17
Fri
12/29/17 $15,600.00
10.1 Developing evaluation reports for all
resources associated with the project 15 days Wed
11/15/17
Tue
12/05/17 44 Technical writers $6,000.00
10.2 Developing review reports 15 days Wed
12/06/17
Tue
12/26/17 46 Technical writers $6,000.00
10.3 Releasing resources 3 days Wed
12/27/17
Fri
12/29/17 47 Project Manager $3,600.00
10.4 End of project completion phase 0 days Fri
12/29/17
Fri
12/29/17 48 Project Manager $0.00
11 End of project 0 days Fri
12/29/17
Fri
12/29/17 49 Project Manager $0.00
tmp51sgqbl1.doc 17 of 24

RALS Rostering Project
Project starts Phase 1: Project Startup
Gathering information
regarding the client
requirements
Developing a
project charter
Developing an initial
management plan of
the project
Identification of the
resources that would
be required for the
project
Estimation of
budgetary
requirements
Estimation of time
requirements
End of project
startup phase
Phase 2: Solution
Requirements Analysis
Communication with
the representatives of
the client to gather
information regarding
the specific
requirements of the
client
Developing use case
models of the
system
Review of the use
case models by the
representatives of
the client
Developing the test
strategy to be utilized
after the rostering
system has been
implemented
Updating the project
plan
End of requirement
analysis phase
Phase 3: Solution Design
Developing the
architectural plan of
the proposed system
Architectural plan
reviewed by the
representatives of
the client
Developing detailed
architectural plans
Developing the test
plan in details
End of solution
design phase
Phase 4: Prototype
Developing a
prototype of the
proposed solution
Making the prototype
available to the
clients
Client accepts
system design after
reviewing the
prototype
End of prototype
phase
Phase 5: Iteration 1
Including all
functionalities in the
prototype accepted
by the client
Designing the test
cases that would be
utilized for verifying
the operational
activities of the ICT
system
End of iteration 1
Phase 6: Iteration 2
Conducting tests on
the ICT system based
in adherence to the
test cases defined in
the last phase
Publishing the
results of the test
cases
End of Iteration 2
Phase 7:Iteration 3
Including changes in
the application in
accordance to results
of the test cases
Conducting tests on
the application
Publishing the results
of the testing
activities
End of Iteration 3
Phase 8: Final Release
Developing all
necessary
documents
Delivering the
application and
project documents
to the client
End of final release
phase
Phase 9: Project
Completion
Developing
evaluation reports for
all resources
associated with the
project
Developing review
reports
Releasing resources
End of project
completion phase
End of project
tmp51sgqbl1.doc 18 of 24

5. 2. Project Milestones
The milestone of this project is mainly listed in the below table:
Project Milestone Deliverable Expected Date
Project Start-up Project charter and project management
plan
3rd February, 2017
Solution
Requirements
Different requirement specifications (use
cases or similar)
Test cases
restructured Project Plan
27th March, 2017
Solution Design Fully implemented architecture as well as
detailed design
Detailed test plan
31st May, 2017
Prototype Various components of solution 24th July, 2017
Iteration Extra functionalities
Test Cases
11th September,
2017
Iteration Test results 5th October, 2017
Iteration Test results 31st October, 2017
Final Release Solutions including all documentations and
rough work
14th November,
2017
Project Completion Individual evaluation reports 29th December,
2017
tmp51sgqbl1.doc 19 of 24

6. Part Four: Project Risk Analysis and Plan
6.1.Assumptions
The plans and estimates for this project are based on the following assumptions:
1. All Globex employees mainly associated with different tasks to maintain
different records of volunteers who taken part in the RALS are capable enough
to utilize all IT functionalities.
2. All volunteers associated with the RALS project get willing to share different
personal and associated project details.
3. The benefits achieved after the installation of system outgrows the financial
investments that made by Globex.
4. All the members of the project management team occurs significant experience
to utilize the selected tools to develop this project.
6.2.Risk Assessment
All the associated risk of the project are mainly discussed below along with the raking of
risks:
6.2.16.2.1 Risk RatingRisk Rating
(Note that the risks need to update as the project proceeds.)
Id Possible Unwelcome Event Likelihood
(L)
1, 2, 3
Severity
(S)
1,2,3
Ranking
L * S
1. Start-up Phase: Improper budget
estimation
2 3 6
2. Analysis Phase: Exact requirements of
this project are mainly not identified in
proper manner.
1 3 3
3. Design Phase: In-complete test plan 1 2 2
4. Prototype Phase: Prototype may not
get approved by clients
2 3 6
5. Iteration Phase: different irregularities
that may not get revealed by the
testing phase
3 3 9
1 is a low risk, 9 high risk.
tmp51sgqbl1.doc 20 of 24

6.2.26.2.2 Risk MitigationRisk Mitigation
I
d
Event Risk mitigation or contingency
1 Start-up Phase All budget requirements need to get
updated based on the project progression
2 Analysis Phase Numbers of meetings occurred with the
project representatives
3 Design Phase All test plans are revised before doing the
finalization
4 Prototype Phase All types of changes are mainly included
in prototype according to the instruction
that mainly provided by customers
5 Iteration Phase All final test activities are needed to be
conducted to do the final review of the
project
7. Part Five: Quality Management Plan
7.1.Philosophy of the team
The prime objective of this project management team is to offer better quality system
solutions to clients so that all specific requirements of project are met.
7.2.Ensuring quality
7.2.17.2.1 A set of verification activitiesA set of verification activities
i. all project team members are needed to be encouraged to have the better review of the
system by identifying all types of errors, issues and also the violation of different rules and
principles.
ii. Different examinations are mainly be conducted by identifying various domains that can
be improved in further.
iii. Reviewing of different testing techniques that can be applied to inspect the software
without having pro[per execution.
7.2.27.2.2 A set of validation activitiesA set of validation activities
i. acceptance testing are needed to be conducted to validate the facts that mainly designed
to validate the reason about the system based on different specific requirements set by the
clients. Different forms of acceptance testing are occurred in this project including the
alpha testing, beta testing etc.
ii. Different end users of this system are requested to provide .the review report after doing
the proper use of system.
tmp51sgqbl1.doc 21 of 24

8. Part Six: Project Closure and Evaluation
8.1.Annotated Bibliography
Article 1: “Project Management: The Managerial Process with MS Project”
The article has been written by Larson and Gray (2013) and kit has covered the impact of
the management process for the development of project operations. The analysis of the
project integration would form the smart analysis of the project analysis and its system
development for the operational processing. The managerial process of the project
management is employed for forming the use of MS Project software for implying the
accurate and effective processing of the organization. The improvisation of the project
planning with the help of project integration and development would be helpful for
developing the smarter operations for the project analysis. The evaluation of the project
plan in terms of the effective management strategies would comprise of developing the
formation of the system integration.
Article 2: Project management: a systems approach to planning, scheduling, and
controlling
The article was made by the Kerzner (2013) and it would form the involvement of the
effective processing. The project management would be helpful for forming the
development of the project scheduling and controlling. The role of the project for the
scheduling and planning would help in development of the system integration for the
management of the operations. The planning of the project is developed for critical
evaluation of the improvised development method. The planning of the project is formed
for the deployment of the improvised development method.
Article 3: A Guide to the Project Management Body of Knowledge: PMBOK (®) Guide
The project management is developed for the deployment of the improved processing and
The managerial process of the project management is employed for forming the use of the
accurate and effective processing of the organization. The improvisation of the project
planning with the help of project integration and development would be helpful for
developing the smarter operations for the project analysis. The evaluation of the project
plan in terms of the effective management strategies would comprise of developing the
formation of the system integration.
8.2.Closure Checklist
The project closure checklist includes,
Project charter and project management plan Checked
Different requirement specifications (use cases or similar)
Test cases
restructured Project Plan

Fully implemented architecture as well as detailed design
Detailed test plan

Various components of solution 
Extra functionalities
Test Cases

Test results 
tmp51sgqbl1.doc 22 of 24

Test results 
Solutions including all documentations and rough work 
Individual evaluation reports 
8.3. Evaluation Plan
The evaluation plan consists of the following the following points,
 Performance
 Meeting Requirements
 Completion Within Time
 Achieving higher level deliverables with quality
tmp51sgqbl1.doc 23 of 24

9. References
Buch, V., PMP, D., & Sharma, A. K. (2014). Identification of Project Risks & Risk
Breakdown Structure In Manufacture of Heavy Forgings. Journal of Engineering
Research and Applications, 4(10), 26-30.
Chance, D. M., & Brooks, R. (2015). Introduction to derivatives and risk management.
Cengage Learning.
Dwivedi, Y. K., Wastell, D., Laumer, S., Henriksen, H. Z., Myers, M. D., Bunker, D., ... &
Srivastava, S. C. (2015). Research on information systems failures and successes:
Status update and future directions. Information Systems Frontiers, 17(1), 143-157.
Hopkin, P. (2017). Fundamentals of risk management: understanding, evaluating and
implementing effective risk management. Kogan Page Publishers.
Lin, C. I., Kuo, F. Y., & Myers, M. D. (2015). Extending ICT4D studies: The value of
critical research. Management Information Systems Quarterly, 39(3), 697-712.
Połoński, M. (2015). Application of the work breakdown structure in determining cost
buffers in construction schedules. Archives of Civil Engineering, 61(1), 147-161.
Pritchard, C. L., & PMP, P. R. (2014). Risk management: concepts and guidance. CRC
Press.
Sandeep, M. S., & Ravishankar, M. N. (2014). The continuity of underperforming ICT
projects in the public sector. Information & Management,
Sharon, A., & Dori, D. (2015). A Project–product model–based approach to planning work
breakdown structures of complex system projects. IEEE Systems Journal, 9(2),
366-376.
tmp51sgqbl1.doc 24 of 24