i-Crop Project: Project Management Charter and Implementation Plan
VerifiedAdded on  2023/06/04
|21
|3916
|111
Project
AI Summary
This project management assignment details the development of the i-Crop application, aimed at facilitating easier transactions for crop growers and buyers. The project charter outlines the Measurable Organizational Value (MOV), prioritizing customer and operational impact. Key aspects include scope management, resource allocation, milestone tracking, and activity scheduling, with a detailed Gantt chart and Work Breakdown Structure (WBS). The document also covers project budgeting, risk analysis, and a quality management plan, culminating in a closure checklist and project evaluation. This comprehensive plan provides a structured approach to the successful implementation of the i-Crop application.

Running head: PROJECT MANAGEMENT
Project Management
Name of the Student
Name of the University
Author Note
Project Management
Name of the Student
Name of the University
Author Note
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

1
PROJECT MANAGEMENT
Table of Contents
1. Part One...........................................................................................................................3
2. Part Two...........................................................................................................................4
2.1. Scope and Scope management..................................................................................4
2.2. List of Resources......................................................................................................4
3. Part Three.........................................................................................................................5
3.1. Milestone..................................................................................................................5
3.2. Activities/tasks..........................................................................................................5
3.3. Resource Assignments..............................................................................................6
3.4. Estimates for Each Activity......................................................................................8
3.5. Project Budget........................................................................................................11
4. Part Four........................................................................................................................13
4.1. Assumptions...........................................................................................................13
4.2. Project Risks...........................................................................................................13
4.3. Risk Analysis..........................................................................................................14
5. Part Five: Quality Management Plan.............................................................................14
6. Part Six...........................................................................................................................15
6.1. Closure Checklist....................................................................................................15
6.2. Project Evaluation...................................................................................................15
References..........................................................................................................................16
PROJECT MANAGEMENT
Table of Contents
1. Part One...........................................................................................................................3
2. Part Two...........................................................................................................................4
2.1. Scope and Scope management..................................................................................4
2.2. List of Resources......................................................................................................4
3. Part Three.........................................................................................................................5
3.1. Milestone..................................................................................................................5
3.2. Activities/tasks..........................................................................................................5
3.3. Resource Assignments..............................................................................................6
3.4. Estimates for Each Activity......................................................................................8
3.5. Project Budget........................................................................................................11
4. Part Four........................................................................................................................13
4.1. Assumptions...........................................................................................................13
4.2. Project Risks...........................................................................................................13
4.3. Risk Analysis..........................................................................................................14
5. Part Five: Quality Management Plan.............................................................................14
6. Part Six...........................................................................................................................15
6.1. Closure Checklist....................................................................................................15
6.2. Project Evaluation...................................................................................................15
References..........................................................................................................................16

2
PROJECT MANAGEMENT
Appendix............................................................................................................................18
Annotated Bibliography.................................................................................................18
PROJECT MANAGEMENT
Appendix............................................................................................................................18
Annotated Bibliography.................................................................................................18
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

3
PROJECT MANAGEMENT
1. Part One
The measurable organization value provides a clear definition of the success and the
objectives of the project (Martinelli & Milosevic, 2016). The goal of this project is to develop an
application and a website that will help the crop growers and the buyers in easier dealing with
the warehoused grains. The desired areas that the project will have an impact on include
customer, operational, financial and strategy. The ranking of the area of impact according to their
importance are as follows-
Area of Impact Ranking
Customer 1
Operational 2
Financial 3
Strategy 4
The values that i-crop application development project will bring to the company are as follows-
Do More: The Company wants to continue its growth by improving the ease of access and
management of the warehoused grains by development of an online website and a smartphone
application.
Faster: With the use of online website the buyers and the growers will be able to easily deal
with the warehoused grains thus increasing the efficiency of the process.
The metrics that will help in easier measurement of the measurable organizational value are as
follows-
PROJECT MANAGEMENT
1. Part One
The measurable organization value provides a clear definition of the success and the
objectives of the project (Martinelli & Milosevic, 2016). The goal of this project is to develop an
application and a website that will help the crop growers and the buyers in easier dealing with
the warehoused grains. The desired areas that the project will have an impact on include
customer, operational, financial and strategy. The ranking of the area of impact according to their
importance are as follows-
Area of Impact Ranking
Customer 1
Operational 2
Financial 3
Strategy 4
The values that i-crop application development project will bring to the company are as follows-
Do More: The Company wants to continue its growth by improving the ease of access and
management of the warehoused grains by development of an online website and a smartphone
application.
Faster: With the use of online website the buyers and the growers will be able to easily deal
with the warehoused grains thus increasing the efficiency of the process.
The metrics that will help in easier measurement of the measurable organizational value are as
follows-
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

4
PROJECT MANAGEMENT
1. It is to be checked whether the project has been able to fulfill the required deliverables.
2. It is to be ensured that no scope creep has occurred in the project.
The timeframe for achieving the MOV will be 5 months from the start date of the project.
2. Part Two
2.1. Scope and Scope management
It is essential to identify the scope of the project. For efficient scope management it is
essential to identify the accurate scope of the project. The main aim or scope of this project is to
develop and implement the website and the application in an inexpensive manner and therefore
the scope management in this project is essential (Desmond, 2014). As a part of scope
management, it is necessary to ensure that the project does not suffer scope creep. Furthermore,
resource management is quite vital for implementation of this project (Rolstadås, Tommelein,
Morten Schiefloe & Ballard, 2014). The list of resources associated with this project is
represented in the following section.
2.2. List of Resources
The resources associated with this project are as follows-
Resource Name Type Max. Units Std. Rate Cost/Use
Project Manager Work 100% $95.00/hr $0.00
Resource Manager Work 100% $40.00/hr $0.00
Functional Manager Work 200% $35.00/hr $0.00
Supervisor From Globex Work 200% $40.00/hr $0.00
Supervisor from Virtucon Work 100% $65.00/hr $0.00
Virtucon Coding Team Work 1,000% $30.00/hr $0.00
Virtucon Testing Team Work 200% $30.00/hr $0.00
Database Administrator Work 100% $30.00/hr $0.00
PROJECT MANAGEMENT
1. It is to be checked whether the project has been able to fulfill the required deliverables.
2. It is to be ensured that no scope creep has occurred in the project.
The timeframe for achieving the MOV will be 5 months from the start date of the project.
2. Part Two
2.1. Scope and Scope management
It is essential to identify the scope of the project. For efficient scope management it is
essential to identify the accurate scope of the project. The main aim or scope of this project is to
develop and implement the website and the application in an inexpensive manner and therefore
the scope management in this project is essential (Desmond, 2014). As a part of scope
management, it is necessary to ensure that the project does not suffer scope creep. Furthermore,
resource management is quite vital for implementation of this project (Rolstadås, Tommelein,
Morten Schiefloe & Ballard, 2014). The list of resources associated with this project is
represented in the following section.
2.2. List of Resources
The resources associated with this project are as follows-
Resource Name Type Max. Units Std. Rate Cost/Use
Project Manager Work 100% $95.00/hr $0.00
Resource Manager Work 100% $40.00/hr $0.00
Functional Manager Work 200% $35.00/hr $0.00
Supervisor From Globex Work 200% $40.00/hr $0.00
Supervisor from Virtucon Work 100% $65.00/hr $0.00
Virtucon Coding Team Work 1,000% $30.00/hr $0.00
Virtucon Testing Team Work 200% $30.00/hr $0.00
Database Administrator Work 100% $30.00/hr $0.00

5
PROJECT MANAGEMENT
Software licensing Fee Material $0.00 $75,000.00
Website and Application
Launch Material $0.00 $50,000.00
Virtucon Training Team Work 400% $20.00/hr $0.00
Archive Material $0.00 $5,000.00
Document handler Work 100% $15.00/hr $0.00
3. Part Three
3.1. Milestone
The major milestones associated with this project are as follows-
M1: Requirements and the Specification of the project are gathered
M2: Preparation and Approval of Project Plan
M3: Successful application and website development
M4: Completion of Testing and Bug Fixing
M5: Successful Project Release
M6: Project Closes
3.2. Activities/tasks
The list of activities or tasks the project will fulfill are as follows-
WBS Task Name
0 i-Crop Project Implementation
1 Initiation Phase
1.1 Setting up a meeting with the Clients
1.2 Identification of the Requirement specifications
1.3 Specification documentation
PROJECT MANAGEMENT
Software licensing Fee Material $0.00 $75,000.00
Website and Application
Launch Material $0.00 $50,000.00
Virtucon Training Team Work 400% $20.00/hr $0.00
Archive Material $0.00 $5,000.00
Document handler Work 100% $15.00/hr $0.00
3. Part Three
3.1. Milestone
The major milestones associated with this project are as follows-
M1: Requirements and the Specification of the project are gathered
M2: Preparation and Approval of Project Plan
M3: Successful application and website development
M4: Completion of Testing and Bug Fixing
M5: Successful Project Release
M6: Project Closes
3.2. Activities/tasks
The list of activities or tasks the project will fulfill are as follows-
WBS Task Name
0 i-Crop Project Implementation
1 Initiation Phase
1.1 Setting up a meeting with the Clients
1.2 Identification of the Requirement specifications
1.3 Specification documentation
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

6
PROJECT MANAGEMENT
1.4 Documenting the findings
1.5 M1: Requirements and the Specification of the project are
gathered
2 Project Planning
2.1 Setting the structure of Project Plan
2.2 Project Scheduling
2.3 Project Budget Estimation
2.4 Resource Estimation
2.5 Resource Allocation
2.6 M2: Preparation and Approval of Project Plan
3 Project Implementation
3.1 Interface Designing
3.2 Software Coding
3.3 Database Designing
3.4 Linking with the database
3.5 Documentation
3.6 M3: Successful application and website development
4 Testing
4.1 Unit Testing
4.2 System testing
4.3 User acceptance testing
4.4 Bug Fixing (if any)
4.5 M4: Completion of Testing and Bug Fixing
5 Website and Application Go Live and Training
5.1 Website and Application Demonstration
5.2 Training and Maintenance
5.3 Post Launch Support
5.4 M5: Successful Project Release
6 Project Closure
6.1 Document archival
6.2 Payment Completion
6.3 Resource Release
6.4 Project Evaluation
6.5 Client Sign off
6.6 M6: Project Closes
3.3. Resource Assignments
PROJECT MANAGEMENT
1.4 Documenting the findings
1.5 M1: Requirements and the Specification of the project are
gathered
2 Project Planning
2.1 Setting the structure of Project Plan
2.2 Project Scheduling
2.3 Project Budget Estimation
2.4 Resource Estimation
2.5 Resource Allocation
2.6 M2: Preparation and Approval of Project Plan
3 Project Implementation
3.1 Interface Designing
3.2 Software Coding
3.3 Database Designing
3.4 Linking with the database
3.5 Documentation
3.6 M3: Successful application and website development
4 Testing
4.1 Unit Testing
4.2 System testing
4.3 User acceptance testing
4.4 Bug Fixing (if any)
4.5 M4: Completion of Testing and Bug Fixing
5 Website and Application Go Live and Training
5.1 Website and Application Demonstration
5.2 Training and Maintenance
5.3 Post Launch Support
5.4 M5: Successful Project Release
6 Project Closure
6.1 Document archival
6.2 Payment Completion
6.3 Resource Release
6.4 Project Evaluation
6.5 Client Sign off
6.6 M6: Project Closes
3.3. Resource Assignments
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

7
PROJECT MANAGEMENT
The Resources that has been assigned to each of the tasks or activities in the project is
represented in the following table-
WBS Task Name Resource Names
0 i-Crop Project Implementation
1 Initiation Phase
1.1 Setting up a meeting with the Clients Functional Manager
1.2 Identification of the Requirement
specifications Project Manager, Functional Manager
1.3 Specification documentation Archive[1],Document handler
1.4 Documenting the findings Document handler
1.5
M1: Requirements and the
Specification of the project are
gathered
2 Project Planning
2.1 Setting the structure of Project Plan Supervisor from Virtucon, Supervisor
From Globex
2.2 Project Scheduling Functional Manager, Supervisor From
Globex
2.3 Project Budget Estimation Supervisor From Globex
2.4 Resource Estimation Resource Manager
2.5 Resource Allocation Resource Manager
2.6 M2: Preparation and Approval of
Project Plan
3 Project Implementation
3.1 Interface Designing Virtucon Coding Team
3.2 Software Coding Virtucon Coding Team, Website and
Application Launch[1]
3.3 Database Designing Virtucon Coding Team, Software
licensing Fee[1],Database Administrator
3.4 Linking with the database Virtucon Coding Team, Database
Administrator
3.5 Documentation Archive[1],Document handler
3.6 M3: Successful application and
website development
4 Testing
4.1 Unit Testing Virtucon Testing Team
4.2 System testing Virtucon Testing Team
4.3 User acceptance testing Virtucon Testing Team
4.4 Bug Fixing (if any) Virtucon Testing Team
4.5 M4: Completion of Testing and
PROJECT MANAGEMENT
The Resources that has been assigned to each of the tasks or activities in the project is
represented in the following table-
WBS Task Name Resource Names
0 i-Crop Project Implementation
1 Initiation Phase
1.1 Setting up a meeting with the Clients Functional Manager
1.2 Identification of the Requirement
specifications Project Manager, Functional Manager
1.3 Specification documentation Archive[1],Document handler
1.4 Documenting the findings Document handler
1.5
M1: Requirements and the
Specification of the project are
gathered
2 Project Planning
2.1 Setting the structure of Project Plan Supervisor from Virtucon, Supervisor
From Globex
2.2 Project Scheduling Functional Manager, Supervisor From
Globex
2.3 Project Budget Estimation Supervisor From Globex
2.4 Resource Estimation Resource Manager
2.5 Resource Allocation Resource Manager
2.6 M2: Preparation and Approval of
Project Plan
3 Project Implementation
3.1 Interface Designing Virtucon Coding Team
3.2 Software Coding Virtucon Coding Team, Website and
Application Launch[1]
3.3 Database Designing Virtucon Coding Team, Software
licensing Fee[1],Database Administrator
3.4 Linking with the database Virtucon Coding Team, Database
Administrator
3.5 Documentation Archive[1],Document handler
3.6 M3: Successful application and
website development
4 Testing
4.1 Unit Testing Virtucon Testing Team
4.2 System testing Virtucon Testing Team
4.3 User acceptance testing Virtucon Testing Team
4.4 Bug Fixing (if any) Virtucon Testing Team
4.5 M4: Completion of Testing and

8
PROJECT MANAGEMENT
Bug Fixing
5 Website and Application Go Live
and Training
5.1 Website and Application
Demonstration
Virtucon Training Team ,Functional
Manager
5.2 Training and Maintenance Virtucon Training Team ,Functional
Manager
5.3 Post Launch Support Functional Manager,Virtucon Training
Team
5.4 M5: Successful Project Release
6 Project Closure
6.1 Document archival Archive[1],Document handler
6.2 Payment Completion Archive[1]
6.3 Resource Release Project Manager
6.4 Project Evaluation Functional Manager, Project Manager
6.5 Client Sign off Project Manager
6.6 M6: Project Closes
3.4. Estimates for Each Activity
The time estimates for each activity is represented as follows-
Task Name Duration Start Finish
i-Crop Project Implementation 164 days Tue 02-10-18 Fri 17-05-19
Initiation Phase 22 days Tue 02-10-18 Wed 31-10-18
Setting up a meeting with the
Clients 6 days Tue 02-10-18 Tue 09-10-18
Identification of the Requirement
specifications 11 days Wed 10-10-18 Wed 24-10-18
Specification documentation 3 days Thu 25-10-18 Mon 29-10-18
Documenting the findings 2 days Tue 30-10-18 Wed 31-10-18
M1: Requirements and the
Specification of the project are
gathered
0 days Wed 31-10-18 Wed 31-10-18
Project Planning 16 days Thu 01-11-18 Thu 22-11-18
Setting the structure of Project
Plan 8 days Thu 01-11-18 Mon 12-11-18
Project Scheduling 3 days Tue 13-11-18 Thu 15-11-18
Project Budget Estimation 8 days Tue 13-11-18 Thu 22-11-18
Resource Estimation 6 days Tue 13-11-18 Tue 20-11-18
PROJECT MANAGEMENT
Bug Fixing
5 Website and Application Go Live
and Training
5.1 Website and Application
Demonstration
Virtucon Training Team ,Functional
Manager
5.2 Training and Maintenance Virtucon Training Team ,Functional
Manager
5.3 Post Launch Support Functional Manager,Virtucon Training
Team
5.4 M5: Successful Project Release
6 Project Closure
6.1 Document archival Archive[1],Document handler
6.2 Payment Completion Archive[1]
6.3 Resource Release Project Manager
6.4 Project Evaluation Functional Manager, Project Manager
6.5 Client Sign off Project Manager
6.6 M6: Project Closes
3.4. Estimates for Each Activity
The time estimates for each activity is represented as follows-
Task Name Duration Start Finish
i-Crop Project Implementation 164 days Tue 02-10-18 Fri 17-05-19
Initiation Phase 22 days Tue 02-10-18 Wed 31-10-18
Setting up a meeting with the
Clients 6 days Tue 02-10-18 Tue 09-10-18
Identification of the Requirement
specifications 11 days Wed 10-10-18 Wed 24-10-18
Specification documentation 3 days Thu 25-10-18 Mon 29-10-18
Documenting the findings 2 days Tue 30-10-18 Wed 31-10-18
M1: Requirements and the
Specification of the project are
gathered
0 days Wed 31-10-18 Wed 31-10-18
Project Planning 16 days Thu 01-11-18 Thu 22-11-18
Setting the structure of Project
Plan 8 days Thu 01-11-18 Mon 12-11-18
Project Scheduling 3 days Tue 13-11-18 Thu 15-11-18
Project Budget Estimation 8 days Tue 13-11-18 Thu 22-11-18
Resource Estimation 6 days Tue 13-11-18 Tue 20-11-18
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

9
PROJECT MANAGEMENT
Resource Allocation 1 day Wed 21-11-18 Wed 21-11-18
M2: Preparation and Approval
of Project Plan 0 days Wed 21-11-18 Wed 21-11-18
Project Implementation 46 days Thu 22-11-18 Thu 24-01-19
Interface Designing 15 days Thu 22-11-18 Wed 12-12-18
Software Coding 20 days Thu 13-12-18 Wed 09-01-19
Database Designing 15 days Thu 13-12-18 Wed 02-01-19
Linking with the database 13 days Thu 03-01-19 Mon 21-01-19
Documentation 3 days Tue 22-01-19 Thu 24-01-19
M3: Successful application and
website development 0 days Thu 24-01-19 Thu 24-01-19
Testing 41 days Fri 25-01-19 Fri 22-03-19
Unit Testing 8 days Fri 25-01-19 Tue 05-02-19
System testing 15 days Wed 06-02-19 Tue 26-02-19
User acceptance testing 10 days Wed 27-02-19 Tue 12-03-19
Bug Fixing (if any) 8 days Wed 13-03-19 Fri 22-03-19
M4: Completion of Testing and
Bug Fixing 0 days Fri 22-03-19 Fri 22-03-19
Website and Application Go Live
and Training 32 days Mon 25-03-19 Tue 07-05-19
Website and Application
Demonstration 7 days Mon 25-03-19 Tue 02-04-19
Training and Maintenance 10 days Wed 03-04-19 Tue 16-04-19
Post Launch Support 15 days Wed 17-04-19 Tue 07-05-19
M5: Successful Project Release 0 days Tue 16-04-19 Tue 16-04-19
Project Closure 23 days Wed 17-04-19 Fri 17-05-19
Document archival 3 days Wed 17-04-19 Fri 19-04-19
Payment Completion 7 days Mon 22-04-19 Tue 30-04-19
Resource Release 3 days Wed 01-05-19 Fri 03-05-19
Project Evaluation 10 days Mon 06-05-19 Fri 17-05-19
Client Sign off 1 day Mon 06-05-19 Mon 06-05-19
M6: Project Closes 0 days Mon 06-05-19 Mon 06-05-19
The scheduled Gantt Chart for the project is represented in the following picture-
PROJECT MANAGEMENT
Resource Allocation 1 day Wed 21-11-18 Wed 21-11-18
M2: Preparation and Approval
of Project Plan 0 days Wed 21-11-18 Wed 21-11-18
Project Implementation 46 days Thu 22-11-18 Thu 24-01-19
Interface Designing 15 days Thu 22-11-18 Wed 12-12-18
Software Coding 20 days Thu 13-12-18 Wed 09-01-19
Database Designing 15 days Thu 13-12-18 Wed 02-01-19
Linking with the database 13 days Thu 03-01-19 Mon 21-01-19
Documentation 3 days Tue 22-01-19 Thu 24-01-19
M3: Successful application and
website development 0 days Thu 24-01-19 Thu 24-01-19
Testing 41 days Fri 25-01-19 Fri 22-03-19
Unit Testing 8 days Fri 25-01-19 Tue 05-02-19
System testing 15 days Wed 06-02-19 Tue 26-02-19
User acceptance testing 10 days Wed 27-02-19 Tue 12-03-19
Bug Fixing (if any) 8 days Wed 13-03-19 Fri 22-03-19
M4: Completion of Testing and
Bug Fixing 0 days Fri 22-03-19 Fri 22-03-19
Website and Application Go Live
and Training 32 days Mon 25-03-19 Tue 07-05-19
Website and Application
Demonstration 7 days Mon 25-03-19 Tue 02-04-19
Training and Maintenance 10 days Wed 03-04-19 Tue 16-04-19
Post Launch Support 15 days Wed 17-04-19 Tue 07-05-19
M5: Successful Project Release 0 days Tue 16-04-19 Tue 16-04-19
Project Closure 23 days Wed 17-04-19 Fri 17-05-19
Document archival 3 days Wed 17-04-19 Fri 19-04-19
Payment Completion 7 days Mon 22-04-19 Tue 30-04-19
Resource Release 3 days Wed 01-05-19 Fri 03-05-19
Project Evaluation 10 days Mon 06-05-19 Fri 17-05-19
Client Sign off 1 day Mon 06-05-19 Mon 06-05-19
M6: Project Closes 0 days Mon 06-05-19 Mon 06-05-19
The scheduled Gantt Chart for the project is represented in the following picture-
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

10
PROJECT MANAGEMENT
PROJECT MANAGEMENT

11
PROJECT MANAGEMENT
Figure 1: Representing the Gantt Chart of the project
(Source: Generated by Author using MS project)
The work activities marked in red in the Gantt chart above depict the critical path of the project
The Work breakdown Structure of the project is as follows-
i-Crop Project
Implementation
Initiation Phase
Setting up a meeting with
the Cleints
Identification of the
Requirmenet
specifications
Specification
documentation
Documenting the
findingsM1: Requirements and
the Specification of the
project are gathered
Project Planning
Setting the structure of
Project Plan
Project Scheduling
Project Budget Estimation
Resource Estimation
Resource Allocation
M2: Preparation and
Approval of Project Plan
Project Implementation
Interface Designing
Software Coding
Database Designing
Linking with the database
Documentation
M3: Successful
application and website
development
Testing
Unit Testing
System testing
User acceptance testing
Bug Fixing (if
any)M4: Completion of Testing
and Bug Fixing
Website and Application
Go Live and Training
Website and Application
Demonstration
Training and
Maintaianance
Post Launch Support
M5: Successful Project
Release
Project Closure
Document archival
Payement
CompletionResource Release
Project Evaluation
Client Sign off
M6: Project Closes
Figure 2: Representing the work breakdown structure of the project
(Source: created by author using MS schedule Pro)
3.5. Project Budget
The estimated budget of the project is as follows-
Task Name Duration Resource Names Cost
i-Crop Project
Implementation 164 days $231,960.00
Initiation Phase 22 days $18,720.00
Setting up a meeting
with the Clients 6 days Functional Manager $1,680.00
Identification of the
Requirement specifications 11 days Project Manager, Functional
Manager $11,440.00
Specification
documentation 3 days Archive[1],Document handler $5,360.00
Documenting the
findings 2 days Document handler $240.00
PROJECT MANAGEMENT
Figure 1: Representing the Gantt Chart of the project
(Source: Generated by Author using MS project)
The work activities marked in red in the Gantt chart above depict the critical path of the project
The Work breakdown Structure of the project is as follows-
i-Crop Project
Implementation
Initiation Phase
Setting up a meeting with
the Cleints
Identification of the
Requirmenet
specifications
Specification
documentation
Documenting the
findingsM1: Requirements and
the Specification of the
project are gathered
Project Planning
Setting the structure of
Project Plan
Project Scheduling
Project Budget Estimation
Resource Estimation
Resource Allocation
M2: Preparation and
Approval of Project Plan
Project Implementation
Interface Designing
Software Coding
Database Designing
Linking with the database
Documentation
M3: Successful
application and website
development
Testing
Unit Testing
System testing
User acceptance testing
Bug Fixing (if
any)M4: Completion of Testing
and Bug Fixing
Website and Application
Go Live and Training
Website and Application
Demonstration
Training and
Maintaianance
Post Launch Support
M5: Successful Project
Release
Project Closure
Document archival
Payement
CompletionResource Release
Project Evaluation
Client Sign off
M6: Project Closes
Figure 2: Representing the work breakdown structure of the project
(Source: created by author using MS schedule Pro)
3.5. Project Budget
The estimated budget of the project is as follows-
Task Name Duration Resource Names Cost
i-Crop Project
Implementation 164 days $231,960.00
Initiation Phase 22 days $18,720.00
Setting up a meeting
with the Clients 6 days Functional Manager $1,680.00
Identification of the
Requirement specifications 11 days Project Manager, Functional
Manager $11,440.00
Specification
documentation 3 days Archive[1],Document handler $5,360.00
Documenting the
findings 2 days Document handler $240.00
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide
1 out of 21
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
 +13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.