Project Charter Document for Development of i-Crop Application

This project charter document outlines the development of i-Crop application, including measurable organizational value, project scope, work breakdown structure, assumptions and risks, quality, and project evaluation.

Running head: PROJECT CHARTER DOCUMENT
Project Charter Document
Development of i-Crop Application
Name of the Student:
Student ID:

1PROJECT CHARTER DOCUMENT
Table of Contents
1. Part One - Measurable Organisational Value...........................................................................2
1.1. Identification of the Area of Impact..................................................................................2
1.2. Identification of the Desired Value...................................................................................2
2. Part Two – Project Scope.........................................................................................................3
2.1. In Scope.............................................................................................................................3
2.2. Out of Scope......................................................................................................................3
2.3. People and their Roles.......................................................................................................3
2.4. Technology (Hardware, Software and Network)..............................................................4
2.5. Facilities............................................................................................................................4
3. Part Three – Work Breakdown Structure.................................................................................4
3.1. High Level Work Break Down Structure.........................................................................4
3.2. Gantt Chart and Project Schedule.....................................................................................5
3.3. Milestones.........................................................................................................................7
3.4. Resource Usage.................................................................................................................7
3.5. Project Budget...................................................................................................................8
4. Part Four – Assumptions and Risks.........................................................................................9
4.1. Assumptions......................................................................................................................9

2PROJECT CHARTER DOCUMENT
4.2. Risks..................................................................................................................................9
5. Part Five – Quality.................................................................................................................10
5.1. Quality Statements..........................................................................................................10
5.2. Verification Activities.....................................................................................................10
5.3. Validation Activities.......................................................................................................10
6. Part Six – Project Evaluation..................................................................................................10
6.1. Annotated Bibliography..................................................................................................10
6.2. Closure Checklist............................................................................................................12
Bibliography..................................................................................................................................14

3PROJECT CHARTER DOCUMENT
1. Part One - Measurable Organisational Value
1.1. Identification of the Area of Impact
Factor Description Ranking
Customer The focus of the customer is high on the project as Globex wants the
application for its customers only
1
Financial Economical impact on operations would be effective for the
development of the successful execution of the activities.
2
Operational Operations of the organization is a must as the application is supposed
to make it more effective
3
Strategy Strategies of implementing the development factors would be eased
with the consideration of the factors and development.
4
Social Social influence of operations would be implied with the involvement of
the successive development factor.
5
1.2. Identification of the Desired Value
Value Metrics Time Frame
Better Number of operations 3 months
Faster Delivery time 2 months

4PROJECT CHARTER DOCUMENT
Cheaper Cost Incurred 5 months
Do More Effectiveness 8 months
2. Part Two – Project Scope
2.1. In Scope
 Development of the Project Plan
 Design of Cash Application
 Development of Cash Application
 Testing of Cash Application
 Final Documentation
2.2. Out of Scope
 Training of the users
 Change Management
 Scope Creep Analysis
2.3. People and their Roles
Resource Name Roles
Financial manager Management of the Cash Application
Project manager Management of the project activities
Project planner Project Scheduling

5PROJECT CHARTER DOCUMENT
Developer Development of Application
System engineer Integration of system functions
Designer Design development
Tester Testing the system for functions
System analyst Analyzing the system requirements
Database administrator Management of the database
Human resource manager Management of the human resources
Risk analyst Analyzing the project risks
Programmer Programming the application
System administrator Managing system functions
Software engineer Integration of system functions
2.4. Technology (Hardware, Software and Network)
2.4.1. Hardware and Network Requirements
Computer System, Router, Switch, and NIC card
2.4.2. Software Requirements
Application UI, Programming, Designing, and Testing Software
2.5. Facilities
3. Part Three – Work Breakdown Structure
3.1. High Level Work Break Down Structure

6PROJECT CHARTER DOCUMENT
Development of i-Crop
Application
Initial Phase
Analyzing for
requirements
Planning for project
Analyzing for
feasibility
Kick off
Plan Phase
Scheduling for
activities
Estimating for
project resources
Allocating for project
resources
Planning for
communication
Managing for
resources
Plan Approval
Design Phase
Developing the
prototype
Determining the
features
Identifying the design
requirements
Design Approval
Development Phase
Adding the offers
Developing Bidding
Option
Incorporating the
buyer option
Adding mobile
features
Incorporating the
service option
Sales Review
Developing
communication
facility
Managing finance
option
Online Functionality
System Developed
Testing phase
White Box
Black Box
User Interface
Prototyping
Simulation
Test Documentation
Control Phase
Management
Request
Issues Management
Risk Management
Project Meetings
Earned Value
Analysis
System Live
Closure Phase
Sign offf
Reviewing the
Project
Project Closed
3.2. Gantt Chart and Project Schedule
The Gantt chart for the project is shown below,

7PROJECT CHARTER DOCUMENT
ID Task
Mode
WBS Task Name Duration Start Finish Predecessors
0 0 Development of i-Crop Application 59 days Wed 8/1/18 Mon 10/22/18
1 1 Initial Phase 4 days Wed 8/1/18 Mon 8/6/18
2 1.1 Analyzing for requirements 1 day Wed 8/1/18 Wed 8/1/18
3 1.2 Planning for project 2 days Thu 8/2/18 Fri 8/3/18 2
4 1.3 Analyzing for feasibility 1 day Mon 8/6/18 Mon 8/6/18 3
5 M1 Kick off 0 days Mon 8/6/18 Mon 8/6/18 4
6 2 Plan Phase 10 days Tue 8/7/18 Mon 8/20/18
7 2.1 Scheduling for activities 2 days Tue 8/7/18 Wed 8/8/18 4
8 2.2 Estimating for project resources 2 days Thu 8/9/18 Fri 8/10/18 7
9 2.3 Allocating for project resources 2 days Mon 8/13/18 Tue 8/14/18 8
10 2.4 Planning for communication 2 days Wed 8/15/18 Thu 8/16/18 9
11 2.5 Managing for resources 2 days Fri 8/17/18 Mon 8/20/18 10
12 M2 Plan Approval 0 days Mon 8/20/18 Mon 8/20/18 11
13 3 Design Phase 6 days Tue 8/21/18 Tue 8/28/18
14 3.1 Developing the prototype 3 days Tue 8/21/18 Thu 8/23/18 11
15 3.2 Determining the features 2 days Fri 8/24/18 Mon 8/27/18 14
16 3.3 Identifying the design requirements 1 day Tue 8/28/18 Tue 8/28/18 15
17 M3 Design Approval 0 days Tue 8/28/18 Tue 8/28/18 16
18 4 Development Phase 24 days Wed 8/29/18 Mon 10/1/18
19 4.1 Adding the offers 3 days Wed 8/29/18 Fri 8/31/18 16
20 4.2 Developing Bidding Option 3 days Mon 9/3/18 Wed 9/5/18 19
21 4.3 Incorporating the buyer option 3 days Thu 9/6/18 Mon 9/10/18 20
22 4.4 Adding mobile features 3 days Tue 9/11/18 Thu 9/13/18 21
23 4.5 Incorporating the service option 3 days Fri 9/14/18 Tue 9/18/18 22
24 4.6 Sales Review 2 days Wed 9/19/18 Thu 9/20/18 23
25 4.7 Developing communication facility 2 days Fri 9/21/18 Mon 9/24/18 24
26 4.8 Managing finance option 3 days Tue 9/25/18 Thu 9/27/18 25
27 4.9 Online Functionality 5 days Tue 9/25/18 Mon 10/1/18 25
28 M4 System Developed 0 days Thu 9/27/18 Thu 9/27/18 26
29 5 Testing phase 10 days Fri 9/28/18 Thu 10/11/18
30 5.1 White Box 2 days Fri 9/28/18 Mon 10/1/18 26
31 5.2 Black Box 2 days Tue 10/2/18 Wed 10/3/18 30
32 5.3 User Interface 2 days Thu 10/4/18 Fri 10/5/18 31
33 5.4 Prototyping 2 days Mon 10/8/18 Tue 10/9/18 32
34 5.5 Simulation 2 days Wed 10/10/18 Thu 10/11/18 33
35 M5 Test Documentation 0 days Thu 10/11/18 Thu 10/11/18 34
36 6 Control Phase 5 days Fri 10/12/18 Thu 10/18/18
37 6.1 Management Request 1 day Fri 10/12/18 Fri 10/12/18 34
38 6.2 Issues Management 1 day Mon 10/15/18 Mon 10/15/18 37
39 6.3 Risk Management 1 day Tue 10/16/18 Tue 10/16/18 38
40 6.4 Project Meetings 1 day Wed 10/17/18 Wed 10/17/18 39
41 6.5 Earned Value Analysis 1 day Thu 10/18/18 Thu 10/18/18 40
42 M6 System Live 0 days Thu 10/18/18 Thu 10/18/18 41
43 7 Closure Phase 2 days Fri 10/19/18 Mon 10/22/18
44 7.1 Sign offf 1 day Fri 10/19/18 Fri 10/19/18 42
45 7.2 Reviewing the Project 1 day Mon 10/22/18 Mon 10/22/18 44
46 M7 Project Closed 0 days Mon 10/22/18 Mon 10/22/18 45
Finanacial manager,Project manager
Finanacial manager
Project planner,Human resource manager
8/6
Project manager
Project planner,Human resource manager
Project manager,Project planner,Human resource manager
Finanacial manager,Human resource manager
Project manager,Human resource manager
8/20
System analyst,Designer,System engineer
Software engineer,System administrator,System engineer
System analyst,Human resource manager,System administrator
8/28
Developer,Programmer,Software engineer
Database administrator,System engineer
Hardware and software requirements[1],Programmer,Software en
Software engineer,System administrator
Project manager,System engineer,Software engineer,Tester
Project planner,System engineer,System administrator
Database administrator,Developer,System administrator
9/27
Additional cost[1],Risk analyst,Tester
Tester
Risk analyst,Tester
Risk analyst,Tester
Risk analyst,Tester
10/11
Finanacial manager
Risk analyst
Risk analyst,Tester
Project manager,Finanacial manager
Human resource manager,Finanacial manager
10/18
Finanacial manager
Designer,Finanacial manager
10/22
S T M F T S W S T M F T S W S T M F
May 21, '18 Jul 2, '18 Aug 13, '18 Sep 24, '18 Nov 5, '18 Dec 17, '18 Jan 28, '19 Mar 11, '19

8PROJECT CHARTER DOCUMENT
3.3. Milestones
WBS Task Name Duration Start Finish
M1 Kick off 0 days Mon 8/6/18 Mon 8/6/18
M2 Plan Approval 0 days Mon 8/20/18 Mon 8/20/18
M3 Design Approval 0 days Tue 8/28/18 Tue 8/28/18
M4 System Developed 0 days Thu 9/27/18 Thu 9/27/18
M5 Test Documentation 0 days Thu 10/11/18 Thu 10/11/18
M6 System Live 0 days Thu 10/18/18 Thu 10/18/18
M7 Project Closed 0 days Mon 10/22/18 Mon 10/22/18
3.4. Resource Usage

9PROJECT CHARTER DOCUMENT
ID Resource Name Work
1 Finanacial manager 80 hrs
2 Project manager 80 hrs
3 Project planner 56 hrs
4 Developer 64 hrs
5 System engineer 96 hrs
6 Designer 32 hrs
7 Tester 104 hrs
8 System analyst 32 hrs
9 Database administrator 64 hrs
10 Human resource manager 88 hrs
11 Risk analyst 80 hrs
12 Programmer 48 hrs
13 System administrator 128 hrs
14 Software engineer 104 hrs
15 Hardware and software
requirements
1
16 Additional cost 1
Details
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
M M M M M M M M
Jul 30, '18 Aug 27, '18 Sep 24, '18 Oct 22, '18
24h 16h 32h 8h
24h 32h 16h 8h
24h 16h 8h 8h
24h 40h
32h 32h 24h 8h
24h 8h
16h 48h 40h
24h 8h
24h 40h
24h 48h 8h 8h
32h 48h
40h 8h
8h 32h 40h 48h
8h 48h 48h
0.67 0.33
1
3.5. Project Budget
Resource Name Work Standard Rate Cost
Financial manager 80 hrs $ 70.00/hr $ 5,600.00
Project manager 80 hrs $ 80.00/hr $ 6,400.00
Project planner 56 hrs $ 40.00/hr $ 2,240.00
Developer 64 hrs $ 60.00/hr $ 3,840.00
System engineer 96 hrs $ 75.00/hr $ 7,200.00
Designer 32 hrs $ 50.00/hr $ 1,600.00
Tester 104 hrs $ 50.00/hr $ 5,200.00

10PROJECT CHARTER DOCUMENT
System analyst 32 hrs $ 55.00/hr $ 1,760.00
Database administrator 64 hrs $ 60.00/hr $ 3,840.00
Human resource manager 88 hrs $ 70.00/hr $ 6,160.00
Risk analyst 80 hrs $ 40.00/hr $ 3,200.00
Programmer 48 hrs $ 65.00/hr $ 3,120.00
System administrator 128 hrs $ 70.00/hr $ 8,960.00
Software engineer 104 hrs $ 75.00/hr $ 7,800.00
Hardware and software requirements 1 $ 5,000.00 $ 5,000.00
Additional cost 1 $ 3,000.00 $ 3,000.00
Total Budget $74,920.00
4. Part Four – Assumptions and Risks
4.1. Assumptions
 Important Documentation would be done by the users
 All bugs and errors would be fixed in the estimated time
 Cash Application would be compatible with the user’s requirements
4.2. Risks
Risk Probability
(1-5)
Impact
(1-5)
Rating
P*I
Over budget 4 3 8
Delay of Schedule 5 2 10

11PROJECT CHARTER DOCUMENT
Performance Issues 3 5 15
Programming Errors 2 4 8
Missing Function 4 5 20
5. Part Five – Quality
5.1. Quality Statements
The new cash application for Globex would ensure that the requirements of the client for
easing their customer’s operations would be done by following the engineering activities.
5.2. Verification Activities
Testing methods of White Box, Black Box, User Interface. Prototyping, and Simulation
would be used as verification activities.
5.3. Validation Activities
Quality Control, Evaluation Checklist, and Feasible Project Plan analysis would be used
as the validation activities.
6. Part Six – Project Evaluation
6.1. Annotated Bibliography
Article: A computerized method for delay risk assessment based on fuzzy set theory using MS
Project™
Journal: KSCE Journal of Civil Engineering

12PROJECT CHARTER DOCUMENT
Authors: Budayan, C., Dikmen, I., Birgonul, M. T., and Ghaziani, A.
Year of Publication: 2018
Synopsis: According to Budayan, Dikmen, Birgonul and Ghaziani (2018), the Ms-Project
software can be helpful for defining the influence of the risk management. The analysis of the
fuzzy set theory would align with the development of the successive management of the
activities and implying the innovative and improved functional management using successful
development of project schedule using Ms-Project. The risk assessment is helpful for enduring
the analysis of the factors for developing the successful integration and alignment of the cohesive
project integration. The analysis would also be helpful for taking care of the risk assessment and
development of the factors for the integration management. The integration would be aligned for
the management of the successful formation and introducing the utilization and formation.
Article: How does risk management influence production decisions? Evidence from a field
experiment
Journal: The Review of Financial Studies (Vol. 30; Issue no. 6)
Authors: Cole, S., Giné, X., and Vickery, J.
Year of Publication: 2017
Synopsis: According to Cole, Gine and Vickery (2017), risk management holds an integral role
in defining the management of the successful management and integration of the factors. The
production decisions for the project can be effectively dealt with the innovative and improved
analysis model. The risk management operations would be helpful for taking care of the factors
for the implementation and utilization factors. The innovation would be more effective for the

13PROJECT CHARTER DOCUMENT
formation of the impressive management and development. The analysis of the factors for the
development and alignment of the factors has been largely helpful for integrating the listing of
the factors taking care of the improved analysis and development. The easing of the management
model would be implied with the consideration and utilization of the successive development
model.
Article: Between cost and benefit: investigating effects of cost management control systems on
cost efficiency and organisational performance
Journal: Journal of Management Control (Vol. 29; Issue no. 1)
Authors: Diefenbach, U., Wald, A., and Gleich, R.
Year of Publication: 2018
Synopsis: According to Diefenbach, Wald and Gleich (2018), the consideration of the factorial
representation of the development model would align with the consideration to the formation and
listing the innovative management of the factors. The successful management of the factors
would help the organization in taking care of the innovation and development. The cost analysis
and the management of the resources act as a major factor for integrating the utilization and
development. The completion of the successful project completion would be aligned with the
management of the successful cost factors. The consideration for the efficiency analysis of the
costing factor for the project is aligned with the utilization of the improved functional
development.
6.2. Closure Checklist
Is required information and resources for the project comprehensive? 

14PROJECT CHARTER DOCUMENT
Is the project plan feasible? 
Has the design being approved by the client? 
Are all the factors for the risk assessment being considered? 
Is it possible for the actualization of the project? 
Has the project be approved by the client? 

15PROJECT CHARTER DOCUMENT
Bibliography
Almeida, H., Hankins, K. W., & Williams, R. (2017). Risk management with supply
contracts. The Review of Financial Studies, 30(12), 4179-4215.
Andersen, K., Thorsteinsson, S. E., Thorbergsson, H., & Gudmundsson, K. S. (2017, July).
Developing the academic-industrial partnership through student research and projects:
Case studies from Iceland. In Professional Communication Conference (ProComm),
2017 IEEE International (pp. 1-5). IEEE.
Budayan, C., Dikmen, I., Birgonul, M. T., & Ghaziani, A. (2018). A computerized method for
delay risk assessment based on fuzzy set theory using MS Project™. KSCE Journal of
Civil Engineering, 1-12.
Burtonshaw-Gunn, S. A. (2017). Risk and financial management in construction. Routledge.
Christian, D. (2018). Building Cost Management: Case Study Using Costing Methods. IJAME.
Cole, S., Giné, X., & Vickery, J. (2017). How does risk management influence production
decisions? Evidence from a field experiment. The Review of Financial Studies, 30(6),
1935-1970.
Cooper, R. (2017). Supply chain development for the lean enterprise: interorganizational cost
management. Routledge.
da Silva, R. F., Filgueira, R., Pietri, I., Jiang, M., Sakellariou, R., & Deelman, E. (2017). A
characterization of workflow management systems for extreme-scale applications. Future
Generation Computer Systems, 75, 228-238.

16PROJECT CHARTER DOCUMENT
Diefenbach, U., Wald, A., & Gleich, R. (2018). Between cost and benefit: investigating effects
of cost management control systems on cost efficiency and organisational
performance. Journal of Management Control, 29(1), 63-89.
Fuller, M. A., Valacich, J. S., George, J. F., & Schneider, C. (2017). Information Systems Project
Management: A Process and Team Approach, Edition 1.1. Prospect Press.
Harris, E. (2017). Strategic project risk appraisal and management. Routledge.
Harrison, F., & Lock, D. (2017). Advanced project management: a structured approach.
Routledge.
Heldman, K. (2018). PMP: project management professional exam study guide. John Wiley &
Sons.
Hopkin, P. (2018). Fundamentals of risk management: understanding, evaluating and
implementing effective risk management. Kogan Page Publishers.
Husin, S., & Malahayati, N. (2018, May). Identifying inaccuracy of MS Project using system
analysis. In IOP Conference Series: Materials Science and Engineering (Vol. 352, No. 1,
p. 012036). IOP Publishing.
Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring
and monitoring project performance. John Wiley & Sons.
Kerzner, H. (2018). Project management best practices: Achieving global excellence. John
Wiley & Sons.

17PROJECT CHARTER DOCUMENT
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Markou, C., Koulinas, G. K., & Vavatsikos, A. P. (2017). Project resources scheduling and
leveling using Multi-Attribute Decision Models: Models implementation and case
study. Expert Systems with Applications, 77, 160-169.
Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business and
technology. Routledge.
Papke-Shields, K. E., & Boyer-Wright, K. M. (2017). Strategic planning characteristics applied
to project management. International Journal of Project Management, 35(2), 169-179.
Shakeri, M., Shayestegan, M., Abunima, H., Reza, S. S., Akhtaruzzaman, M., Alamoud, A. R.
M., ... & Amin, N. (2017). An intelligent system architecture in home energy
management systems (HEMS) for efficient demand response in smart grid. Energy and
Buildings, 138, 154-164.
Stair, R., & Reynolds, G. (2017). Fundamentals of information systems. Cengage Learning.
Wager, K. A., Lee, F. W., & Glaser, J. P. (2017). Health care information systems: a practical
approach for health care management. John Wiley & Sons.