Weekly Progress Report: Cloud ERP Implementation Project (Weeks 2-12)

This document presents a detailed weekly progress report on the implementation of a Cloud-based ERP system, spanning from week 2 to week 12. The report meticulously outlines each week's milestones, planned versus actual progress, and any encountered challenges. Key areas covered include topic selection, annotated bibliography, literature review, project problem domain, aim, scope, expected outcomes, resource allocation, and methodology. Each week's section provides specific details on actions taken, results achieved, and planning issues faced. The report also includes a bibliography of relevant sources used in the project. This comprehensive documentation offers valuable insights into the project's evolution, challenges, and solutions adopted throughout the implementation process. The report covers the entire project lifecycle, providing a clear picture of the complexities involved in implementing a cloud-based ERP system.

Weekly Progress Report
Full Name
Student ID
Subject Emerging Technology and Innovations
Assignment No Weekly Progress Report
Due Date 15th February, 2019
Lecturer’s Name
Week 2:
NAME:
PROJECT TITLE: Implementing Cloud-based ERP system
WEEK NO: 2 DATE: 3rd October, 2019
PLANNING
MILESTONE: PLANNED: ACTUAL: COMMENT:
Topic selection 10rd October 7rd October There are a huge
number of topics
under emerging
technologies, the
topic of
implementing
cloud based ERP
system has been
chosen.
ISSUES
DESCRIPTION: DATE: ACTION/
RESULTS:
FINISHED (Y/N)
The field of
emerging
technologies and
innovation is a
huge one, there
are numerous
topics under it, and
hence it was tough
5rd October Cloud based ERP
system helps an
organization in
keeping up with
various evolving
technologies as well
as business
practices.
Yes
1

to select one
among them.
2

Week 3:
NAME:
PROJECT TITLE:
WEEK NO: 3 DATE: 11rd October
PLANNING
MILESTONE: PLANNED: ACTUAL: COMMENT:
Annotated
bibliography
18rd October 16th October Numerous
journals and
articles were
found for carrying
out annotated
bibliography.
ISSUES
DESCRIPTION: DATE: ACTION/
RESULTS:
FINISHED (Y/N)
Selecting sources
that are relevant
and has the
appropriate amount
of content was
difficult.
14th October The sources that
had very limited
content but had the
needed data were
chosen.
yes
3

Week 4:
NAME:
PROJECT TITLE: Implementing Cloud-based ERP system
WEEK NO: 4 DATE: 19rd October
PLANNING
MILESTONE: PLANNED: ACTUAL: COMMENT:
Literature review 26rd October 25th October A literature review
has been carried
out in order to
know regarding
previous
researches that
are already
completed on this
topic
ISSUES
DESCRIPTION: DATE: ACTION/
RESULTS:
FINISHED (Y/N)
There were few
sources that
provided complete
data hence it was
tough to
23rd October Sources were
checked properly
regarding if they
have complete data.
yes
4

Week 5:
NAME:
PROJECT TITLE: Implementing Cloud-based ERP system
WEEK NO: 5 DATE: 27rd October
PLANNING
MILESTONE: PLANNED: ACTUAL: COMMENT:
Project problem
domain
30rd October 30rd October The project
problem domain
had been figured
out on the basis of
the advantages
provided to the
organizations as
well as challenges
faced by ERP
implementations
Background of the
project
3rd November 2nd November The background
regarding why the
organization use
ERP system and
what are the
challenges faced
by them are
mentioned.
ISSUES
DESCRIPTION: DATE: ACTION/
RESULTS:
FINISHED (Y/N)
Selecting a
problem domain
was difficult
because different
organizations face
different problems
based on the fields
they deal with and
the size of the
organizations.
1st November A specific problem
domain was chosen
that is faced by
most of the
organizations.
Yes
5

Week 6:
NAME:
PROJECT TITLE: Implementing Cloud-based ERP system
WEEK NO: 6 DATE: 4th November
PLANNING
MILESTONE: PLANNED: ACTUAL: COMMENT:
Project aim 11th November 10th November The aim of the
project has been
selected.
ISSUES
DESCRIPTION: DATE: ACTION/
RESULTS:
FINISHED (Y/N)
The aim was
confirmed until the
supervisor did not
check on it
9th November With the help of
the supervisor the
aim of the project
was finalized and
the project was
further proceeded
yes
6

Week 7:
NAME:
PROJECT TITLE: Implementing Cloud-based ERP system
WEEK NO: 7 DATE: 12th November
PLANNING
MILESTONE: PLANNED: ACTUAL: COMMENT:
Project scope 19th November 17th November The scope of the
project has been
decided
ISSUES
DESCRIPTION: DATE: ACTION/
RESULTS:
FINISHED (Y/N)
There was a
confusion with the
project scope, all
the group members
did not agree to it
16th November The help of
supervisor was
taken and the scope
was finalized
Yes
7

Week 8:
NAME:
PROJECT TITLE: Implementing Cloud-based ERP system
WEEK NO: 8 DATE: 20th November
PLANNING
MILESTONE: PLANNED: ACTUAL: COMMENT:
Project outcome 27th November 25th November The expected
outcome at the
end of the project
had been
mentioned
ISSUES
DESCRIPTION: DATE: ACTION/
RESULTS:
FINISHED (Y/N)
Outcomes were
selected on the
basis of team
members’
discussion
22nd November Authenticate
outcomes were
selected that would
help in solving the
problems faced by
the organization
Yes
8

Week 9:
NAME:
PROJECT TITLE: Implementing Cloud-based ERP system
WEEK NO: 9 DATE: 28th November
PLANNING
MILESTONE: PLANNED: ACTUAL: COMMENT:
Resources 5th December 5th December The resources
that would be
needed were
decided
ISSUES
DESCRIPTION: DATE: ACTION/
RESULTS:
FINISHED (Y/N)
Selecting
resources were
tough
2nd December Discussion with
team members was
carried out, for
choosing the
resources
Yes
9

Week 10:
NAME:
PROJECT TITLE: Implementing Cloud-based ERP system
WEEK NO: 10 DATE: 6th December
PLANNING
MILESTONE: PLANNED: ACTUAL: COMMENT:
Selecting the
resources
13th December 11th December Various
resources that had
been selected
were not available
hence some more
resources were
selected
ISSUES
DESCRIPTION: DATE: ACTION/
RESULTS:
FINISHED (Y/N)
Among the newly
selected resources,
few were
unavailable
10th December The supervisor
was asked for help
for selecting
resources that
would be readily
available
yes
10

Week 11:
NAME:
PROJECT TITLE: Implementing Cloud-based ERP system
WEEK NO: 11 DATE: 14th December
PLANNING
MILESTONE: PLANNED: ACTUAL: COMMENT:
Methodology 21th December 20th December Methodology has
been decided,
analysis of various
sources of data
was carried out,
research methods
were selected,
data collection
was done
ISSUES
DESCRIPTION: DATE: ACTION/
RESULTS:
FINISHED (Y/N)
19th December Yes
Week 12:
11

NAME:
PROJECT TITLE: Implementing Cloud-based ERP system
WEEK NO: 12 DATE: 22nd December
PLANNING
MILESTONE: PLANNED: ACTUAL: COMMENT:
Methodology 29th December 28th December Some ethical
issues were
considered.
ISSUES
DESCRIPTION: DATE: ACTION/
RESULTS:
FINISHED (Y/N)
There were
numerous ethical
that were
inappropriate
25th December With the help of a
supervisor
appropriate ethical
issues were
identified
Yes
12

Bibliography
Carutasu, N., & Carutasu, G. (2016). Cloud ERP implementation. FAIMA Business & Management
Journal, 4(1), 31.
Jalil, D., & Bakar, M. S. A. (2017). Adapting Software Factory Approach into Cloud ERP Production
Model. International Journal of Computer Science and Information Security, 15(1), 221.
Khot, N., Mudur, K., Thorat, O., & Doulatramani, Y. (2017). Information Intendance System on Cloud.
Popa, S., Vaida, M. F., & AG, C. (2016). A Practical Strategy for ERP to Cloud Integration. Studies in
Informatics and Control, 25(3), 375-384.
13