Website and Application Development for I-Crop: Project Report

Verified

Added on  2023/06/07

|15
|2690
|419
Project
AI Summary
This document presents the final report for the I-Crop website and mobile application development project, detailing various aspects from inception to closure. It begins with defining the Measurable Organizational Value (MOV), covering financial, customer, operational, strategic, and social areas, outlining improvements in customer experience, operational pace, cost reduction, and enhanced communication. The report then defines the project scope, including requirements, in-scope and out-of-scope items, deliverables, and acceptance criteria, along with a list of necessary resources. A detailed project schedule is provided, featuring milestones, activities/tasks, resource assignments, and time estimates for each activity. Furthermore, the report includes a comprehensive project budget, a risk analysis and plan identifying potential risks and mitigation strategies, and a quality management plan ensuring the project's outputs meet the required standards through verification and validation activities. The document concludes with a closure and evaluation section, including an annotated bibliography of relevant sources, providing a holistic view of the project's lifecycle and outcomes.
Document Page
Running head: PROJECT FINAL REPORT
Project Final Report
Website and Application Development for I-Crop
Name of the Student:
Student ID:
Name of the Students:
Author’s note:
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
1PROJECT FINAL REPORT
1. Part One: MOV - Measurable Organisational Value
Financial Area: Economically the project has to be feasible for the clients and it has the
highest priority in terms of important factors.
Customer Area: Customer Approval is another major factor for alignment of the project
activities and lower priority management.
Operational Area: The operations of the project can be efficiently implied for the
alignment of the successive management.
Strategy Area: The strategy area can be implied for the alignment of the successive
implication of the operations and it has a specific area of importance for the project.
Social Area: The social area is responsible for making sure that the activities can be
implied successfully for operating in the reasonable formation model.
Better- Improved customer experience with website (even accessible from mobile) and
mobile application
Faster- Increase the pace of operations for the formation of the efficient customer support
and formation
Cheaper- Cost and Expenses of the activities can be decreased and hence it would result
in more profit generation
Do more- Provide scope for the communication and implication of the activities
successfully
Document Page
2PROJECT FINAL REPORT
Rank Impact Metrics Timeframe (in months)
1 Financial NPV and Profit Calculation 2
2 Customer Customer feedback and Suggestions 4
3 Operational Management Plan 5
4 Strategy Strategic Analysis Matrix 6
5 Social Social Sites Review 2
2. Part Two: Define Scope and produce a Scope Management Plan
Define the scope: Scope can be defined as the involved functions and deliverable for the project
of website and mobile application formation project of I-Crop.
Requirements: The inclusion of the principles of project management with the website and
mobile formation technology are the requirements of the project.
In scope-out scope items: The initiation documents, project plan, website and mobile
application design, website and mobile application, and final closure report are the in scope items
Document Page
3PROJECT FINAL REPORT
of the project of website and mobile application formation project of I-Crop. The transportation
requirements and the communication plan are the out of scope items of the project of website and
mobile application formation project of I-Crop.
Deliverables: Project initiation documents, project plan, website and mobile application design,
website and mobile application, and final closure report
Acceptance Criteria: The acceptance criteria for the project of website and mobile application
formation project of I-Crop is,
All documents are made properly
Design and Plan has been pre-approved
All testing results are positive and as expected
Feasible Cost Analysis has been executed
Provide a list of Resources:
People: Analyst, Documenter, Planner, Project Manager, Website Designer, Application
Designer, Engineer, Website Developer, Programmer, and Application Developer
Technology: Website Designing and Developing Tools, Mobile Application Designing and
Developing Tools
Facilities: Testing facilities and Project meeting rooms
3. Part Three: Project Schedule
Milestones
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
4PROJECT FINAL REPORT
WBS Milestone Name Duration Start Finish
1.5 Sign off 0 days Fri 10/12/18 Fri 10/12/18
2.5 Plan Approval 0 days Mon 10/29/18 Mon 10/29/18
3.1.5 Design Approval 0 days Tue 11/13/18 Tue 11/13/18
3.2.5 Design Approval 0 days Wed 11/28/18 Wed 11/28/18
5.5 Closed 0 days Fri 2/8/19 Fri 2/8/19
Activities / Tasks
WBS Task Name
1.1 Requirement Analysis
1.2 Charter Documentation
1.3 Initiation Document
1.4 Document Submission
2.1 Selection of Plan Methodology
2.2 Outline of plan
2.3 Plan Review
2.4 Complete Plan
3.1.1 Design Platform selection
3.1.2 Outline of Website
3.1.3 Review of Website
3.1.4 Complete Website Design
3.2.1 Design Platform selection
3.2.2 Outline of Application
3.2.3 Review of Application Design
Document Page
5PROJECT FINAL REPORT
3.2.4 Complete Application Design
4.1.1 Buy Website Domain
4.1.2 Develop Website Interface
4.1.3 Functions are aligned
4.1.4 Programming the website functions
4.1.5 Checking Mobile Compatibility
4.1.6 Complete Website is developed
4.2.1 Application Interface is developed
4.2.2 Programming of the application functions
4.2.3 Application Integration
4.2.4 Complete Application Development
5.1 Developing Final Reports
5.2 Checklist Development
5.3 Submission of documents
5.4 Sign off
Document Page
6PROJECT FINAL REPORT
Resource Assignments
ID Resource Name Work
1 Analyst 16 hrs
2 Documenter 96 hrs
3 Planner 72 hrs
4 Project Manager 40 hrs
5 Website Designer 72 hrs
6 Application Designer 72 hrs
7 Engineer 64 hrs
8 Website Developer 120 hrs
9 Programmer 96 hrs
10 Application Developer 112 hrs
11 Documents 3
12 Design Tools 4
13 Domain Cost 1
Details
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
T W T M S S F T W T M S
Sep 23, '18 Oct 21, '18 Nov 18, '18 Dec 16, '18 Jan 13, '19 Feb 10, '19
16h
40h 24h 16h 16h
32h 40h
16h 24h
32h 40h
24h 48h
16h 24h 24h
8h 48h 64h
24h 8h 40h 24h
32h 24h 56h
1.67 0.33 0.67 0.33
1 2 1
1
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
7PROJECT FINAL REPORT
Estimates for Each Activity / Task
ID Task
Mode
WBS Task Name Duration Start Finish Predecessors
0 0 Website and Application
Development for I-Crop
95 days Mon 10/1/18 Fri 2/8/19
1 1 Initial Phase 10 days Mon 10/1/18 Fri 10/12/18
2 1.1 Requirement Analysis 2 days Mon 10/1/18 Tue 10/2/18
3 1.2 Charter Documentation 3 days Wed 10/3/18 Fri 10/5/18 2
4 1.3 Initiation Document 3 days Mon 10/8/18 Wed 10/10/18 3
5 1.4 Document Submission 2 days Thu 10/11/18 Fri 10/12/18 4
6 1.5 Sign off 0 days Fri 10/12/18 Fri 10/12/18 5
7 2 Planning Phase 11 days Mon 10/15/18 Mon 10/29/18
8 2.1 Selection of Plan Methodology 1 day Mon 10/15/18 Mon 10/15/18 6
9 2.2 Outline of plan 3 days Tue 10/16/18 Thu 10/18/18 8
10 2.3 Plan Review 2 days Fri 10/19/18 Mon 10/22/18 9
11 2.4 Complete Plan 5 days Tue 10/23/18 Mon 10/29/18 10
12 2.5 Plan Approval 0 days Mon 10/29/18 Mon 10/29/18 11
13 3 Design Phase 22 days Tue 10/30/18 Wed 11/28/18
14 3.1 Website Design 11 days Tue 10/30/18 Tue 11/13/18
15 3.1.1 Design Platform selection 1 day Tue 10/30/18 Tue 10/30/18 12
16 3.1.2 Outline of Website 3 days Wed 10/31/18 Fri 11/2/18 15
17 3.1.3 Review of Website 2 days Mon 11/5/18 Tue 11/6/18 16
18 3.1.4 Complete Website Design 5 days Wed 11/7/18 Tue 11/13/18 17
19 3.1.5 Design Approval 0 days Tue 11/13/18 Tue 11/13/18 18
20 3.2 Application Design 11 days Wed 11/14/18 Wed 11/28/18
21 3.2.1 Design Platform selection 1 day Wed 11/14/18 Wed 11/14/18 19
22 3.2.2 Outline of Application 3 days Thu 11/15/18 Mon 11/19/18 21
23 3.2.3 Review of Application Design2 days Tue 11/20/18 Wed 11/21/18 22
24 3.2.4 Complete Application Design 5 days Thu 11/22/18 Wed 11/28/18 23
25 3.2.5 Design Approval 0 days Wed 11/28/18 Wed 11/28/18 24
26 4 Development Phase 45 days Thu 11/29/18 Wed 1/30/19
27 4.1 Website Development 20 days Thu 11/29/18 Wed 12/26/18
28 4.1.1 Buy Website Domain 1 day Thu 11/29/18 Thu 11/29/18 25
29 4.1.2 Develop Website Interface 5 days Fri 11/30/18 Thu 12/6/18 28
30 4.1.3 Functions are aligned 2 days Fri 12/7/18 Mon 12/10/18 29
31 4.1.4 Programming the website functions4 days Tue 12/11/18 Fri 12/14/18 30
32 4.1.5 Checking Mobile Compatibility3 days Mon 12/17/18 Wed 12/19/18 31
33 4.1.6 Complete Website is developed5 days Thu 12/20/18 Wed 12/26/18 32
34 4.2 Mobile Application Development25 days Thu 12/27/18 Wed 1/30/19
35 4.2.1 Application Interface is developed4 days Thu 12/27/18 Tue 1/1/19 33
36 4.2.2 Programming of the
application functions
8 days Wed 1/2/19 Fri 1/11/19 35
37 4.2.3 Application Integration 3 days Mon 1/14/19 Wed 1/16/19 36
38 4.2.4 Complete Application Development10 days Thu 1/17/19 Wed 1/30/19 37
39 5 Closure 7 days Thu 1/31/19 Fri 2/8/19
40 5.1 Developing Final Reports 3 days Thu 1/31/19 Mon 2/4/19 38
41 5.2 Checklist Development 2 days Tue 2/5/19 Wed 2/6/19 40
42 5.3 Submission of documents 1 day Thu 2/7/19 Thu 2/7/19 41
43 5.4 Sign off 1 day Fri 2/8/19 Fri 2/8/19 42
44 5.5 Closed 0 days Fri 2/8/19 Fri 2/8/19 43
F
Aug 12, '18
Document Page
8PROJECT FINAL REPORT
Project Budget
The time phased budget showing the complete budget of the project is shown below,
4. Part Four: Project Risk Analysis and Plan
Ref no RF000901 RF000902 RF000903 RF000904 RF000905
Risk Name Website and
Application
Development
Issues
Design Flaws Over budget Human
Errors
Delay in
Completion
Description Functions of
the website and
application
might not work
properly
Design made
for website
and mobile
application
would not be
feasible
The project
can go over
budget by
exhausting
more
resources than
planned
Human
mistakes in
executing the
activities of
project is
another
major risk
Overall delay
in completion
of the project
Category Technical Technical Financial Human Operational
Triggers Equipment or
device failures
Lack of
Design
Principles
Shortage of
Resources
General
Mistakes by
human
Minute issues
in the project
Potential
Response
Prior Testing
methods
SDLC
approach
should be
used
Provisional
budget should
be developed
Training of
the members
Contingency
Planning
should be
done
Document Page
9PROJECT FINAL REPORT
Risk
Owner
Developer Designer Budgeter Project
Manager
Planner
Probability Likely Possible Possible Unlikely Likely
Impact Very High High Medium High Low
Ranking 1 2 3 4 5
5. Part Five: Quality Management Plan
Quality management plan deals with the analysis of the factors of quality involved for the project
and develop some methods of dealing with the execution of the project. The quality management
activities ensure that the outputs of the project are of standard quality and acceptable by the
client. For this project, the testing of the go live function can be done for ensuring the completion
of the project
A set of verification activities: Various testing methods like alpha testing, simulation, mobile
platform acceptability, UI testing, and performance testing
A set of validation activities: Quality analysis and control using 7QC, checklist verification,
and proper documentation
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
10PROJECT FINAL REPORT
Bibliography
Braglia, M., &Frosolini, M. (2014).An integrated approach to implement project management
information systems within the extended enterprise.International Journal of Project
Management, 32(1), 18-29.
Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management.
Cengage Learning.
Galliers, R. D., &Leidner, D. E. (2014). Strategic information management: challenges and
strategies in managing information systems. Routledge.
Garton, C., & McCulloch, E. (2012). Fundamentals of Technology Project Management. MC
Press, LLC.
Goetsch, D. L., & Davis, S. B. (2014). Quality management for organizational
excellence.pearson.
Kendrick, T. (2015). Identifying and managing project risk: essential tools for failure-proofing
your project. AMACOM Div American Mgmt Assn.
Nanda, V. (2016). Quality management system handbook for product development
companies.CRC Press.
Pritchard, C. L., & PMP, P. R. (2014). Risk management: concepts and guidance. CRC Press.
Schwalbe, K. (2015). Information technology project management.Cengage Learning.
Stark, J. (2015). Product lifecycle management.In Product Lifecycle Management (pp. 1-
29).Springer International Publishing.
Document Page
11PROJECT FINAL REPORT
Verburg, R. M., Bosch-Sijtsema, P., &Vartiainen, M. (2013).Getting it done: Critical success
factors for project managers in virtual work settings.International Journal of Project
Management, 31(1), 68-79.
Verzuh, E. (2015). The fast forward MBA in project management.John Wiley & Sons.
chevron_up_icon
1 out of 15
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]