Project Charter: i-Crop Application Development for Globex Corp - Plan

This document presents a comprehensive project charter for the development of the i-Crop application for Globex Corporation. It outlines the measurable organizational value, project scope including in and out of scope items, roles and responsibilities of team members, technology requirements, and facilities needed. The work breakdown structure (WBS), Gantt chart, project schedule, milestones, resource usage, and project budget are detailed. The charter also addresses assumptions, risks, quality statements, verification and validation activities, and project evaluation including an annotated bibliography and closure checklist. The project aims to develop an online cash marketplace platform to provide value-added services to Globex clients, focusing on improving the efficiency and effectiveness of their operations.

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