Project Management Plan: ERP Information System Development for AAA Law Firm

This project management plan outlines the development of an ERP information system for AAA law firm. It includes scope, objectives, benefits, methodology, stakeholders, risks, and delivery planning.

IFN700: Case Study Task (CST) – sem2 2018
Project Management Plan: ERP information system development for AAA law firm
Name of the Student:
Student ID:
Tutor Name:
IFN700: Case Study Task (CST)
0

IFN700: Case Study Task (CST) – sem2 2018
Revision history
Existing Content Changed Content
PBS structure Object Structure
(12/10/18)
Network Diagram Node Diagram
(15/11/18)
Operation Model Improved Functional Objectives
(25/11/18)
1

IFN700: Case Study Task (CST) – sem2 2018
Table of Contents
1. Business driver.............................................................................................................................3
2. Project objectives.........................................................................................................................3
3. Business benefits.........................................................................................................................4
4. Defining the scope.......................................................................................................................4
4.1 Scope statement.....................................................................................................................5
4.2 Product breakdown structure (PBS) and a Product flow diagram (PFD)..............................6
4.3 Work breakdown structure (WBS)........................................................................................7
4.4 Project Task Table.................................................................................................................7
4.5 Network diagram and critical path........................................................................................9
5. Justify the chosen methodology.................................................................................................10
6. Key stakeholders........................................................................................................................11
7. Outline solution.........................................................................................................................12
8. Key risks....................................................................................................................................13
9. Delivery and release planning...................................................................................................13
9.1 Gantt chart...........................................................................................................................13
10. Project control..........................................................................................................................14
11. Project costs.............................................................................................................................15
Bibliography..................................................................................................................................17
2

IFN700: Case Study Task (CST) – sem2 2018
1. Business driver
The law firm would require the improvement of their operations and management of the
functional development for ensuring the completion of the activities. The business driver would
be constructed with the consideration of the factors and deployment of the improved functional
development. The management of the activities had been helpful for aligning with the operation
management for the law firms and developing proper management of the information
development for the organization. The organization needs the new system with the compact
alignment management for the successful introduction of the factors. The cohesive analysis had
been aligned with the simplification of the information gathering and the analysis of the factors.
The following assignment had been developed with the development of the factors and aligning
the project management information development.
2. Project objectives
The following are the objectives of the project of ERP information system development
for AAA law firm,
 To develop an ERP based information system for improving the operations of the
activity development
 To ensure the complete activity management and implying the successful
completion of the project
 To imply the management of the activities and listing the improvement of the
activities and aligning the significant development
 To complete the project in the estimated time and budget for successfully
completing the assignment
3

IFN700: Case Study Task (CST) – sem2 2018
3. Business benefits
The implication of the project of ERP information system development for AAA law
firm would result in managing and improving the operations for developing the successful
integration and management. The analysis would be successfully deployed with the utilization of
the factors and improving the management process. The benefits of implying the project are
explained below,
Specific – ERP information system would help in managing the records of the law firm,
identification of the legal services, skills and qualification testimonials, and proposal
documentation.
Measurable – ERP information system would help in managing the transaction logs and the
access to information processing. Registering development would be implied with the formation
and listing the coherent management of the factors.
Assignable – ERP information system would help in improving the complete management of the
activities and development of successive information
Realistic – The operations of the law firms would be increased with the management of the
successful development
Time-related – The time related activities would be implied with the successful integration and
development of the functional management
4. Defining the scope
4

IFN700: Case Study Task (CST) – sem2 2018
The project of ERP information system development for AAA law firm scopes for
developing an ERP information system for taking care of the improved functional analysis. The
project scope can be divided into in scope and out of scope. The in scope items of the project are
project plan development, scope management plan, design development, information
management, system development, and closure documentation.
4.1 Scope statement
The following is the scope statement for the project of ERP information system
development for AAA law firm,
‘The project scopes for developing an ERP based information system for AAA law firm
with the concept for improving the management of the successful information management and
improving functions of documentation and processing for the law firm.’
5

IFN700: Case Study Task (CST) – sem2 2018
4.2 Product breakdown structure (PBS) and a Product flow diagram (PFD)
The product breakdown structure (PBS) and Product Flow Diagram (PFD) for the project of ERP information system development for AAA law firm is shown below,
ERP information system
development for AAA law
firm
Initialization
Analysis of requirements
Charter Documentation
PID documentation
Team members
appointment
Kick off
Planning phase
Schedule Estimation
Resource Estimation
Finance Management
Quality Management
Risk Management
Acceptance Criteria
Communication Process
Procurement
management
Plan Approval
Execution phase
Business Needs
Identification
ERP Vendor Selection
Customization of
functions
Migration of data
Infrastructure checking
Operation Development
Change management
Technology Development
Testing
System inteegration
testing
User acceptance testing
Executed Phase
Closing phase
Post project review
Stakeholder sign off
Post go-live support
Closed
Figure 1: Product Breakdown Structure
0 - ERP information system development for AAA law firm
1 - Initialization
1.1 - Analysis of requirements 1.2 - Charter Documentation 1.3 - PID documentation 1.4 - Team members appointment M1 - Kick off
2 - Planning phase
2.1 - Schedule Estimation 2.2 - Resource Estimation 2.3 - Finance Management 2.4 - Quality Management 2.5 - Risk Management 2.6 - Acceptance Criteria 2.7 - Communication Process 2.8 - Procurement management M2 - Plan Approval
3 - Execution phase
3.1 - Business Needs Identification 3.2 - ERP Vendor Selection 3.3 - Customization of functions 3.4 - Migration of data 3.5 - Infrastructure checking 3.6 - Operation Development 3.7 - Change management 3.8 - Technology Development 3.9 - Testing 3.10 - System inteegration testing 3.11 - User acceptance testing M3 - Executed Phase
4 - Closing phase
4.1 - Post project review 4.2 - Stakeholder sign off 4.3 - Post go-live support M4 - Closed
Figure 2: Product Flow Diagram
6

IFN700: Case Study Task (CST) – sem2 2018
4.3 Work breakdown structure (WBS)
The work breakdown structure for the project of ERP information system development
for AAA law firm is shown below,
ERP information system
development for AAA law
firm
Initialization
Analysis of
requirements
Charter
Documentation
PID documentation
Team members
appointment
Kick off
Planning phase
Schedule Estimation
Resource Estimation
Finance
Management
Quality Management
Risk Management
Acceptance Criteria
Communication
Process
Procurement
management
Plan Approval
Execution phase
Business Needs
Identification
ERP Vendor
Selection
Customization of
functions
Migration of data
Infrastructure
checking
Operation
Development
Change
management
Technology
Development
Testing
System inteegration
testing
User acceptance
testing
Executed Phase
Closing phase
Post project review
Stakeholder sign off
Post go-live support
Closed
Figure 3: Work Breakdown Structure
4.4 Project Task Table
7

IFN700: Case Study Task (CST) – sem2 2018
The task table for the project of ERP information system development for AAA law firm
is given below,
WBS Task Name Duratio
n Start Finish
0 ERP information system development for AAA
law firm 41 days Mon
10/22/18
Mon
12/17/18
1 Initialization 14 days Mon
10/22/18 Thu 11/8/18
1.1 Analysis of requirements 4 days Mon
10/22/18 Thu 10/25/18
1.2 Charter Documentation 4 days Fri 10/26/18 Wed
10/31/18
1.3 PID documentation 5 days Fri 10/26/18 Thu 11/1/18
1.4 Team members appointment 6 days Thu 11/1/18 Thu 11/8/18
M1 Kick off 0 days Wed
10/31/18
Wed
10/31/18
2 Planning phase 13 days Thu 11/1/18 Mon
11/19/18
2.1 Schedule Estimation 5 days Fri 11/2/18 Thu 11/8/18
2.2 Resource Estimation 7 days Fri 11/2/18 Mon
11/12/18
2.3 Finance Management 6 days Fri 11/9/18 Fri 11/16/18
2.4 Quality Management 5 days Fri 11/9/18 Thu 11/15/18
2.5 Risk Management 7 days Thu 11/1/18 Fri 11/9/18
2.6 Acceptance Criteria 6 days Thu 11/1/18 Thu 11/8/18
2.7 Communication Process 5 days Fri 11/9/18 Thu 11/15/18
2.8 Procurement management 7 days Fri 11/9/18 Mon
11/19/18
M2 Plan Approval 0 days Thu 11/8/18 Thu 11/8/18
8

IFN700: Case Study Task (CST) – sem2 2018
3 Execution phase 24 days Fri 11/9/18 Wed
12/12/18
3.1 Business Needs Identification 15 days Tue 11/13/18 Mon 12/3/18
3.2 ERP Vendor Selection 12 days Mon
11/19/18 Tue 12/4/18
3.3 Customization of functions 15 days Fri 11/16/18 Thu 12/6/18
3.4 Migration of data 16 days Mon
11/12/18 Mon 12/3/18
3.5 Infrastructure checking 17 days Mon
11/12/18 Tue 12/4/18
3.6 Operation Development 19 days Fri 11/9/18 Wed 12/5/18
3.7 Change management 18 days Fri 11/9/18 Tue 12/4/18
3.8 Technology Development 17 days Fri 11/16/18 Mon
12/10/18
3.9 Testing 15 days Fri 11/16/18 Thu 12/6/18
3.10 System integration testing 16 days Tue 11/20/18 Tue 12/11/18
3.11 User acceptance testing 17 days Tue 11/20/18 Wed
12/12/18
M3 Executed Phase 0 days Mon
11/19/18
Mon
11/19/18
4 Closing phase 27 days Fri 11/9/18 Mon
12/17/18
4.1 Post project review 3 days Fri 11/9/18 Tue 11/13/18
4.2 Stakeholder sign off 3 days Thu 12/13/18 Mon
12/17/18
4.3 Post go-live support 3 days Tue 12/4/18 Thu 12/6/18
M4 Closed 0 days Mon 12/3/18 Mon 12/3/18
9

IFN700: Case Study Task (CST) – sem2 2018
4.5 Network diagram and critical path
The network diagram and the critical path of the project of ERP information system
development for AAA law firm is shown below,
2 8
3
5
6
11
20 33
10
19
18
9
34
14
16
12 21
22
13
25
26
23
24
31
15
27
29
28 324
Figure 4: Network Diagram
ID Task
Mode
WBS Task Name Duration
2 1.1 Analysis of requirements 4 days
4 1.3 PID documentation 5 days
8 2.1 Schedule Estimation 5 days
15 2.8 Procurement management 7 days
28 3.11 User acceptance testing 17 days
32 4.2 Stakeholder sign off 3 days
Project planner,Project manager
Project planner
Project planner, Supervisor
Project planner, Supervisor,Finanacial manager
Supervisor,Technical engineer
Project manager
S M T W T F S S M T W
Oct 14, '18 Nov 4, '18 Nov 25, '18 Dec 16, '18 Jan 6, '19
Figure 5: Critical Path Identification
5. Justify the chosen methodology
The Prince2 methodology has been selected for identifying the utilization of the
successive and improved management processing. The implication would be helpful for making
sure that the project plan is executed successfully. The Prince2 methodology would align with
10

IFN700: Case Study Task (CST) – sem2 2018
the consideration for the execution of the factors. The Prince2 methodology would be helpful for
aligning with the concept of improved factor development. The methodology has been selected
for the following points,
Improved Plan Development: Prince2 allows the development of the improved
management process. It would make sure that the foundation of the effective planning and
development. Prince2 follows the structure of 5 step model (initiating, planning, developing,
monitoring, and closing) for the completion of the project plan.
Resource Management: Prince2 allows the significant management of the factors for
developing the improved functional development. The resource management has been eased with
the consideration of the factors and development of aligned management. The construction
management would be implied with the utilization of the factorial development.
6. Key stakeholders
The key stakeholders of the project include the owners, project quality head, operation
head, end users, project manager, and sponsors. They are highly impacted and play a vital role in
the completion of the project activity.
Role Name Contact Information Power Impact
Owner Alice Keith alice.keith@****mail.com
+41-****-****
High High
Sponsor Amanda Jones amanda.jones@****mail.com
+41-****-****
High High
Project
Manager
Chuck Jane jane.chuck@****mail.com
+41-****-****
Low High
Quality Head Kristie Bill bill.kristie@****mail.com
+41-****-****
High Low
End User Jack Mathew mathew.jack@****mail.com
+41-****-****
Low Low
Operation Head Perry Connor Perry.connor@****mail.com High Low
11

IFN700: Case Study Task (CST) – sem2 2018
+41-****-****
12

IFN700: Case Study Task (CST) – sem2 2018
7. Outline solution
The change management would be helpful for taking care of the factors and developing the management for developing the proper plan estimation. The following is the outline solution structure for the project of ERP information
system development for AAA law firm,
1
1.1 1.2 1.3 1.4 M1
2
2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 M2
3
3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 M3
4
4.1 4.2 4.3 M4
Initialization
$3,880.00 232 hours Analysis of requirements
$1,120.00 64 hours
Charter Documentation
$480.00 32 hours
PID documentation
$600.00 40 hours
Team members
appointment
$1,680.00 96 hours
Kick off
$0.00 0 hours
Planning phase
$11,920.00 920 hours Schedule Estimation
$1,000.00 80 hours
Resource Estimation
$2,520.00 168 hours
Finance Management
$1,440.00 96 hours
Quality Management
$1,400.00 120 hours
Risk Management
$1,120.00 112 hours
Acceptance Criteria
$1,200.00 96 hours
Communication Process
$1,000.00 80 hours
Procurement
management
$2,240.00 168 hours
Plan Approval
$0.00 0 hours
Execution phase
$52,040.00 4,456 hours Business Needs
Identification
$4,800.00 360 hours
ERP Vendor Selection
$1,920.00 192 hours
Customization of
functions
$4,200.00 360 hours
Migration of data
$4,480.00 384 hours
Infrastructure checking
$5,440.00 544 hours
Operation Development
$6,840.00 456 hours
Change management
$8,640.00 720 hours
Technology Development
$6,120.00 544 hours
Testing
$2,400.00 240 hours
System inteegration
testing
$4,480.00 384 hours
User acceptance testing
$2,720.00 272 hours
Executed Phase
$0.00 0 hours
Closing phase
$1,200.00 72 hours Post project review
$360.00 24 hours
Stakeholder sign off
$480.00 24 hours
Post go-live support
$360.00 24 hours
Closed
$0.00 0 hours
Figure 6: Solution Structure Development
13

IFN700: Case Study Task (CST) – sem2 2018
8. Key risks
The information management would be implied with the management of the successful
formation of the risk identification. The major risk factors for the project of ERP information
system development for AAA law firm include,
Risk Risk Type Probabilit
y
Impact Mitigation Strategy
Over budget Financial High Medium Avoid risk - change the plan to circumvent the
problem
Delay in
Completion
Performance High Low Accept risk - take the chance and possible
consequences of the threat happening
System Design
Issues
Technical Low High Transfer risk - outsource the risk to a third
party either through insurance or by
outsourcing the responsibility
Functional
Issues
Technical Medium High Mitigate risk - reduce the probability and/or
impact through planned actions
9. Delivery and release planning
9.1 Gantt chart
14

IFN700: Case Study Task (CST) – sem2 2018
ID Task
Mode
WBS Task Name Duration
0 0 ERP information system
development for AAA law firm
41 days
1 1 Initialization 14 days
2 1.1 Analysis of requirements 4 days
3 1.2 Charter Documentation 4 days
4 1.3 PID documentation 5 days
5 1.4 Team members appointment 6 days
6 M1 Kick off 0 days
7 2 Planning phase 13 days
8 2.1 Schedule Estimation 5 days
9 2.2 Resource Estimation 7 days
10 2.3 Finance Management 6 days
11 2.4 Quality Management 5 days
12 2.5 Risk Management 7 days
13 2.6 Acceptance Criteria 6 days
14 2.7 Communication Process 5 days
15 2.8 Procurement management 7 days
16 M2 Plan Approval 0 days
17 3 Execution phase 24 days
18 3.1 Business Needs Identification 15 days
19 3.2 ERP Vendor Selection 12 days
20 3.3 Customization of functions 15 days
21 3.4 Migration of data 16 days
22 3.5 Infrastructure checking 17 days
23 3.6 Operation Development 19 days
24 3.7 Change management 18 days
25 3.8 Technology Development 17 days
26 3.9 Testing 15 days
27 3.10 System inteegration testing 16 days
28 3.11 User acceptance testing 17 days
29 M3 Executed Phase 0 days
30 4 Closing phase 27 days
31 4.1 Post project review 3 days
32 4.2 Stakeholder sign off 3 days
33 4.3 Post go-live support 3 days
34 M4 Closed 0 days
Project planner,Project manager
Finanacial manager
Project planner
Project planner,Project manager
10/31
Project planner, Supervisor
Project planner,Finanacial manager,Human resource manager
Project planner,Finanacial manager
Supervisor,Finanacial manager,Risk analyst
Risk analyst,Tester
Project planner, Supervisor
Project planner, Supervisor
Project planner, Supervisor,Finanacial manager
11/8
Supervisor,Database manager,Human resource manager
Supervisor,Technical engineer
Risk analyst,Technical engineer,Project planner
Database manager,Technical engineer,Tester
Supervisor,Risk analyst,Technical engineer,Tester
Database manager,Project manager,Technical engineer
Project planner, Supervisor,Database manager,Risk analyst,Technical engineer
Supervisor,Database manager,Risk analyst,Technical engineer
Risk analyst,Tester
Supervisor,Database manager,Technical engineer
Supervisor,Technical engineer
11/19
Project planner
Project manager
Project planner
12/3
S M T W T F S S M T W T F S S
Oct 14, '18 Nov 4, '18 Nov 25, '18 Dec 16, '18 Jan 6, '19 Jan 27, '19
Figure 7: Gantt chart of the project
10. Project control
The following are the control measure for the project of ERP information system
development for AAA law firm,
 Development of the checklist and identifying the probable issues allocated with it
 Tracking project with the help of Ms-Project Gantt chart
 Cost Budget Management for making sure the cost are defined
15

IFN700: Case Study Task (CST) – sem2 2018
11. Project costs
Resource Name Work Standard Rate Cost
Project manager 256 hrs $20.00/hr $5,120.00
Project planner 720 hrs $15.00/hr $10,800.00
Database manager 808 hrs $15.00/hr $12,120.00
Supervisor 1,120 hrs $10.00/hr $11,200.00
Human resource
manager
176 hrs $15.00/hr $2,640.00
Risk analyst 752 hrs $10.00/hr $7,520.00
Financial manager 232 hrs $15.00/hr $3,480.00
Tester 440 hrs $10.00/hr $4,400.00
Technical
engineer
1,176 hrs $10.00/hr $11,760.00
16

IFN700: Case Study Task (CST) – sem2 2018
21 1 11 21 1 11
$0.00
$5,000.00
$10,000.00
$15,000.00
$20,000.00
$25,000.00
$30,000.00
$2,080.00
$9,280.00
$20,800.00
$25,280.00
$10,520.00
$1,080.00
Cost
Figure 8: Time Phased Budget (Phase Wise)
17

IFN700: Case Study Task (CST) – sem2 2018
Bibliography
Cleden, D. (2017). Managing project uncertainty. Routledge.
Coombs, C. R. (2015). When planned IS/IT project benefits are not realized: a study of inhibitors
and facilitators to benefits realization. International Journal of Project
Management, 33(2), 363-379.
Fleming, Q. W., & Koppelman, J. M. (2016, December). Earned value project management.
Project Management Institute.
Harris, E. (2017). Strategic project risk appraisal and management. Routledge.
Harrison, F., & Lock, D. (2017). Advanced project management: a structured approach.
Routledge.
Hornstein, H. A. (2015). The integration of project management and organizational change
management is now a necessity. International Journal of Project Management, 33(2),
291-298.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Ko, D. G., & Kirsch, L. J. (2017). The hybrid IT project manager: One foot each in the IT and
business domains. International Journal of Project Management, 35(3), 307-319.
Marchewka, J. T. (2014). Information technology project management. John Wiley & Sons.
Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business and
technology. Routledge.
18

IFN700: Case Study Task (CST) – sem2 2018
Svejvig, P., & Andersen, P. (2015). Rethinking project management: A structured literature
review with a critical look at the brave new world. International Journal of Project
Management, 33(2), 278-290.
Terlizzi, M. A., de Souza Meirelles, F., & de Moraes, H. R. O. C. (2016). Barriers to the use of
an IT project management methodology in a large financial institution. International
Journal of Project Management, 34(3), 467-479.
19