Assignment Cover Sheet – Individual & Group

Course Name: Managing Project and Systemic Risk

Course Coordinator: Kiran Hiriyanna
Assignment: Enterprise Risk Management Framework

Student’s Names and ID Number:

Please write your full name as stated when you enrolled and your Student ID number
1. Igor Ritonga / a1737050
Due Date: 2 April 2018
Date Submitted: 2 April 2018
Word length: 2929

Student Declaration:

 I have read and understood the rules relating to plagiarism and related forms of cheating as
included in the Course Information Booklet supplied for this course. I understand that
providing only a reference when directly quoting work, without also using quotation marks or
indentation, still constitutes plagiarism.

 This submission is a final version and not a draft. It is entirely my own work, it does not
include any plagiarised material. It has not been submitted for any other course.

 I give permission for this work to be photocopied, scanned and electronically submitted to
check for plagiarism.

 I have kept a photocopy or electronic copy of this assignment that I can produce on demand.
 I understand that by typing my name below I am providing a digital signature

Signed: Igor Ritonga Date: 2 April 2018

Business Plan

XYZ COMPANY

Enterprise Risk Management Framework a1737050/Igor Ritonga 2

Table of Contents

1 BUSINESS OVERVIEW 4
2 PRODUCT AND SERVICES 4
2.1 Segmentation 4
2.2 The Supply Vendor 4
3 TIME MANAGEMENT 5
3.1 Project Schedule 5-7
3.2 Schedule Control 8
4 COST MANAGEMENT 8
4.1 Cost Estimates and Budget 8
4.2 Control Cost 8
5 QUALITY MANAGEMENT 9
5.1 Quality Assurance Reviews 9
5.2 Quality Control 9
6 HUMAN RESOURCE MANAGEMENT 9
6.1 Roles and Responsibilities 9
6.2 Project Organisation Chart 10
7 COMMUNICATIONS AND CHANGE MANAGEMENT 10
7.1 Manage Communications 10
7.2 Manage The Changes 10
8 RISK MANAGEMENT 11
8.1 Risk Response and Control 11
9 PROCUREMENT MANAGEMENT 12
10 APPENDIX A – GLOSSARY 12

Enterprise Risk Management Framework a1737050/Igor Ritonga 3

1 Business Overview
Project management software is an important part of the construction of software, therefore
required project management for the design of the software. Surely this management required
by managers or leaders of the project so that the results obtained in accordance with needs,
time, and costs are provided. The software project is a great project because the resulting
software should be able to manage the process of accounting or accounting companies.
Many activities can be done in software projects, such as creating the design, managing
websites, designing enterprise information system, installing applications on the computer
system in the company and more. PT. XYZ is a company that specializes in terms of the designing
system of information within the company and perform the installation and perform maintenance
or update of the applications that have been installed. As a new company, we are able to give a
unique design of system information and which is comparable enough to the industry. This
company believes can provide an exceptional design for planning and creating your information
system especially in accounting system. The scope of this plan starting from preparation of the
project until the final results of the project.

VISION Become the trendsetter in designing system information

MISSION Think out of the box and creates new innovation in every project
GOAL Gives the best quality in terms of planning, installing and maintenance also always
be punctual on every project
OBJECTIVES Follow up the system information news and trends to understand what clients
need

2 Product and Services

XYZ Company specialized in designing accounting information system that provides a
unique design and integrated to task-related activities in a company. This accounting information
system will ease management level in administering the finances and the preparation of the
financial statements of the company, which includes: the report realization of a budget, balance
sheet, cash flow statement and the notes to financial statements required of companies.

Making an appointment and meet with the client is important to know the client’s needs
and ideas. Producing an advertisement is our main strategy to show client our capability and
characters as a company that suitable for the client’s need. XYZ company will provide one sample
of our accounting system product to shows the client what our company product and our quality.

2.1 Segmentation

Enterprise Risk Management Framework a1737050/Igor Ritonga 4

It will be produced professionally by our designer and our professional alliance by sketching the
design system, presenting the concept, and installing it. Compare to other competitors, XYZ
company has an enthusiasm for every project with brilliant ideas and varying innovations to
serve all kind of company, institution, government, and industry.

2.2 The Supply Vendor

XYZ company provides all kinds of products from various vendors of existing information systems
on the market. By providing a wide range of products and innovation, XYZ company can be
expected to be a leading company in the field of the provision of the innovative financial
information system.

3 Time Management
The project schedule was drawn up based on the structure of the details of the work
(work breakdown structure) that contains a list of jobs or tasks that are done within a project.
To work on a financial information system development projects take time to build the system,
plus 20 working days to mentoring and 30 working days for the treatment system as well as
18 days for the preparation of additional time changes work and meetings. The total time is
provided for this project, ranging from the preparation of the project until completion of the
project is 110 days.

3.1 Project Schedule

WBS PROJECT TASK DURATION START END DATE PREDECESSOR
DATE

1 Project initiation and project 18 days 06/07/2018 09/07/2018

planning

1.1 Create a project charter 4 days 06/07/2018 09/07/2018

1.1.1 Discussion with the owner of 1 day 06/07/2018 06/07/2018
the project

Enterprise Risk Management Framework a1737050/Igor Ritonga 5

 1.1.2 Discussions with the project 1 day 07/07/2018 07/07/2018 1.1.1
team
1.1.3 Documentation of the project 2 days 08/07/2018 09/07/2018 1.1.2
charter
1.2 Make a software project 14 days 12/07/2018 25/07/2018
management plan

1.2.1 Create the scope of work 4 days 12/07/2018 14/07/2018 1.1.3

1.2.2 Make the structure of the 5 days 15/07/2018 20/07/2018 1.2.1
details of the job
1.2.3 Create the schedule of the 3 days 21/07/2018 23/07/2018 1.2.2
project
1.2.4 Resources planning 2 days 21/07/2018 22/07/2018 1.2.2
1.2.5 Create a cost budget plan 5 days 21/07/2018 25/07/2018 1.2.2
1.2.6 Communication planning 2 days 21/07/2018 22/07/2018 1.2.2
1.2.7 Making the procurement 2 days 21/07/2018 22/07/2018 1.2.2
planning
1.2.8 Make planning for the changes 2 days 21/07/2018 22/07/2018 1.2.2
1.2.9 Create risks planning 2 days 21/07/2018 22/07/2018 1.2.2
1.2.10 Create quality planning 2 days 21/07/2018 22/07/2018 1.2.2
2 Analysis and design 19 days 23/07/2018 18/08/2018
2.1 Make Software Requirement 13 days 23/07/2018 01/08/2018
Specification (SRS)

2.1.1 Discussions with management 1 day 23/07/2018 23/07/2018 1.2.10

2.1.2 Discussion with the user 1 day 26/07/2018 26/07/2018 2.1.1
2.1.3 Discussion to determines the 1 day 27/07/2018 27/07/2018 2.1.2
format of the system

2.1.4 Create activity diagram 5 days 28/07/2018 03/08/2018 2.1.3

business processes

2.1.5 Create use case diagram 3 days 04/08/2018 06/08/2018 2.1.4

2.1.6 Create documentation of 2 days 09/08/2018 10/08/2018 2.1.5
analysis and system design

2.2 Make Software Design 16 days 28/07/2018 18/08/2018

Description (SDD)

2.2.1 Create Entity Relationship 3 days 11/08/2018 13/08/2018 2.1.6

Diagram (ERD)
2.2.2 Create class diagram 3 days 16/08/2018 18/08/2018 2.2.1
2.2.3 Make activity diagram function 3 days 09/08/2018 13/08/2018 2.1.5
2.2.4 Create design interface 2 days 09/08/2018 10/08/2018 2.1.5
2.2.5 Create navigation structure 2 days 09/08/2018 10/08/2018 2.1.5
2.2.6 Make web design 3 days 09/08/2018 12/08/2018 2.2.5
2.2.7 Make report design 3 days 28/07/2018 30/07/2018 2.1.3
2.2.8 Create architectural design 2 days 09/08/2018 10/08/2018 2.1.5

Enterprise Risk Management Framework a1737050/Igor Ritonga 6

 2.2.9 Make SOP application 2 days 16/07/2018 17/07/2018 2.2.6
2.2.10 Software design 3 days 11/08/2018 13/08/2018 2.2.8
documentation
3 Coding 60 days 16/08/2018 05/11/2018
3.1 Coding accounting software 60 days 16/08/2018 05/11/2018 2.2.10
3.2 Coding web publication 45 days 16/08/2018 05/10/2018 2.2.10
software
3.3 Program documentation 3 days 18/10/2018 20/10/2018 3.2
4 Testing the program 12 days 21/10/2018 05/11/2018
4.1 Testing the unit 21/10/2018 24/10/2018 3.3
4.2 Integrated & Performance 5 days 26/10/2018 01/11/2018 4.1
Test
4.3 Generate reports of 2 days 02/11/2018 03/11/2018 4.2
improvements
4.4 Create documentation of the 2 days 04/11/2018 05/11/2018 4.3
testing program

5 Procurement Of Infrastructure 28 days 11/08/2018 17/09/2018

(Computer Network + Other)

5.1 Procurement of hardware 20 days 11/08/2018 07/09/18 2.2.8

5.2 Procurement intranet network 20 days 11/08/2018 07/09/18 2.2.8
5.3 Internet procurement 20 days 11/08/2018 07/09/18 2.2.8
5.4 Configuration (Service + 5 days 08/09/18 14/09/18 5.3
Security)
5.5 Performance Test 3 days 15/09/18 17/09/18 5.4
6 Deployment 5 days 20/09/18 24/09/18
6.1 System configuration 3 days 20/09/18 22/09/18 5.1
6.2 Replication 2 days 22/09/18 23/09/18 5.3
7 Human resources training 12 days 15/09/18 29/09/18
7.1 Sys-Admin Linux training 3 days 15/09/18 17/09/18 5.5
7.2 Network administrator 3 days 15/09/18 17/09/18 5.5
training
7.3 Web Master training 3 days 15/09/18 17/09/18 5.5
7.4 Database administrator 3 days 15/09/18 17/09/18 5.5
training
7.5 Training to make report 2 days 15/09/18 16/09/18 5.5
generator
7.6 Training In the use of the 4 days 24/09/18 29/09/18 6.2
application
7.7 Mentoring 20 days 30/09/18 27/10/18 7.6
8 Maintenance 30 days 30/09/18 20/11/18 7.6

Enterprise Risk Management Framework a1737050/Igor Ritonga 7

3.2 Schedule Control
The controls will be done every 4 months in a year. If problems occur in the system that has
been running in period of one year the XYZ company will perform the necessary repairs in
accordance with an approved warranty in this agreement

4 Cost Management
The budget of the project is calculated based on resources levelling with the aim to be
able to figure out the timing and magnitude of project implementation the resource needs for
labour. Resource leveling is done with the help of Ms. program Project.

4.1 Cost Estimates and Budget

Description Of The Activity Duration Estimated Cost
Project initiation and project planning 18 days $ 1,700.00
Analysis and design 19 days $ 2,250.00
Coding 60 days $ 5,300.00
Testing the program 12 days $ 8,600.00
Procurement Of Infrastructure (Computer 28 days $ 14,000.00
Network + Other)
Deployment 5 days $ 350.00
Human resources training 12 days $ 700.00
Mentoring 20 days $ 800.00
Maintenance 30 days $ 1,450.00
The cost of printing the documentation $ 2,400.00
The cost of backup operations $ 3,200.00
The unexpected cost budget $ 2,150.00
Total Budget $ 42,900.00

4.2 Control Cost

It is important for a top management to understand very well and clearly define the respective
roles of information systems or information technology which is owned by the company. This is
all to prevent the occurrence of excess investment that can create swelling corporate overhead
costs or a lack of investment which can result in loss of opportunity (opportunity loss). If these
possibilities can be identified from the beginning then it can create a good cost control and
prevent the occurrence of unexpected expenses.

Enterprise Risk Management Framework a1737050/Igor Ritonga 8

5 Quality Management
In the implementation of the project of financial information systems procurement, the
quality management system of the integrated information system is indispensable, it is,
therefore, necessary stages as below.

5.1 Quality Assurance Reviews

At this stage of project implementation, project manager reviewing the quality management
system and continually modified by: specifies the object's control, determines the unit that will
be measured (analysed), specify the optimal performance of the process of the work that has
been done, developing the idea for the root cause of the problem, minimize, optimize the use of
the tools required in performing a quality improvement, creating opportunities and opportunities
for quality improvement.

5.2 Quality Control

To guarantee the quality of the products that will be generated when the project
manager performs the planning quality, include the following:
a) Identify and communicate quality criteria to stakeholders.
b) Develop and communicate the quality of requirements with stakeholders.
c) Make a list of things that must be done in order to meet the quality of the project in the
form of a quality checklist.

6 Human Resource Management

According to Kathrin Connor (quoted from Schuller, 1990):
“Human resources are a part of the strategic planning process. It is a part of policy
development, planning and the extension line merger and acquisition processes. Little is done
in planning policy on the finalization stages of any deal”.

From Connor, Kathrin statement recognized that human resources is part of the strategic
planning process and became part of the development of the wisdom of the Organization, the
planning of the extension of line organization, merger and acquisition processes of the
organization.

6.1 Roles and Responsibilities

At this stage, the project manager identified qualifications and number of personnel required,
document the roles and responsibility of a person in the project and make the partnership liability
(in the form of reports, coordination or cooperation) the task is either formally or informally. The
qualifications and number of personnel required for this project consists of a one person project
manager, two systems analyst, database designer, one-person two people desktop Java
programmers, two Web developers, web designers, one person one person documentation, one
person report designer, one person consultant director, chief engineer of one person, one person,
one quality assurance technical support and six trainers. Roles and responsibilities of each of the
personnel or groups with reference to the form assignment project team (project team
assignment).

Enterprise Risk Management Framework a1737050/Igor Ritonga 9

6.2 Project Organisation Chart

The framework provides a basis for the understanding structure of project management based
on nine areas of knowledge management projects. Which stakeholders have goals or
expectations that poured in a project. A project manager will lead and manage the project.
Project management includes activities that correspond to project management knowledge areas
of the use of equipment, techniques, and methods related to achieving the goals expected by
stakeholders.

7 Communications and Change Management

In a project, there is an intense and communication required in such communication
possibility occurs the demand for change. To anticipate the things it needs to be arranged a
procedure.

7.1 Manage Communications

Activities include communication planning meetings and reporting. Preparations should be done
prior executed meetings, among others:
1. Distribute meeting agenda, no later than the day before. Discussion topics based on order
of importance, starting with the easy topics and each topic is given the allocation of time.
2. Distribute the materials of the meeting, the agenda and the time and location information.
3. Each Member of the project team responsible for preparing, attend and actively
participate in the meeting.
4. The leader of the meeting and the facilitator ensures meetings can run on the course and
efficiently.
5. The leader of the meeting appoints someone as a forward to make the meeting
documentation and distribute it appropriately.
6. At the time of the meeting to discuss the progress of the project, activities that will soon
be conducted and repeated discussion of control changes (change control review).

7.2 Manage The Changes

Procedures to control changes in this project (changes control procedure):
a) Any approved modifications or changes to the schedule and project costs should refer to
the next procedure.
b) Changes can come from any member of the team when needed, especially for changes
that will affect the schedule and workspace.
c) Agreement in the form of the request changes or changes request form (CRF) indicates
consent to changes in the schedule.

Enterprise Risk Management Framework a1737050/Igor Ritonga 10

 8 Risk Management
Project managers identify risks that may occur and plan strategies to address those
risks. The methods used to identify risk can use table 8.1 shows that strategies are possible to
anticipate the risks that may occur.

8.1 Risk Response and Control

No Risk Frequency Impact Strategies To Anticipate Risks
Interoperability with other Propose making IT Plan and carried out
systems to get business by the project team for ease of
1 Low High
information becomes more integration
difficult
Human resources have no Select human resources who meet the
2 competency in the field of Low High qualifications and have the desire to
accounting learn

Generally there is resistance Made training schedule that can

3 to the new system Low High support learning towards a new system
Too high gap between Offers an extended mentoring period
4 human resources and Low High for an additional fee
systems

There is no clear default The contract must be consulted to the

rates, especially for auditor
5 specialized software Low High
applications so that tends to
be a target of the auditors
The installation process Create a detail job description
takes a long time that
6 Low High
interfere with other
processes
The database used on the Perform database tuning on every
system cannot process period of entry
7 Medium High
transactions per second as
much as expected
Data lost due to the age of Prepare a backup online, providing
8 equipment or other factors High High backup hardware and SOP
Sick staff at critical Re-organized the team project that is
9 moments of the project Medium High by empowering human resources
intensity work already decreased

Network infrastructure does Perform a regular basis from of the

not function properly and infrastructure and monitoring data that
10 Medium High
the financial report of late already processed
due to data not yet entry

Enterprise Risk Management Framework a1737050/Igor Ritonga 11

9 Procurement Management
Project managers make the planning of procurement of goods that lay out the stuff that
is needed, the time an item is needed, and the process of procurement. Procedure for the
procurement of goods on this project starting from the process of filing a request for a proposal
and request for quote to the vendor. Then the vendor sends a letter of the offer price. Further
discussion was held to determine the vendors who offer goods with good quality and low price.
The selected vendor will be called to take a test the feasibility of the vendor. If judged worthy
then made news event booking of the goods in accordance with the specifications of the goods
and the time as listed on the contract.

10 Appendix A – Glossary
Term/Acronym Meaning
Entity Relationship Diagram An entity-relationship model is usually the result of systematic
(ERD) analysis to define and describe what is important to processes
in an area of a business. It does not define the business
processes; it only presents a business data schema in graphical
form. It is usually drawn in a graphical form as boxes (entities)
that are connected by lines (relationships) which express the
associations and dependencies between entities. An ER model
can also be expressed in a verbal form, for example, one
building may be divided into zero or more apartments, but one
apartment can only be located in one building.

Software Design Description A software design description (a.k.a. software design

(SDD) document or SDD) is a written description of
a software product, that a software designer writes in order to
give a software development team overall guidance to the
architecture of the software project. An SDD usually
accompanies an architecture diagram with pointers to detailed
feature specifications of smaller pieces of the design.
Practically, the description is required to coordinate a large
team under a single vision, needs to be a stable reference, and
outline all parts of the software and how they will work.
Software Requirement A software requirements specification (SRS) is a description of
Specification (SRS) a software system to be developed. It lays
out functional and non-functional requirements, and may
include a set of use cases that describe user interactions that
the software must provide. Software requirements
specification establishes the basis for an agreement between
customers and contractors or suppliers (in the market-driven
project, these roles may be played by the marketing and
development divisions) on what the software product is to do
as well as what it is not expected to do.

Enterprise Risk Management Framework a1737050/Igor Ritonga 12