Business Case: Corporate Database Project Plan for First National Bank

This document presents a business case for the development and implementation of a corporate database at First National Bank (FNB). The project aims to improve resource utilization, streamline business operations, and reduce business risks. Key objectives include successful database implementation, secure data migration, and adherence to the project schedule and budget. The scope encompasses various tasks from system analysis and project planning to database design, implementation, and employee training. The document outlines in-scope and out-of-scope items, project deliverables, success criteria, resource allocation, risk management, work breakdown structure, project timeline, communication plan, and change management plan. The risk plan identifies potential risks such as resistance to change and security attacks, and provides mitigation strategies. The work breakdown structure details tasks from initiation to closure, with corresponding timelines and milestones. A communication plan ensures stakeholders are informed throughout the project lifecycle. The ultimate goal is to implement a corporate database that enhances information security, improves employee performance, and delivers a positive return on investment for FNB.

Name Hassan Mustafa
Subject Name Project Management Capstone
Submitted to Luke Webster
Assignment Name Business Case
Submission Date 07.10.2018
1

Table of Contents
Introduction................................................................................................................................................3
Project Title...........................................................................................................................................3
Project Aim............................................................................................................................................3
Project Background...............................................................................................................................3
Project Benefits.....................................................................................................................................3
Project Objectives..................................................................................................................................3
Project Scope.............................................................................................................................................3
Organizational Context..........................................................................................................................3
In-Scope & Out-of-Scope Items............................................................................................................4
Project Deliverables..............................................................................................................................5
Success Criteria.....................................................................................................................................5
Resources...............................................................................................................................................5
Linkages................................................................................................................................................6
Risk Plan....................................................................................................................................................6
Assumptions..........................................................................................................................................6
Constraints.............................................................................................................................................6
Risk Register.........................................................................................................................................6
Work Breakdown.......................................................................................................................................7
Timeframe & Milestones...........................................................................................................................9
Communication Plan...............................................................................................................................10
Change Management Plan.......................................................................................................................12
Project Team Roles..................................................................................................................................12
High Level Timeline................................................................................................................................13
References................................................................................................................................................14
Appendix..................................................................................................................................................15
Gantt chart...........................................................................................................................................15
2

Introduction
Project Title
Corporate Database Development for First National Bank (FNB)
Project Aim
The aim of the project is to implement a corporate database at FNB and make sure
that the employees adapt to the changes.
Project Background
First National Bank (FNB) is one of the finest banks that are set up in the Midwest.
The bank has been involved in purchasing small banks in Ohio. The expansion of the
business operations and activities will lead to the requirements and involvement of
increased number of data sets. It will be required to implement a corporate database in
the bank.
Project Benefits
 The resources of the bank will be better utilized with the implementation of
the corporate database.
 The business services and operations will be streamlined leading to higher
returns on investment.
 The business risks and cost of business will come down leading to higher
investor engagement and customer satisfaction levels.
Project Objectives
 To successfully implement the corporate database in the First National Bank
 To migrate and manage the existing information and data sets in a secure
manner
 To adhere with the estimated schedule and budget for the project (Wearne,
2014)
3

Project Scope
Organizational Context
First National Bank (FNB) is one of the finest banks that are set up in the Midwest.
The bank has been involved in purchasing small banks in Ohio. The expansion of the
business operations and activities will lead to the requirements and involvement of
increased number of data sets. It will be required to implement a corporate database in
the bank. The resources of the bank will be better utilized with the implementation of
the corporate database. The business services and operations will be streamlined
leading to higher returns on investment. The business risks and cost of business will
come down leading to higher investor engagement and customer satisfaction levels
(Teller, 2013).
In-Scope & Out-of-Scope Items
The following tasks will be completed by the members of the project team:
 Observation & Analysis of the Current System
 Aims and Objectives Definition
 Development of the Project Proposal
 Meeting with Stakeholders
 Project Approval
 Risks Assessment and management
 Scope Definition and Project Estimations
 Change Management Planning
 Resource Allocation
 Security Planning & Communication Guidelines
 Technical Infrastructure Analysis
 Procurement of database and other tools
 Designing of the database set-up
 Setting up of the environment and infrastructure (Dalcher, 2015)
 Network Compatibility and topologies
 Database implementation
 Syncing with other tools
 Integration with BI tools
 Migration of legacy data and systems
 User access and permissions
4

 Security Analysis
 Trainings to the employees of FNB
 Management of changes
 Feedback and lessons learned
 Performance ratings and measurement
 Final documentation
The members of the project team will not negotiate with the vendors and supplier
groups. The marketing tasks will also not be covered.
Project Deliverables
 Project Proposal & Plan: The document covering the high-level and elaborated
details of the project.
 Migrated information sets: The data sets migrated from the legacy system to
the new system.
 Change Report: List and details of the changes made or to be made.
 Minutes of Meetings: The notes on the daily and weekly project meetings.
 Final Report: Completion report of the project.
Success Criteria
 Cost & Schedule Variance: These values will be calculated as per the Earned
Value Analysis method and the project will be considered successful only
when the values are not negative.
 Employee Feedback: The feedback from the employees of FNB will be
collected and shall be positive.
 Performance Graphs: The database performance graphs will be obtained.
 Return on Investment: The value of ROI will be calculated.
Resources
Resource Name Type Initials Max. Units Std. Rate Ovt. Rate Cost/Use Accrue At Base Calendar
Project
Manager
Wor
k
PM 100% $0.00/hr $0.00/hr $0.00 Prorated Standard
Database
Administrator
Work DA 100% $0.00/hr $0.00/hr $0.00 Prorated Standard
Data Analyst Work DAA 100% $0.00/hr $0.00/hr $0.00 Prorated Standard
Database Expert Work DE 100% $0.00/hr $0.00/hr $0.00 Prorated Standard
Technical Expert Work TE 100% $0.00/hr $0.00/hr $0.00 Prorated Standard
Security Analyst Work SA 100% $0.00/hr $0.00/hr $0.00 Prorated Standard
5

Technical Writer Work TW 100% $0.00/hr $0.00/hr $0.00 Prorated Standard
Trainer Work TR 100% $0.00/hr $0.00/hr $0.00 Prorated Standard
FNB Employees Work FNB 100% $0.00/hr $0.00/hr $0.00 Prorated Standard
Linkages
 Information Security: The implementation of the corporate database will lead
to enhanced security of the information sets.
 Performance Growth: The performance and skill sets of the employees will be
improved with the use of new tools.
Risk Plan
Assumptions
 The skill sets of the resources will be utilized in the project correctly.
 The Project Manager will have the skills to utilize the resources in an optimum
manner.
Constraints
 Project schedule and budget
 Resource skills and competencies
Risk Register
ID Name Probability
(01. To 1)
Impact (1
to 10)
Score Response
1 Resistance to
Change
0.8 9 7.2 The risk to FNB corporate
database project shall be
treated and resolved with
avoidance strategy.
2 Information
Security Attacks
0.9 10 9 The risk to FNB corporate
database project shall be
treated and resolved with
mitigation & avoidance
strategy.
3 Communication
Gaps
0.5 7 3.5 The risk to FNB corporate
database project shall be
6

treated and resolved with
avoidance strategy.
4 Schedule/Budget
Overrun
0.4 8 3.2 The risk to FNB corporate
database project shall be
treated and resolved with
avoidance strategy.
5 Quality Issues 0.2 9 1.8 The risk to FNB corporate
database project shall be
treated and resolved with
avoidance strategy
(Atkinson, Crawford, &
Ward, 2006).
6 Legal Obligations 0.2 10 2 The risk to FNB corporate
database project shall be
treated and resolved with
avoidance strategy.
7 Technical Failures 0.5 6 3 The risk to FNB corporate
database project shall be
treated and resolved with
transfer strategy.
8 Ethical Issues 0.2 9 1.8 The risk to FNB corporate
database project shall be
treated and resolved with
avoidance strategy.
9 Operational
Mistakes
0.6 5 3 The risk to FNB corporate
database project shall be
treated and resolved with
avoidance strategy.
10 Resource Risks –
Unavailability,
performance issues
0.4 7 2.8 The risk to FNB corporate
database project shall be
treated and resolved with
avoidance strategy.
7

Work Breakdown
The work breakdown structure for the project is as shown below.
WBS Task Name
1 Corporate Database Development
1.1 Initiation
1.1.1 Observation & Analysis of the Current System
1.1.2 Aims and Objectives Definition
1.1.3 Project Proposal
1.1.4 Meeting with Stakeholders
1.1.5 Project Approval
1.1.6 Milestone 1: Project Proposal
1.2 Planning
1.2.1 Risks Assessment
1.2.2 Scope Definition and Project Estimations
1.2.3 Change Management Planning
1.2.4 Resource Allocation
1.2.5 Security Planning & Communication Guidelines
1.2.6 Technical Infrastructure Analysis
1.2.7 Milestone 2: Project Plan
1.3 Execution
1.3.1 Procurement of database and other tools
1.3.2 Designing of the database set-up
1.3.3 Setting up of the environment and infrastructure
1.3.4 Network Compatibility and topologies
1.3.5 Database implementation
1.3.6 Syncing with other tools
1.3.7 Milestone 3: Corporate Database
1.4 Implementation & Control
1.4.1 Integration with BI tools
1.4.2 Migration of legacy data and systems
1.4.3 User access and permissions
1.4.4 Security Analysis
8

1.4.5 Milestone 4: Migrated data sets
1.5 Closure
1.5.1 Trainings to the employees of FNB
1.5.2 Management of changes
1.5.3 Feedback and lessons learned
1.5.4 Performance ratings and measurement
1.5.5 Final documentation
1.5.6 Milestone 5: Completion Report
Timeframe & Milestones
WB
S
Task Name Duratio
n
Start Finish Predecessor
s
1 Corporate Database Development 61 days Mon 17/09/18 Sun 09/12/18
1.1 Initiation 5 days Mon 17/09/18 Fri 21/09/18
1.1.1 Observation & Analysis of the Current System 1 day Mon 17/09/18 Mon 17/09/18
1.1.2 Aims and Objectives Definition 1 day Thu 20/09/18 Thu 20/09/18 3
1.1.3 Project Proposal 1 day Tue 18/09/18 Thu 20/09/18 3
1.1.4 Meeting with Stakeholders 1 day Tue 18/09/18 Tue 18/09/18 3
1.1.5 Project Approval 1 day Fri 21/09/18 Fri 21/09/18 4,5,6
1.1.6 Milestone 1: Project Proposal 0 days Fri 21/09/18 Fri 21/09/18 7
1.2 Planning 11 days Mon 24/09/18 Mon 08/10/18
1.2.1 Risks Assessment 4 days Mon 24/09/18 Mon 01/10/18 8
1.2.2 Scope Definition and Project Estimations 1 day Tue 02/10/18 Tue 02/10/18 10
1.2.3 Change Management Planning 1 day Wed 03/10/18 Wed 03/10/18 11
1.2.4 Resource Allocation 1 day Mon 08/10/18 Mon 08/10/18 11
1.2.5 Security Planning & Communication Guidelines 1 day Wed 03/10/18 Wed 03/10/18 11
1.2.6 Technical Infratructure Analysis 1 day Wed 03/10/18 Wed 03/10/18 11
1.2.7 Milestone 2: Project Plan 0 days Mon 08/10/18 Mon 08/10/18 15,12,13,14
1.3 Execution 18 days Tue 09/10/18 Thu 01/11/18
1.3.1 Procurement of database and other tools 2 days Tue 09/10/18 Wed 10/10/18 16
1.3.2 Designing of the database set-up 2 days Thu 11/10/18 Fri 12/10/18 18
1.3.3 Setting up of the environment and infrastructure 2 days Fri 19/10/18 Mon 22/10/18 19
1.3.4 Network Compatibility and topologies 2 days Mon 15/10/18 Tue 16/10/18 19
1.3.5 Database implementation 3 days Tue 23/10/18 Thu 25/10/18 20,21
1.3.6 Syncing with other tools 3 days Tue 30/10/18 Thu 01/11/18 22
1.3.7 Milestone 3: Corporate Database 0 days Thu 01/11/18 Thu 01/11/18 23
1.4 Implementation & Control 10 days Fri 02/11/18 Thu 15/11/18
1.4.1 Integration with BI tools 2 days Fri 02/11/18 Mon 05/11/18 24
1.4.2 Migration of legacy data and systems 4 days Tue 06/11/18 Fri 09/11/18 26
1.4.3 User access and permissions 2 days Mon 12/11/18 Tue 13/11/18 27
9

1.4.4 Secuirty Analysis 2 days Wed 14/11/18 Thu 15/11/18 28
1.4.5 Milestone 4: Migrated data sets 0 days Thu 15/11/18 Thu 15/11/18 29
1.5 Closure 17 days Fri 16/11/18 Sun 09/12/18
1.5.1 Trainings to the employees of FNB 5 days Fri 16/11/18 Thu 22/11/18 30
1.5.2 Management of changes 5 days Fri 23/11/18 Thu 29/11/18 32
1.5.3 Feedback and lessons learned 2 days Tue 04/12/18 Wed 05/12/18 33
1.5.4 Performance ratings and measurement 2 days Fri 30/11/18 Mon 03/12/18 33
1.5.5 Final documentation 3 days Thu 06/12/18 Sun 09/12/18 34,35
1.5.6 Milestone 5: Completion Report 0 days Sun 09/12/18 Sun 09/12/18 36
Communication Plan
Stakeholders Who What are their information
needs
How & when will we
provide them
information
First National Bank
(FNB)
Project
Sponsor
Details of the adaptability and
resistance of the employees
towards the change, project
estimates, project progress
status, project schedule &
budget, major issues
Meetings: Weekly basis
using teleconferencing
tools
Updates and
Notifications: Emails
Information Sharing:
SharePoint location
Investors The investors
associated
with FNB
Project benefits, release date,
aims and objectives
Meetings: Weekly basis
using teleconferencing
tools
Updates and
Notifications: Emails
Information Sharing:
SharePoint location
(Missonier, & Loufrani-
Fedida, 2014)
Customers The end-users
and clients of
FNB
Project benefits, release date,
aims and objectives
Meetings: Weekly basis
using teleconferencing
tools
10

Updates and
Notifications: Emails
Information Sharing:
SharePoint location
Suppliers The suppliers
of the tools
and
equipment
needed in the
project
List of tools Meetings: Weekly basis
using teleconferencing
tools
Updates and
Notifications: Emails
Information Sharing:
SharePoint location
Business Partners The partners
engaged with
FNB
(Shareholders
)
Details of the adaptability and
resistance of the employees
towards the change, project
estimates, project progress
status, project schedule &
budget, major issues
(Koskinen, 2004)
Meetings: Weekly basis
using teleconferencing
tools
Updates and
Notifications: Emails
Information Sharing:
SharePoint location
Project Team The core
project team
responsible
for carrying
out the project
activities
Project requirements, project
funds, business case, existing
system details
Meetings: Daily basis
using teleconferencing
tools
Updates and
Notifications: Emails
Information Sharing:
SharePoint location
Change Management Plan
There will be several changes that may come up in the project in the form of project
technological changes, changes in expectations of the client, changes in quality
parameters, resource changes, etc.
11

Management of these changes will be essential to ensure that the project is successful.
There will be a phased process implemented for managing these changes. The phases
will include planning of the changes by developing change requests followed by
execution of the changes. The changes will then be monitored and controlled. The
change closure will then take place.
Project Team Roles
Executive Sponsor:  First National Bank
 Responsible for providing the project team with Project requirements,
project funds, business case, existing system details
 Communication availability
Project Key
Contacts:
Project Manager
Name: Project Manager
Email: Emails Address
Phone: Phone Number
Review Process: There will be daily meeting facilitated by the Project Manager with the
project team members and weekly meeting with the stakeholders. The
review processes will also be included in every project phase and will be
conducted by the manager in association with project board and senior
management. The review reports will be published and the improvement
activities will be done accordingly.
Start Date: 17th
September
2018
Completion Date: 9th December 2018
Executive Sponsor
Statement:
Name: Signature & Date:
12

High Level Timeline
WB
S
Task Name Duratio
n
Start Finish
1 Corporate Database
Development
61 days Mon 17/09/18 Sun 09/12/18
1.1 Initiation 5 days Mon 17/09/18 Fri 21/09/18
1.2 Planning 11 days Mon 24/09/18 Mon 08/10/18
1.3 Execution 18 days Tue 09/10/18 Thu 01/11/18
1.4 Implementation &
Control
10 days Fri 02/11/18 Thu 15/11/18
1.5 Closure 17 days Fri 16/11/18 Sun 09/12/18
13

References
Atkinson, R., Crawford, L., & Ward, S. (2006). Fundamental uncertainties in projects
and the scope of project management. International Journal Of Project
Management, 24(8), 687-698. doi: 10.1016/j.ijproman.2006.09.011
Dalcher, D. (2015). Going Beyond The Waterfall: Managing Scope Effectively
Across the Project Life Cycle. Project Management Journal, 46(1), e2-e2. doi:
10.1002/pmj.21475
Koskinen, K. (2004). Knowledge Management to Improve Project Communication
and Implementation. Project Management Journal, 35(2), 13-19. doi:
10.1177/875697280403500203
Missonier, S., & Loufrani-Fedida, S. (2014). Stakeholder analysis and engagement in
projects: From stakeholder relational perspective to stakeholder relational
ontology. International Journal Of Project Management, 32(7), 1108-1122.
doi: 10.1016/j.ijproman.2014.02.010
Teller, J. (2013). Portfolio Risk Management and Its Contribution to Project Portfolio
Success: An Investigation of Organization, Process, and Culture. Project
Management Journal, 44(2), 36-51. doi: 10.1002/pmj.21327
Wearne, S. (2014). Evidence-Based Scope for Reducing “Fire-Fighting†in
Project Management. Project Management Journal, 45(1), 67-75. doi:
10.1002/pmj.21395
14

Appendix
Gantt chart
15