IT Project Management: ERP System Implementation for Retail Business

This project management assignment details the implementation of an ERP system for a retail business. It begins with a business case outlining the project's objectives, which include developing and installing the ERP system to improve business functions. The assignment covers stakeholder strategy, including identification and analysis of key stakeholders. It also presents a comprehensive communication management plan to ensure effective information transfer. A project charter defines project information, objectives, deliverables, milestones, constraints, and assumptions. The document further includes a scope statement, work breakdown structure (WBS), WBS dictionary, risk registry, cost management plan, RACI matrix, milestones list, project schedule, project dashboard, quality checklist, human resource management plan, and lessons learned. The project aims to streamline retail operations through efficient ERP system integration, enhancing functional analysis and overall business performance.

Running head: IT PROJECT MANAGEMENT
IT Project Management
Implementation of the ERP system
Name of the Student:
Student ID:
Name of the University:
Author’s note:

1IT PROJECT MANAGEMENT
Table of Contents
1. Business Case..............................................................................................................................3
1.1 Business Description.............................................................................................................3
1.2 Project Description................................................................................................................3
2. Stakeholder Strategy....................................................................................................................4
2.1 Identification of Stakeholders................................................................................................4
2.2 Key Stakeholders...................................................................................................................4
2.3 Stakeholder Analysis.............................................................................................................5
3. Communication Management Plan..............................................................................................6
4. Project Charter.............................................................................................................................8
4.1 Project Information................................................................................................................8
4.2 Objectives of the Project........................................................................................................8
4.3 Key Deliverables of the Project.............................................................................................9
4.4 Milestones of the Project.....................................................................................................10
4.5 Constraints/Limitation.........................................................................................................11
4.6 Assumptions........................................................................................................................11
5. Scope Statement.........................................................................................................................12
6. Work Breakdown Structure.......................................................................................................14
7. WBS Dictionary.........................................................................................................................14
8. Risk Registry.............................................................................................................................18

2IT PROJECT MANAGEMENT
9. Cost Management Plan..............................................................................................................19
10. RACI Matrix............................................................................................................................19
11. Milestones List.........................................................................................................................20
12. Project Schedule......................................................................................................................20
13. Project Dashboard....................................................................................................................23
14. Quality Checklist.....................................................................................................................24
15. Human Resource Management Plan........................................................................................24
16. Lessons learned........................................................................................................................25
Bibliography..................................................................................................................................26

3IT PROJECT MANAGEMENT
1. Business Case
1.1 Business Description
The project of ERP System Development is implied for a retail business organization and
the management of the system development along with the implementation of the information
system. The ERP system development has formed the integration of the functions for forming
the modification of the functions and deployment of the functions for the organization (Nanney
et al., 2016). The implication of the ERP system would provide the retail industry with the
advent of utilising the development of the functions and carrying out of the activities for
successful system development. The analysis of the project advent development would allow the
users with the development of improved functional analysis and development. The modification
of the functions would allow the formation of the support and development for the users. The
business functions of the retail industry would allow the formation of the improved functional
analysis for increasing their efficiency and formation of the functions.
1.2 Project Description
The project comprises of developing an improved breakdown of activities for resulting
the ERP system for the retail organization. The analysis of the effective and improved project
functions has allowed the formation of the improved functional analysis (Sadgrove, 2016). The
project would involve the use of project management and system development methods for
implying the improved functional development. The alignment of the project objectives would
allow the development of the project functions. The project of implementing ERP system has
allowed the formation of the functions of the project development. The project comprises of

4IT PROJECT MANAGEMENT
developing and installing the system so that the retail organization can manage the flow of
functions and improved their functions efficiently.
2. Stakeholder Strategy
2.1 Identification of Stakeholders
The project structure comprises of developing the improved functions and implying the
improved functional analysis. The deployment of the activities would allow the users for
implementing the successful development of the functions (Fageha & Aibinu, 2014). The
stakeholders of the project can be divided into three layers namely governance, managerial, and
functional. The project of ERP system implementation would allow the users for the
modification of the functions and imply the successful development of the functions. The project
governance stakeholder comprises of the client organization, users (staffs and customers of retail
organization), and board members of the project team. The project managerial stakeholder
comprises of managers, head of departments, and team leaders of the project. The project
functional stakeholder comprises of analyst, documenter, planner, designer, engineer, database
developer, programmer, and tester.
2.2 Key Stakeholders
The key stakeholders of the project comprise of the end user and client organization or
investor who have invested the money in the project (Collins, Parrish & Gibson Jr, 2017). The
analysis of the project integration would allow the users for forming improved functional
analysis. The project owners would form the development of the improved functions. The key
stakeholders of the project would be responsible for the successful project completion. The

5IT PROJECT MANAGEMENT
satisfaction of the key stakeholders of the project would be a major factor for the project success.
The unhappy project key stakeholders would result in forming the issues and problems for the
project functions.
2.3 Stakeholder Analysis
The stakeholder analysis is the method of analysing the project’s stakeholder and deploys
the improved functions for forming the project success. The roles and responsibilities of the
project stakeholders are given below,
Name Role Power
(H/L)
Interest
(H/L)
Responsibilities
Katherine
Jones
Analyst L L Analyzing the basic project requirements,
Feasibility Analysis, Client's requirement is
listed
Amanda Lee Documenter L L Development of Project Initiation Documents,
Project Charter is made, Submission of the PID,
Final documents are made, Documents are
Submitted
<<name of
the student>>
Project
Manager
H H Approval of the project, Reviewed and Sign off,
Project is Closed
John Wick Planner L L Selecting the model for plan development,
Outline of the plan is developed, Plan is
reviewed, Completed Plan is made
Stuart Simon Designer L H Design Platform is selected, Interface Design is
formed, Components are listed, Design is
Approved
Rey Dawn Engineer H L User Interface is formed, Complete System is
developed, ERP system is implemented
Dorothy
Miens
Database
Developer
H L Database is developed, Database Integration is
done

6IT PROJECT MANAGEMENT
Christine
Jones
Programmer H L Functions are Aligned, Programming of the
functions are done
Meg Konini Tester L H Prototype Testing, Simulation Testing, White
Box Testing, Black Box Testing
3. Communication Management Plan
The communication management plan is formed for ensuring that the project is carried on
successfully and there are no issues in conveying the information to other team members. The
project of implementing the ERP system would comprise of forming the improved functions and
implication of the integrated data analysis (Potts & Ankrah, 2014). The communication
management would allow the users for developing the improved project information transfer and
align the development of the functions. The main reason behind making the communication plan
is that it would allow the development of the process of transferring the information to the
required person so that the probability of occurrence of the errors are minimized. The
communication management plan can be formed as explained below,
Plan: The first step of developing the communication management plan is the formation
of an effective plan. It is the initiation phase of the communication management plan as all the
analysis of the requirements and the development of the improved functional analysis was
employed for the formation of the functions. The plan development would allow the formation of
the successive communication management process.
Management: The management is the second step of the communication management
plan development as it would allow the users for managing the methods of the communication
and imply them for the improved communication process. The communication process is implied

7IT PROJECT MANAGEMENT
for developing the improved functional analysis. The deployment of the communication
management plan should be managed with the help of this process.
Control: The establishment of the control is a major factor for the expansion of the
functions and arrangement of the controlled communication management plan. The
establishment of the control factor for the project would allow the users for the development of
the communication. The control factor would allow the users for the management of the control
of information transfer. The transfer would allow the management of the improved specific
system alignment.
Communication
type
Communication
Objective
Medium Frequency Audience Owner Deliverable
Kick off
Meeting
Initiation of the
project, Stating
project goals and
objectives,
Assigning work
to team members
Face to
Face
Once All
stakeholders
including
Project
team
Members
Project
Manager
Project
Resource
Allocation
Working
Schedule
Midway Project
Status Meeting
Reporting the
project and its
status after the
scheduled half
time completion
of 50% project
completion
Conferenc
e Call
Once Project
Sponsor
Project
Manager
Team Meetings Team meetings
for the issues
and problems of
the project for
sorting them out
Face to
face
As
Required
Project
Team
Members
Project
Manager
Agendas,
Solution to
the project
issues
Status Reports Status reports
are made for
ensuring that the
project would be
completed in the
estimated time
and schedule.
Reports
and Emails
Weekly PMO Project
Manager
Contingency
Planning
4. Project Charter

8IT PROJECT MANAGEMENT
4.1 Project Information
Project Name ERP System Development
Project Manager <<name of the student>>
Project Type System Development Project
Client/Business Retail Organization
Start Date Duration End Date Budget
Monday 15th January
2018
80 days Friday 4th May 2018 $ 50,000.00
4.2 Objectives of the Project
The project of ERP System Development is a system development project that comprises
of developing a project of the implementation method. The alignment of the project objectives
would allow the development of the project functions. The analysis of the project management
method has allowed the formation of the improved methods. The objectives of the project are,
Development of the Project Plan: The initial objective of the project is to develop
project plan that would help the project team to develop and install the ERP system. The project
plan would comprise of the development of the improved process development and it would
allow the formation of the functions. The development of the project plan is implied for ensuring
that the management of the improved functional functions.
Development and Installation of ERP System: The first and the foremost objective of
the project are to develop an ERP system and implement it for the retail organization. The

9IT PROJECT MANAGEMENT
analysis of the effective and improved project functions has helped in the formation of the
enhanced functional development.
Improvement of the Functions: The functions of the retail organization would be
largely improved with the help of the implemented ERP system. The alignment of the project
activities would allow the deployment of the improved functional analysis. The project has
included the use of project management and system development methods for implying the
improved functional development.
4.3 Key Deliverables of the Project
The project of ERP system development comprises of the development of an ERP system
and implementing the system for the retail organization. The key deliverables for the project are
project charter, project plan, and interface design, database of the system, complete system, and
final documents. The charter documentation is the initial project deliverable that would comprise
of the development of the project documentation. The charter document comprises of the initial
project assumptions, limitations, expected start date and finish date, estimated budget, and
limitations. The complete plan is developed by selecting a proper project plan development
method that would involve the management of the activities listed in a chronological way. The
interface design is formed for the alignment of the system functions so that the users can manage
the project objectives. The complete system development would be aligned for the analysis of
the functions and it would align the management of the functions. The final documents are listed
so that the project is completed successful and compliance development.
The key deliverables along with schedule and duration for the project are listed in the
table below,

10IT PROJECT MANAGEMENT
WBS Task Name Duration Start Finish
1.3 Project Charter is made 4 days Wed 1/24/18 Mon 1/29/18
2.5 Completed Plan is made 5 days Thu 2/15/18 Wed 2/21/18
3.3 Interface Design is formed 6 days Wed 2/28/18 Wed 3/7/18
4.2 Database is developed 5 days Mon 3/19/18 Fri 3/23/18
4.6 Complete System is developed 5 days Fri 4/13/18 Thu 4/19/18
6.1 Final documents are made 4 days Wed 4/25/18 Mon 4/30/18
4.4 Milestones of the Project
The milestones of the project of ERP System Development are listed in the table below,
WBS Task Name Duration Start Finish
M1 Approval of the project 1 day Wed 1/31/18 Wed 1/31/18
M2 Completed Plan is made 5 days Thu 2/15/18 Wed 2/21/18
M3 Design is Approved 1 day Mon 3/12/18 Mon 3/12/18
M4 ERP system is implemented 3 days Fri 4/20/18 Tue 4/24/18
M5 Project is Closed 1 day Fri 5/4/18 Fri 5/4/18
4.5 Constraints/Limitation

11IT PROJECT MANAGEMENT
The project is constrained in terms of the time, budget, and function and the overall
completion of the project is limited to the service alignment. The constraints/limitations of the
project of ERP system development are,
Time Bounded: The project is time bounded and it should be completed within the
period of 80 days
Fixed Budget: The project should be completed in the estimated budget of $ 50,000.00
and the program would be completed within the budget
Function: The limitation of the functions of the ERP system is another major factor for
the deployment of the improved functions
4.6 Assumptions
The assumptions of the project of ERP system development are given below,
Appropriate Resources: Resources were available for the expansion of the project plan.
The project resources would be easily distributable and the project would be completed in the
estimated budget. The alignment of the resources would help in forming the successful
completion of the project.
Harmony among Co-workers: Team members would be comfortable for working with
each other and there would be no scope for the conflicts among the project team members. The
team members would provide helping hand to other members and the development of the
activities would help in forming improved functions.

12IT PROJECT MANAGEMENT
Data Compatibility: The existing data of the retail organization would be transferred to
the new ERP system development. The compatible data can be easily transferred to the new
database and it would help in easing the data backup in the new system.
5. Scope Statement
Project Name: ERP System Development
Prepared by: <<name of the student>> Date: 5th January 2018
Project Justification: The ERP system modification of the functions would allow the formation
of the support and development for the users. The business functions of the retail industry would
allow the formation of the improved functional analysis for increasing their efficiency and
formation of the functions.
Project Description: The project comprises of developing the improved analysis of activities for
forming the ERP system for the retail organization. The alignment of the project activities for
implementing ERP system will allow the integration of the functions of the project development.
Project Deliverables: The key deliverables for the project are project charter, project plan, and
interface design, database of the system, complete system, and final documents.
Charter Documents The charter document comprises of the initial project assumptions,
limitations, expected start date and finish date, estimated budget, and limitations.
Complete Plan The complete plan is developed by selecting a proper project plan development
method that would involve the management of the activities listed in a chronological way.
Interface Design The interface design is formed for the alignment of the system functions so
that the users can manage the project objectives.
Complete System The complete system development would be aligned for the analysis of the

13IT PROJECT MANAGEMENT
functions and it would align the management of the functions.
Final Project Document The final documents are listed so that the project is completed
successful and compliance development.
Out of Scope Items: The out of scope items include the Transportation cost, Change
Management, and Scope Management plan.
Project Objectives: The objectives of the ERP system development project are,
 Development of the Project Plan
 Development and Installation of ERP System
 Improvement of the Functions
Constraints: The constraints of the project of ERP system development are
The project is time bounded and it should be completed within the period of 80 days
The project should be completed in the estimated budget of $ 50,000.00 and the program would
be completed within the budget
The limitation of the functions of the ERP system is another major factor for the deployment of
the improved functions
Assumptions: The assumptions of the project of ERP system development are
Resources would be available for the development of the project plan
Team members would be comfortable for working with each other and there would be no scope
for the conflicts among the project team members
The existing data of the retail organization would be transferred to the new ERP system
development
6. Work Breakdown Structure

14IT PROJECT MANAGEMENT
The work breakdown structure for the ERP system development project is given below,
ERP System
Development
Project Initialization
Analyzing the basic
project requirements
Development of
Project Initiation
Documents
Project Charter is
made
Submission of the
PID
Approval of the
project
Project Planning
Selecting the model
for plan development
Feasibility Analysis
Outline of the plan is
developed
Plan is reviewed
Completed Plan is
made
System Designing
Design Platform is
selected
Client's requirement
is listed
Interface Design is
formed
Components are
listed
Design is Approved
System Development
User Interface is
formed
Database is
developed
Database Integration
is done
Functions are
Aligned
Programming of the
functions are done
Complete System is
developed
ERP system is
implemented
System Testing
Prototype Testing
Simulation Testing
White Box Testing
Black Box Testing
Closure and
Documentation
Final documents are
made
Documents are
Submitted
Reviewed and Sign
off
Project is Closed
Figure 1: Project Work Breakdown Structure
(Source: Created by the Author)
7. WBS Dictionary
Project Title: ERP System Development Date Prepared: 2nd January 2018
Work Package name WBS ID
Project Initialization 1
Milestone: M1-Approval of the project Due Date: 31st January 2018
ID Activity Resource Labour Material Total
CostHour
s
Rate Total Unit
s
Cost Total
1.1 Analyzing the basic
project requirements
Analyst 24 $50/hr $1,200 $1200
1.2 Development of
Project Initiation
Documents
Documenter 32 $55/hr $1,760 $1760
1.3 Project Charter is Documenter 32 $55/hr $1760 $1760

15IT PROJECT MANAGEMENT
made
1.4 Submission of the
PID
Documenter 8 $55/hr $440 $440
1.5 Approval of the
project
Project
Manager
8 $100/hr $800 $800
Project Title: ERP System Development Date Prepared: 2nd January 2018
Work Package name WBS ID
Project planning 2
Milestone: M2-Complete Plan is made Due Date: 21st February, 2018
ID Activity Resourc
e
Labour Material Total
Cost
Hours Rate Total Units Cost Total
2.1 Selecting
the model
for plan
development
Planner 16 $60/hr $960 $960
2.2 Feasibility
Analysis
Analyst 24 $50/hr $1200 $1200
2.3 Outline of
the plan is
developed
Planner 24 $60/hr $1440 $1440
2.4 Plan is
reviewed
Planner 16 $60/hr $960 $960
2.5 Completed
Plan is made
Planner 40 $60/hr $2400 $2400
Project Title: ERP System Development Date Prepared: 2nd January 2018
Work Package name WBS ID
System Designing 3
Milestone: M3-Design is approved Due Date: 12th March 2018
ID Activity Resourc
e
Labour Material Total
Cost
Hours Rate Total Units Cost Total
3.1 Design
Platform is
Designer,
Designing
16 $70/hr $1120 1 $330 $1450

16IT PROJECT MANAGEMENT
selected Tools[1]
3.2 Client's
requirement
is listed
Analyst 16 $50/hr $800 $800
3.3 Interface
Design is
formed
Designer 48 $70/hr $1120 $3360
3.4 Components
are listed
Designer 48 $70/hr $3360 $1120
3.5 Design is
Approved
Designer 8 $70/hr $560 $560
Project Title: ERP System Development Date Prepared: 2nd January 2018
Work Package name WBS ID
System Development 4
Milestone: M4- ERP system is implemented Due Date: 24th April, 2018
ID Activity Resource Labour Material Total
Cost
Hours Rate Total Units Cost Total
4.1 User
Interface is
formed
Engineer 32 $90/hr $2880 $2,880
4.2 Database is
developed
Database
Developer,
Database
Components[1]
40 $80/hr 3200 1 $290 $3,490
4.3 Database
Integration is
done
Database
Developer
16 $80/hr $1280 $1,280
4.4 Functions are
Aligned
Programmer 16 $85/hr $1,360
4.5 Programmin
g of the
functions are
done
Programmer,
Programming
Tools[1]
64 $85/hr $5440 1 $420 $5,860
4.6 Complete
System is
developed
Engineer 40 $90/hr $3600 $3,600
4.7 ERP system
is
Engineer 24 $90/hr $2160 $2,160

17IT PROJECT MANAGEMENT
implemented
Project Title: ERP System Development Date Prepared: 2nd January 2018
Work Package name WBS ID
System Testing 5
Milestone: NA Due Date: 12th April, 2018
ID Activity Resourc
e
Labour Material Total
Cost
Hours Rate Total Units Cost Total
5.1 Prototype
Testing
Tester,
Testing
Tools[1]
16 $65/hr $1040 $100 $1,140
5.2 Simulation
Testing
Tester,
Testing
Tools[1]
16 $65/hr $1040 $100 $1,140
5.3 White Box
Testing
Tester,
Testing
Tools[1]
16 $65/hr $1040 $100 $1,140
5.4 Black Box
Testing
Tester,
Testing
Tools[1]
16 $65/hr $1040 $100 $1,140
Project Title: ERP System Development Date Prepared: 2nd January 2018
Work Package name WBS ID
Closure and Documentation 6
Milestone: M5-Project is closed Due Date: 4th May, 2018
ID Activity Resource Labour Material Total
Cost
Hours Rate Total Units Cost Total
6.1 Final
documents
are made
Documenter 32 $55/hr $1,760 $1,760
6.2 Documents
are
Submitted
Documenter 8 $55/hr $440 $440
6.3 Reviewed Project 16 $100/hr $1,600 $1,600

18IT PROJECT MANAGEMENT
and Sign
off
Manager
6.4 Project is
Closed
Project
Manager
8 $100/hr $800 $800
8. Risk Registry
Risk Register Template
Project Name: ERP System Development
Dated: 2nd January 2018
Risk Name: System failure
Category: Technical
Impact: Catastrophic (5)
Probability: Seldom (3)
Rating: Very High (15)
Mitigation Strategy: Proper Testing Methods should be applied
Risk Name: Cost Overrun
Category: Financial
Impact: Serious (3)
Probability: Occasional (4)
Rating: High (12)
Mitigation Strategy: Provisional Budget Allocation must be done or Investors should be contacted
Risk Name: Delay in operation
Category: Performance
Impact: Minor (2)
Probability: Seldom (3)
Rating: Medium (6)
Mitigation Strategy: Contingency Planning should be used
9. Cost Management Plan
The Cost Management Plan is developed for estimating a budget for the project by the
help of the resource cost estimation. The following table would show the estimated budget,
Cost Budget Estimation

19IT PROJECT MANAGEMENT
Resource Name
Resource
Type Hours/Units Rate Cost
Analyst Human 64 $50.00 $3,200.00
Documenter Human 112 $55.00 $6,160.00
Project Manager Human 32 $100.00 $3,200.00
Planner Human 96 $60.00 $5,760.00
Designer Human 88 $70.00 $6,160.00
Engineer Human 96 $90.00 $8,640.00
Database Developer Human 56 $80.00 $4,480.00
Programmer Human 80 $85.00 $6,800.00
Tester Human 64 $65.00 $4,160.00
Testing Tools Material 4 $100.00 $400.00
Designing Tools Material 1 $330.00 $330.00
Database Components Material 1 $290.00 $290.00
Programming Tools Material 1 $420.00 $420.00
Total Budget $50,000.00
10. RACI Matrix
Project Phase
Stakeholder
Initialization
Phase
Planning
Phase
Designing
Phase
Developmen
t Phase
Testing
Phase
Closure
Phase
Analyst A A
Documenter R A
Project Manager C C C R
Planner I R I C
Designer R I
Engineer I A A C I
Database
Developer
R I
Programmer C A
Tester R

20IT PROJECT MANAGEMENT
11. Milestones List
WBS Task Name Duration Start Finish
M1 Approval of the project 1 day Wed 1/31/18 Wed 1/31/18
M2 Completed Plan is made 5 days Thu 2/15/18 Wed 2/21/18
M3 Design is Approved 1 day Mon 3/12/18 Mon 3/12/18
M4 ERP system is implemented 3 days Fri 4/20/18 Tue 4/24/18
M5 Project is Closed 1 day Fri 5/4/18 Fri 5/4/18
12. Project Schedule
The project of ERP system development is implied for forming the deployment of the
improved functional analysis. The
WBS Task Name Duratio
n Start Finish Predecessor
s Resource Names
0 ERP System
Development 80 days Mon
1/15/18
Fri
5/4/18
1 Project Initialization 13 days Mon
1/15/18
Wed
1/31/18
1.1 Analyzing the basic
project requirements 3 days Mon
1/15/18
Wed
1/17/18 Analyst
1.2 Development of Project
Initiation Documents 4 days Thu
1/18/18
Tue
1/23/18 2 Documenter
1.3 Project Charter is made 4 days Wed
1/24/18
Mon
1/29/18 3 Documenter
1.4 Submission of the PID 1 day Tue
1/30/18
Tue
1/30/18 4 Documenter
1.5 Approval of the project 1 day Wed Wed 5 Project Manager

21IT PROJECT MANAGEMENT
1/31/18 1/31/18
2 Project Planning 15 days Thu
2/1/18
Wed
2/21/18
2.1 Selecting the model for
plan development 2 days Thu
2/1/18
Fri
2/2/18 6 Planner
2.2 Feasibility Analysis 3 days Mon
2/5/18
Wed
2/7/18 8 Analyst
2.3 Outline of the plan is
developed 3 days Thu
2/8/18
Mon
2/12/18 9 Planner
2.4 Plan is reviewed 2 days Tue
2/13/18
Wed
2/14/18 10 Planner
2.5 Completed Plan is made 5 days Thu
2/15/18
Wed
2/21/18 11 Planner
3 System Designing 13 days Thu
2/22/18
Mon
3/12/18
3.1 Design Platform is
selected 2 days Thu
2/22/18
Fri
2/23/18 12 Designer,
Designing Tools[1]
3.2 Client's requirement is
listed 2 days Mon
2/26/18
Tue
2/27/18 14 Analyst
3.3 Interface Design is formed 6 days Wed
2/28/18
Wed
3/7/18 15 Designer
3.4 Components are listed 2 days Thu
3/8/18
Fri
3/9/18 16 Designer
3.5 Design is Approved 1 day Mon
3/12/18
Mon
3/12/18 17 Designer
4 System Development 31 days Tue
3/13/18
Tue
4/24/18
4.1 User Interface is formed 4 days Tue
3/13/18
Fri
3/16/18 18 Engineer
4.2 Database is developed 5 days Mon
3/19/18
Fri
3/23/18
20 Database
Developer,
Database

22IT PROJECT MANAGEMENT
Components[1]
4.3 Database Integration is
done 2 days Mon
3/26/18
Tue
3/27/18 21 Database Developer
4.4 Functions are Aligned 2 days Wed
3/28/18
Thu
3/29/18 22 Programmer
4.5 Programming of the
functions are done 8 days Fri
3/30/18
Tue
4/10/18 23 Programmer,
Programming Tools[1]
4.6 Complete System is
developed 5 days Fri
4/13/18
Thu
4/19/18 24, 30, 31 Engineer
4.7 ERP system is
implemented 3 days Fri
4/20/18
Tue
4/24/18 25 Engineer
5 System Testing 26 days Thu
3/8/18
Thu
4/12/18
5.1 Prototype Testing 2 days Mon
3/19/18
Tue
3/20/18 20 Tester,
Testing Tools[1]
5.2 Simulation Testing 2 days Thu
3/8/18
Fri
3/9/18 16 Tester,
Testing Tools[1]
5.3 White Box Testing 2 days Wed
3/28/18
Thu
3/29/18 22 Tester,
Testing Tools[1]
5.4 Black Box Testing 2 days Wed
4/11/18
Thu
4/12/18 24 Tester,
Testing Tools[1]
6 Closure and
Documentation 8 days Wed
4/25/18
Fri
5/4/18
6.1 Final documents are made 4 days Wed
4/25/18
Mon
4/30/18 26 Documenter
6.2 Documents are Submitted 1 day Tue
5/1/18
Tue
5/1/18 33 Documenter
6.3 Reviewed and Sign off 2 days Wed
5/2/18
Thu
5/3/18 34 Project Manager
6.4 Project is Closed 1 day Fri 5/4/18 Fri
5/4/18 35 Project Manager

23IT PROJECT MANAGEMENT
13. Project Dashboard
Figure: Project Dashboard
(Source: Created by author in Ms-Excel)
14. Quality Checklist
Project Name ERP System Development
Document Quality Checklist Document
Checklist Item Yes? No? Date

24IT PROJECT MANAGEMENT
Feasible Plan  
Appropriate Design  
Compatible Database  
Expected Testing Results  
Completion of final documents  
15. Human Resource Management Plan
The Human Resource Management Plan is developed for aligning of the improved
management of the resource management for the stakeholders and the deployment of the
improved functional functions (Brewster & Hegewisch, 2017). The human resource management
plan can be implied by,
Step 1: Identification of the human resource gap
Step 2: Forecasting of the human needs
Step 3: Forecasting of supply for human resource
Step 4: Action Plan for bridging the gaps
Step 5: Turning the shortage of human resource to surplus human resource
Step 6: Controlling the expenditure of the human resource via scheduling
16. Lessons learned
The study would help in developing and understanding of the project management
methods and the consideration of the effective project integration management. The implication

25IT PROJECT MANAGEMENT
of the project management would provide the ease of the system development and installation.
The integration of the specific model would allow the users for the formation of the improved
functional development. The project would indulge in the formation of the specific project
deployment scenario.

26IT PROJECT MANAGEMENT
Bibliography
Armstrong, M., & Taylor, S. (2014). Armstrong's handbook of human resource management
practice. Kogan Page Publishers.
BinDhim, N. F., Hawkey, A., & Trevena, L. (2015). A systematic review of quality assessment
methods for smartphone health apps. Telemedicine and e-Health, 21(2), 97-104.
Brewster, C., & Hegewisch, A. (Eds.). (2017). Policy and Practice in European Human
Resource Management: The Price Waterhouse Cranfield Survey. Taylor & Francis.
Brioso, X. (2015). Integrating ISO 21500 guidance on project management, lean construction
and PMBOK. Procedia Engineering, 123, 76-84.
Carroll, A., & Buchholtz, A. (2014). Business and society: Ethics, sustainability, and stakeholder
management. Nelson Education.
Collins, W., Parrish, K., & Gibson Jr, G. E. (2017). Development of a Project Scope Definition
and Assessment Tool for Small Industrial Construction Projects. Journal of Management
in Engineering, 33(4), 04017015.
Cooper, R. (2017). Supply chain development for the lean enterprise: interorganizational cost
management. Routledge.
Crawford, J. K. (2014). Project management maturity model. CRC Press.
Dicks, E., Molenaar, K. R., & Gibson Jr, G. E. (2017). Scope Definition of Air Force Design and
Construction Projects. Journal of Management in Engineering, 33(5), 04017028.

27IT PROJECT MANAGEMENT
District, C. P. U., Rights, W., & Supply, W. (2015). MokeWISE Program Scope of Work:
Project 8b: Rehabilitation of Transmission Main.
Eskerod, P., & Vaagaasar, A. L. (2014). Stakeholder management strategies and practices during
a project course. Project Management Journal, 45(5), 71-85.
Fageha, M. K., & Aibinu, A. A. (2014). A Procedure for involving stakeholders when measuring
project scope definition completeness at pre-project planning stage. In AIPM NATIONAL
2014 CONFERENCE PROCEEDINGS (pp. 1-8).
Garcia‐Castro, R., & Francoeur, C. (2016). When more is not better: Complementarities, costs
and contingencies in stakeholder management. Strategic Management Journal, 37(2),
406-424.
Genova, J., Olson, C. A., & Bender, J. (2017). Using the Communication AssessmenT Checklist
in Health to Assess the Communication Quality of Web Based Resources for Prostate
Cancer. Health Literacy: Breakthroughs in Research and Practice: Breakthroughs in
Research and Practice, 24.
Gijo, E. V., & Scaria, J. (2014). Process improvement through Six Sigma with Beta correction: a
case study of manufacturing company. The International Journal of Advanced
Manufacturing Technology, 71(1-4), 717-730.
Gomez, G., & Tejedor, G. (2015). Monitoring of social networks and their links with the external
communication plan of Cofrentes NPP. Nuclear Espana (1996), 366, 71-73.

28IT PROJECT MANAGEMENT
Hansen, S. M., Hetland, M. L., Pedersen, J., Østergaard, M., Rubak, T. S., & Bjorner, J. B.
(2017). Work ability in rheumatoid arthritis patients: a register study on the prospective
risk of exclusion and probability of returning to work. Rheumatology, kex064.
Hong, C. S., Siegel, A. L., & Ferris, T. G. (2014). Caring for high-need, high-cost patients: what
makes for a successful care management program. Issue Brief (Commonw Fund), 19(1),
9.
Kostkova, P., Garbin, S., Moser, J., & Pan, W. (2014, April). Integration and visualization public
health dashboard: the medi+ board pilot project. In Proceedings of the 23rd International
Conference on World Wide Web (pp. 657-662). ACM.
Lipman, B., & Ashlock, M. Z. (2015). Engineering and Implementing an Executive-Level
Communication Plan in a Global Professional Environment: A Case Study. Journal of
Media Critiques [JMC], 1(2).
Mok, K. Y., Shen, G. Q., & Yang, J. (2015). Stakeholder management studies in mega
construction projects: A review and future directions. International Journal of Project
Management, 33(2), 446-457.
Munch, T. N., Rasmussen, M. L. H., Wohlfahrt, J., Juhler, M., & Melbye, M. (2014). Risk
factors for congenital hydrocephalus: a nationwide, register-based, cohort study. J Neurol
Neurosurg Psychiatry, 85(11), 1253-1259.
Nanney, M. S., Nelson, T. F., Kubik, M. Y., & MacLehose, R. (2016). Project ScOPE: School
Obesity-related Policy Evaluation.