Corporate Database Development for First National Bank (FNB)

The aim of the project is to implement a corporate database at FNB and make sure that the employees adapt to the changes. The project will streamline business operations and activities, leading to higher returns on investment and customer satisfaction levels.

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

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................................................................................................................................................7
Risk Plan....................................................................................................................................................7
Assumptions..........................................................................................................................................7
Constraints.............................................................................................................................................7
Risk Register.........................................................................................................................................7
Work Breakdown.......................................................................................................................................9
Timeframe & Milestones.........................................................................................................................10
Communication Plan...............................................................................................................................11
Change Management Plan.......................................................................................................................13
Project Team Roles..................................................................................................................................13
High Level Timeline................................................................................................................................14
Current Knowledge and skills.................................................................................................................15
Specific area of theory.............................................................................................................................15
References................................................................................................................................................17
Appendix..................................................................................................................................................18
Gantt chart...........................................................................................................................................18

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)
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
 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 Work
Project Manager 112 hrs
Aims and Objectives Definition 8 hrs
Project Proposal 8 hrs
Meeting with Stakeholders 8 hrs
Project Approval 8 hrs
Risks Assessment 8 hrs
Scope Definition and Project Estimations 8 hrs
Resource Allocation 8 hrs
Security Planning & Communication Guidelines 8 hrs

Procurement of database and other tools 16 hrs
Feedback and lessons learned 16 hrs
Performance ratings and measurement 16 hrs
Database Administrator 120 hrs
Observation & Analysis of the Current System 8 hrs
Database implementation 24 hrs
Migration of legacy data and systems 32 hrs
User access and permissions 16 hrs
Management of changes 40 hrs
Data Analyst 32 hrs
Migration of legacy data and systems 32 hrs
Database Expert 72 hrs
Risks Assessment 8 hrs
Change Management Planning 8 hrs
Designing of the database set-up 16 hrs
Syncing with other tools 24 hrs
Integration with BI tools 16 hrs
Technical Expert 56 hrs
Technical Infrastructure Analysis 8 hrs
Setting up of the environment and infrastructure 16 hrs
Network Compatibility and topologies 16 hrs
Integration with BI tools 16 hrs
Security Analyst 24 hrs
Security Planning & Communication Guidelines 8 hrs
Security Analysis 16 hrs
Technical Writer 24 hrs
Final documentation 24 hrs
Trainer 40 hrs
Trainings to the employees of FNB 40 hrs

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
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.
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
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
WBS Task Name Duration
1 Corporate Database Development 61 days
1.1 Initiation 22 days
1.1.1 Observation & Analysis of the Current System 1 day
1.1.2 Aims and Objectives Definition 1 day
1.1.3 Project Proposal 1 day
1.1.4 Meeting with Stakeholders 1 day
1.1.5 Project Approval 1 day
1.1.6 Milestone 1: Project Proposal 0 days
1.2 Planning 6 days
1.2.1 Risks Assessment 1 day
1.2.2 Scope Definition and Project Estimations 1 day
1.2.3 Change Management Planning 1 day
1.2.4 Resource Allocation 1 day
1.2.5 Security Planning & Communication Guidelines 1 day
1.2.6 Technical Infrastructure Analysis 1 day
1.2.7 Milestone 2: Project Plan 0 days
1.3 Execution 18 days
1.3.1 Procurement of database and other tools 2 days
1.3.2 Designing of the database set-up 2 days
1.3.3 Setting up of the environment and infrastructure 2 days
1.3.4 Network Compatibility and topologies 2 days

1.3.5 Database implementation 3 days
1.3.6 Syncing with other tools 3 days
1.3.7 Milestone 3: Corporate Database 0 days
1.4 Implementation & Control 10 days
1.4.1 Integration with BI tools 2 days
1.4.2 Migration of legacy data and systems 4 days
1.4.3 User access and permissions 2 days
1.4.4 Security Analysis 2 days
1.4.5 Milestone 4: Migrated data sets 0 days
1.5 Closure 17 days
1.5.1 Trainings to the employees of FNB 5 days
1.5.2 Management of changes 5 days
1.5.3 Feedback and lessons learned 2 days
1.5.4 Performance ratings and measurement 2 days
1.5.5 Final documentation 3 days
1.5.6 Milestone 5: Completion Report 0 days
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
Project benefits, release date,
aims and objectives
Meetings: Weekly basis
using teleconferencing

with FNB 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
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
Project requirements, project
funds, business case, existing
Meetings: Daily basis
using teleconferencing

responsible
for carrying
out the project
activities
system details 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.
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:
High Level Timeline
WBS Task Name Duration Start Finish
1 Corporate Database
Development 61 days Mon 17-09-18 Sun 09-12-18
1.1 Initiation 22 days Mon 17-09-18 Tue 16-10-18
1.2 Planning 6 days Wed 17-10-18 Wed 24-10-
18
1.3 Execution 18 days Mon 22-10-18 Wed 14-11-
18
1.4 Implementation & Control 10 days Tue 06-11-18 Mon 19-11-
18
1.5 Closure 17 days Fri 16-11-18 Sun 09-12-18
Current Knowledge and skills
Corporate Database Development for First National Bank project plan requires the
company to design a corporate database and expects employees to adapt to it. In
developing the project management plan, I possess both an analyst skill and
managerial skills. Before framing the plan, the exact needs of the proposed system is
to be framed. In doing so, various fact finding techniques can be used. In the given
scenario, observations technique was used. Information was gathered on the basis of

details given in the case study. I have good skills at finding out answers to three
questions – What, How and When. I was able to figure out the root cause of problem.
With respect to project management, I have skills pertaining to managing time and
resources. Activities were broken into small manageable small tasks. Then on the
basis of previously done projects, I was able to figure out the duration each of the
tasks and then I also managed to find out which all activities can be done in parallel
and in linear manner. The next task of resource allocation was also done proficiently
because there should not be any resource conflicts. Managing resources in assigned
deadline is the key behind every successful project.
Specific area of theory
I have studied Project Management as well in my course. Specifically, in project
management I studied various aspects of Project Management from the perspective of
PMBoK which is Project Management Body of Knowledge. It is among the most
famous methodologies in project management and is being used across the world for
various types of project. In the case for the database being developed for the First
National Bank, the same project management principles shall be used. This is
because, it’s a large and diverse project that will ultimately affect millions of users of
the bank. The database has to be robust and reliable for it to perform its required
functions. Within project management, specifically, the theory that shall be used
extensively would be areas of project management such as Stakeholder Management,
Risk Management, Change Management, Resource, Time and Budget management
among others. The theories for these respective areas needs to be strong so as to be
put to use for such a task. Apart from that, my theories of Database Management
Systems shall also be put to use. DBMS is an active interest area particularly because
all kinds of software and systems require database and a thorough understanding of
the intricacies of database management will help in the development of this project.

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
Sul, W., Yeom, H., & Jung, H. (2018). Towards Sustainable High-Performance
Transaction Processing in Cloud-based DBMS. Cluster Computing. doi:
10.1007/s10586-018-2826-3
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
Turner, J. (2006). Towards a theory of project management: The nature of the project
governance and project management. International Journal Of Project
Management, 24(2), 93-95. doi: 10.1016/j.ijproman.2005.11.008
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

Appendix
Gantt chart