Redesign Management Information System in Burger King

The project plan is based on redesign of management information system in Burger King (BK). The project is based on developing a Management Information System (MIS) for the company based on the project management principles.

Running head: PROJECT MANAGEMENT
Redesign Management Information System in Burger King
Name of the Student:
Name of the University:

1PROJECT MANAGEMENT
Table of Contents
1. Introduction..................................................................................................................................3
2. Communication plan, WBS and RACI........................................................................................3
2.1 Stakeholder prioritization matrix...........................................................................................3
2.2 Project communication matrix...............................................................................................4
2.3 Work breakdown structure....................................................................................................5
2.4 RACI chart.............................................................................................................................7
3. Project Schedule Plan..................................................................................................................9
3.1 AoN........................................................................................................................................9
3.2 Time estimation...................................................................................................................10
3.2.1 Time estimation- Enumeration method........................................................................12
3.2.2 Time estimation- Two pass method..............................................................................13
3.3 Critical path.........................................................................................................................13
3.4 Gantt chart...........................................................................................................................14
4. Resources and budgeting...........................................................................................................15
4.1 Resource loading.................................................................................................................15
4.2 Budget..................................................................................................................................15
4.3 Reporting.............................................................................................................................19
4.3.1 Earned value management............................................................................................19
4.3.2 Timeline reporting........................................................................................................21
5. Risk management.......................................................................................................................22
5.1 Risk identification................................................................................................................22
6. Quality management and project closure..................................................................................23
6.1 Quality tools.........................................................................................................................23

2PROJECT MANAGEMENT
6.2 Change management............................................................................................................24
7. Project closure...........................................................................................................................25
7.1 Transition plan.....................................................................................................................25
7.2 Close procurements.............................................................................................................26
7.3 Knowledge management.....................................................................................................26
7.4 Lessons learned....................................................................................................................26
7.5 Customer feedback..............................................................................................................26
8. Conclusion.................................................................................................................................27
References......................................................................................................................................28

3PROJECT MANAGEMENT
1. Introduction
The project plan is based on redesign of management information system in Burger King
(BK). BK is the global chain of the hamburger fast food restaurants within America. The project
is based on developing a Management Information System (MIS) for the company based on the
project management principles. The proposed system should provide decisions making activities
to the management team so that they can improve over the business operations. It is used to
provide various impacts like improvement of the contact technologies, and unpredictability of
demands of the clients. The project plan discusses about various aspects of the project
management such as communication plan, work breakdown structure, RACI matrix, scheduling
of entire project, resource and budget planning, risk management, quality management and
project closure.
2. Communication plan, WBS and RACI
2.1 Stakeholder prioritization matrix
This matrix is used to identify the project stakeholders those are involved into the project
along with its power and interest to manage the project work. By use of this matrix, it is used to
determine the stakeholders to manage the project work closely (Kloppenborg 2015, pp. 182).
List of
stakehold
er
Issues of
project
stakehold
ers
Pow
er
Intere
st
Influen
ce
Impa
ct
Urgen
cy
Legitima
cy
Tot
al
Priori
ty
Project
Manager
Proper
planning
of the
project
3 2 2 1 2 3 14 High
Executive
Sponsors
Collect
fund for
1 3 2 1 2 1 10 Mediu
m

4PROJECT MANAGEMENT
the project
Project
Team
Follow a
strict
project
schedule
1 2 1 1 2 1 8 Mediu
m
Functiona
l Lead
Oversee
the
functions
of sales
2 1 1 2 1 1 8 Mediu
m
Technical
Lead
Success of
the
software
solutions
1 3 1 1 3 1 10 Mediu
m
Steering
Committe
e
Monitor
the quality
of the
project
2 3 1 1 1 3 11 Mediu
m
System
Analyst
Analyze
the
proposed
system
1 2 3 2 1 1 9 Mediu
m
2.2 Project communication matrix
It is the document in form of table which summarizes the communication plan behind
redesign of the management information system in Burger King. The matrix is accessible to the
project stakeholders along with updated through entire project work (Kloppenborg 2015,
pp.190).

5PROJECT MANAGEMENT
Stakeholder Lessons
learnt
Information
shared
Time Method Project
owner
Project
Manager
Kick off the
project
Project
objectives and
goals
Weekly basis Face-to-face
meetings
Project Board
Executive
Sponsors
Meetings with
the project
team
Review the
project budget
As required Email and
presentation
Project Board
Project Team Plan the
entire work
Status of the
project
Weekly basis Face-to-face
meetings
Project
Manager
Functional
Lead
Project status
update
Review the
functions of
system
Monthly basis Email and
presentation
Project
Manager
Technical
Lead
Technical
design
Review the
technical
details
Monthly basis Email and
presentation
Technical
team
Steering
Committee
Manage the
project plan
Update the
leadership on
status
Monthly basis Face-to-face
meetings
Project
Manager
System
Analyst
Review the
proposed
system
Discussing
the required
features of
MIS
Weekly basis Email and
presentation
Project
Manager
2.3 Work breakdown structure
[Redesign Management Information System for Burger King]
WBS Task Name
1 Charter Sign Off
2 Initiation of MIS project

6PROJECT MANAGEMENT
2.1 Identifying the scope of project
2.2 Hiring of the human resources
2.3 Feasibility study
2.4 Analyzing the project requirements
2.5 Determining the needs of the business
2.6 Business case
2.7 Milestone 1: Completion of initiation phase
3 Planning of MIS project
3.1 Gathering the requirements of system
3.2 Planning the schedule and cost of system
3.3 Specifications of project scope
3.4 Peer review
3.5 Milestone 2: Completion of planning phase
4 System analysis phase
4.1 Design MIS system
4.2 Preliminary Conceptual Design
4.3 Final design of the system
4.4 Milestone 3: Completion of system analysis phase
5 System testing phase
5.1 Testing of the MIS system
5.2 Identifying the project resources
5.3 Identifying the system tools

7PROJECT MANAGEMENT
5.4 Milestone 4: Completion of system testing phase
6 Risk management phase
6.1 Risk management plan
6.2 Testing the system performance
6.3 Milestone 5: Completion of risk management phase
7 User training phase
7.1 Identifying the trainee
7.2 Conduct the training
7.3 Milestone 6: Completion of user training phase
8 Closure phase
8.1 Release of the resources
8.2 Draft of the final project plan
8.3 Final sign off
8.4 Milestone 7: Completion of closure phase
2.4 RACI chart
This matrix documents roles as well as responsibilities of the project resources those are
involved in the project plan. R- Responsible; A- Accountable; C- Consulted; I- Informed
WBS
code Task Name Project
Sponsor
Project
Manager
Technical
Lead
System
Analyst
Project
Team
1 Charter Sign Off A R I C I
2.1 Identifying the scope of
project
I R A I I
2.2 Hiring of the human R R A C -

8PROJECT MANAGEMENT
resources
2.3 Feasibility study C R I R I
2.4 Analyzing the project
requirements
R A A C I
2.5 Determining the needs of the
business
I R C - -
2.6 Business case - R A - I
3.1 Gathering the requirements
of system
R A R C I
3.2 Planning the schedule and
cost of system
A R I I A
3.3 Specifications of project
scope
R C A A I
3.4 Peer review - R - I I
4.1 Design MIS system C A R R I
4.2 Preliminary Conceptual
Design
C R A I C
4.3 Final design of the system R A R C I
5.1 Testing of the MIS system R A I R I
5.2 Identifying the project
resources
I I C R I
5.3 Identifying the system tools I A - - A

9PROJECT MANAGEMENT
6.1 Risk management plan R A C I -
6.2 Testing the system
performance
C R A I C
7.1 Identifying the trainee - I I - R
7.2 Conduct the training - R I - -
8.1 Release of the resources - R A C I
8.2 Draft of the final project plan C R A I C
8.3 Final sign off R R I I I
3. Project Schedule Plan
3.1 AoN

10PROJECT MANAGEMENT
Figure 1: Activity on Node Diagram
(Source: Created by author using Ms Vision)
3.2 Time estimation
WBS Task Name Duration WBS
Predecessors
Explanation on
duration
1 Charter Sign Off 4 days -
Sign off by project
manager and sponsor
on different days
2 Initiation of MIS project 14 days
2.1 Identifying the scope of project 3 days 1
Takes 3 days for
identifying in-scope
and out scope items
2.2 Hiring of the human resources 2 days 2.1
Takes time to select
the best skilled
resources
2.3 Feasibility study 5 days 1
Takes time for
technical and financial
analysis
2.4 Analyzing the project
requirements 3 days 2.3 Identify all project
needs
2.5 Determining the needs of the
business 4 days 2.4 Identify all project
needs
2.6 Business case 2 days 2.5 Identify objectives,
aim and goals
3 Planning of MIS project 13 days
3.1 Gathering the requirements of
system 3 days 2.7
Takes time to identify
functional and non-
functional
requirements

11PROJECT MANAGEMENT
3.2 Planning the schedule and cost
of system 5 days 2.3
Takes time to plan as
per project
requirements
3.3 Specifications of project scope 3 days 3.2
Takes 3 days for
identifying in-scope
and out scope items
3.4 Peer review 5 days 3.3 Review entire project
activities
4 System analysis phase 15 days
4.1 Design MIS system 4 days 2.5 Identify the system
design needs
4.2 Preliminary Conceptual Design 3 days 3.3,3.4 Design the system as
per needs
4.3 Final design of the system 6 days 4.2 Design the system as
per needs
5 System testing phase 19 days
5.1 Testing of the MIS system 5 days 4.4
Test the proposed
system- user testing,
acceptance testing
5.2 Identifying the project
resources 9 days 4.4 Identify all the
resources involved
5.3 Identifying the system tools 10 days 5.2 Identify tools and
techniques used
6 Risk management phase 27 days
6.1 Risk management plan 15 days 4.3 Identify all the project
risks
6.2 Testing the system
performance
12 days 6.1 Test the system-user
testing and system
acceptance testing

12PROJECT MANAGEMENT
7 User training phase 17 days
7.1 Identifying the trainee 8 days 6.3
Trainee are to be
reviewed who needs
technical training
7.2 Conduct the training 9 days 7.1 Perform technical
training
8 Closure phase 17 days
8.1 Release of the resources 3 days 7.3
Kick off the
stakeholders after
completion
8.2 Draft of the final project plan 6 days 8.1 Prepare the project
documents
8.3 Final sign off 8 days 8.2 Sign off each project
documents
3.2.1 Time estimation- Enumeration method

13PROJECT MANAGEMENT
Figure 2: Time estimation diagram using PERT
(Source: Created by author using Ms Vision)
3.2.2 Time estimation- Two pass method
EST- Early start time; EFT- Early finish time, LST- Late start time, LFT- Late finish time.
Activity Description Time EST EFT LST LFT Slack Criticality
(days)
A Charter sign off 4 0 4 0 4 0 **
B Initiation of MIS system 14 4 18 4 18 0 **
C Planning of MIS system 13 18 31 47 60 29
D System analysis phase 15 18 33 18 33 0 **
E System testing phase 19 33 52 41 60 8
F Risk management phase 27 33 60 33 60 0 **
G User training phase 17 33 50 43 60 10
H Closure phase 17 60 77 60 77 0 **
3.3 Critical path
From the above two pass method table, the critical path of the project is A-B-D-F-H and
it takes 77 days.

14PROJECT MANAGEMENT
3.4 Gantt chart

15PROJECT MANAGEMENT
Figure 3: Gantt chart
(Source: Created by author)
4. Resources and budgeting
4.1 Resource loading
Into this particular project management plan, overloading of the project resources are
caused. The resource allocation is being prevented by the increasing the duration of the project
activities for reduction of project units and times.
4.2 Budget
WBS Task Name Resource Names Cost
0
Redesign Management
Information System in Burger
King
$91,340.00
1 Charter Sign Off Executive Sponsor, Project
Manager $4,800.00
2 Initiation of MIS project $9,520.00
2.1 Identifying the scope of project Project Manager, Project
Team $2,160.00
2.2 Hiring of the human resources Project Manager $800.00
2.3 Feasibility study Project Manager $2,000.00
2.4 Analyzing the project
requirements
Functional Lead, Project
Manager $2,160.00
2.5 Determining the needs of the
business Project Manager $1,600.00

16PROJECT MANAGEMENT
2.6 Business case Project Manager $800.00
2.7 Milestone 1: Complete initiation
phase $0.00
3 Planning of MIS project $8,720.00
3.1 Gathering the requirements of
system Technical Lead $960.00
3.2 Planning the schedule and cost of
system
Project Manager, Project
Team $3,600.00
3.3 Specifications of project scope Project Manager, Project
Team $2,160.00
3.4 Peer review Project Manager $2,000.00
3.5 Milestone 2: Completion of
planning phase $0.00
4 System analysis phase $11,820.00
4.1 Design MIS system
System Analyst, Technical
Lead, Hardware
equipment[1],Software
resources[1]
$6,060.00
4.2 Preliminary Conceptual Design System Analyst, Technical
Lead $1,920.00
4.3 Final design of the system Functional Lead, System
Analyst $3,840.00
4.4 Milestone 3: Completion of $0.00

17PROJECT MANAGEMENT
system analysis phase
5 System testing phase $16,080.00
5.1 Testing of the MIS system System Analyst, Technical
Lead $3,200.00
5.2 Identifying the project resources Project Manager, Project
Team $6,480.00
5.3 Identifying the system tools Functional Lead, Technical
Lead $6,400.00
5.4 Milestone 4: Completion of
system testing phase $0.00
6 Risk management phase $18,480.00
6.1 Risk management plan Project Manager, Project
Team $10,800.00
6.2 Testing the system performance Functional Lead, Technical
Lead $7,680.00
6.3 Milestone 5: Completion of risk
management phase $0.00
7 User training phase $9,680.00
7.1 Identifying the trainee Project Manager $3,200.00
7.2 Conduct the training Project Manager, Project
Team $6,480.00
7.3 Milestone 6: Completion of user
training phase $0.00

18PROJECT MANAGEMENT
8 Closure phase $12,240.00
8.1 Release of the resources Project Manager, Project
Team $2,160.00
8.2 Draft of the final project plan Project Manager, Project
Team $4,320.00
8.3 Final sign off Project Manager, Project
Team $5,760.00
8.4 Milestone 7: Completion of
closure phase $0.00

19PROJECT MANAGEMENT
4.3 Reporting
4.3.1 Earned value management
Activity June July August Septembe
r
October Novembe
r
Decembe
r
January February March April May PV %
Complet
e
EV
Charter sign off $
7,000
$
7,000
$
14,000
100% $
14,000
Initiation of MIS
system
$
5,000
$
7,000
$
12,000
100% $
12,000
Feasibility analysis $
9,000
$
9,000
$
18,000
100% $
18,000
Analyzing the project
requirements
$
7,900
$
6,000
$
5,000
$
18,900
100% $
18,900
Planning of MIS
system
$
6,000
$
8,000
$
14,000
100% $
14,000
System analysis phase $
9,000
$
9,000
100% $
9,000
System testing phase $
9,000
$
9,000
$
18,000
50% $
9,000
Testing the system $
7,000
$
7,000
$
7,000
$
21,000
100% $
21,000
Identify the system
tools
$
9,000
$
9,000
$
10,000
$
28,000
50% $
14,000
Risk managemnt phase $
9,000
$
5,000
$
14,000
0% $
-
User training phase $
9,000
$
9,000
0%
Closure phase $
5,000
$
5,000
0%
Review of the project
plan
$
7,000
$
7,000
0% $
-
Monthly Planned Value
(PV)
$
7,000
$
12,000
$
16,000
$
16,900
$
12,000
$
31,000
$
16,000
$
7,000
$
16,000
$
9,000
$
19,000
$
26,000
$
187,900
$
129,900

20PROJECT MANAGEMENT
Cumulative Planned
Value (PV)
$
7,000
$
19,000
$
35,000
$
51,900
$
63,900
$
94,900
$
110,900
$
117,900
$
133,900
$
142,90
0
$
161,900
$
187,900
Monthly Actual Cost
(AC)
$
12,000
$
15,000
$
17,000
$
17,000
$
18,000
$
18,000
$
19,000
$
15,000
$
15,000
$
-
$
-
$
-
Cumulative Actual
Cost (AC)
$
12,000
$
27,000
$
44,000
$
61,000
$
79,000
$
97,000
$
116,000
$
131,000
$
146,000
$
146,00
0
$
146,000
$
146,000
Monthly Earned Value
(EV)
$
10,000
$
25,000
$
50,000
$
25,000
$
50,000
$
50,000
$
40,000
$
30,000
$
10,000
$
-
$
-
$
-
Cumulative Earned
Value (EV)
$
10,000
$
35,000
$
85,000
$
110,000
$
160,000
$
210,000
$
250,000
$
280,000
$
290,000
$
290,00
0
$
290,000
$
290,000
EV $
160,000
PV $
63,900
AC $
79,000
CV=EV-AC $
81,000
SV=EV-PV $
96,100
CPI=EV/AC 203%
SPI=EV/PV 250%
Estimate at Completion
(EAC)
$
92,776
Estimate time to
complete
4.79

21PROJECT MANAGEMENT
4.3.2 Timeline reporting
Past time period
Milestones Approved plan Actual
progress
Variances Causes
Charter sign off Approved Completed No Sign the charter by
sponsor and manager
Initiation of the
proposed system
Approved Completed No Project manager
initiates the project
needs
Current time period
Milestones Plan until next
report
Risks before
next report
Issues before
next report
Changes to be
approved
Planning of
proposed system
Gathering the
requirements of
the system
Lack of project
understanding
Business case is
not provided
Planning
changes
System analysis
phase
Preliminary
conceptual
design
Lack of
understanding
of the system
Failure of the
design of
system
System
analysis
changes
System testing
phase
Identifying the
system tools
Lack of testing
needs
Failure in
testing the
system
Testing
changes
Risk
management
phase
Risk
management
plan
Lack of
understanding
of the project
risks
Poor system
performance
Changes in the
risk register
Future time period
Milestones
Plan to
Completion
Risks After
next Report
Issues After
Next Report
User training
phase
Training to the
employees
Training is not
provided
The employees
are not attended

22PROJECT MANAGEMENT
the training
program
Closure phase Final draft of the
project
Final project
plan is not
prepared
Sign off the
project report is
not done.
5. Risk management
5.1 Risk identification
The risks are to be identified by means of qualitative method where the impacts as well as
probability of the risks are measured. Following table shows the risk register of the project:
Risk
Description
Impact Category Probability Impact Score
(P*I)
Mitigation
strategy
Failure of
the system
Project
delay
Business 3 4 12 The system should
be maintained
properly.
Lack of
project
training
Project
delay
Business 4 4 16 Training should be
conducted on the
employees those
have lack of
technical
knowledge.
Lack of
project
reporting
Project
delay
Business 2 3 6 All the project
reports should
require to be
prepared.
Security
risks
Project
delay
Security 3 4 12 Privacy should
require to be
provided to the

23PROJECT MANAGEMENT
system.
Unchanged
scope
statement
Scope
creep
Business 4 3 12 Changes should be
approved.
Failure of
project
testing
Project
delay
Business 3 3 9 User testing should
require to be done.
Overrun of
the project
cost
Project
delay
Cost 3 4 12 There should be
proper estimation
of project budget
based on all
resources required.
6. Quality management and project closure
6.1 Quality tools
Based on this project plan, identified project quality tools are as follows:
Quality audit: This tool is used to check the quality of the proposed management
information system which helps to determine defined system processes and result based
assessment criteria.
Brainstorming: It is used to find the conclusion and result for the specific system
problems by collecting of ideas contributed by the project team members.
Cause and effect diagram: It is a tool for categorization of the project causes and
problems for identifying the root causes of each project related problems (Kloppenborg 2015,
pp.307).

24PROJECT MANAGEMENT
Project
deliverables
Work processes Quality control
activities
Quality
assurance
activities
Quality roles
and
responsibilities
Feasibility study Perform
technical
feasibility of the
system
Brainstorming Quick generation
of the project
ideas to identify
the project gaps
Technical lead,
identify the
system functions
Specifications of
project scope
Project scope
statement
Project Charter Identify the
needs of the
system in the
business
organization
Project manager,
plan and execute
the project plan
as per the system
requirements
Preliminary
conceptual
design
Quality metrics Flow chart Visual model of
the flow of work
System Analyst,
analyzing the
requirements of
the proposed
system
6.2 Change management
Description of the
change
There is required to make changes into the project schedule and cost.
Why needed Both the schedule and cost is exceeding from its planned value.
Impact on the project
scope
Scope creep
Impact on deadline
dates
Project delay
Impact on budget Over budget of the project cost
Impact on risk There is schedule and cost risks in the project plan.
Impact on team Losses of the project resources
Date approved 17th August, 2019

25PROJECT MANAGEMENT
Project Manager (Please fill)
Sponsor Johnny Smith
Customer Andy James
7. Project closure
Project: Redesign the management information system for Burger King
Date: 17th September, 2019
Prepared by: Project Manager
 All the project activities are taken care of.
 The project work is done as per the project requirements.
 Feedback is collected from the project client.
 Your teammates are provided support to the project.
 You have followed all closure processes of the company.
Approved for closeout: Project Board
Project Manager: (Please fill)
7.1 Transition plan
Project: ____________________ Date: __________ Prepared by: _______________
Current Project Situation: The project is done properly as per the project schedule and all the
project team members performed their responsibilities perfectly.
Schedule of Remaining Work: As per the project needs
Risks Remaining: Schedule risks
Recommendations to Users of Project Deliverables: Documentation of the project work Training related to handling the technical system and equipments
Relevant contacts:

26PROJECT MANAGEMENT
1. Project Manager
2. Technical Lead
3. Functional Lead
7.2 Close procurements
In order to manage the procurement closure, the project manager is required to handle the
project deliverables to the project customers, passing the project documentation to business
organization, cancel the contracts of the project suppliers, releasing of the project staffs and
technical equipments and inform the project stakeholders related to project closure (Kloppenborg
2015, pp. 424)
7.3 Knowledge management
The knowledge is captured into the project by providing training to the staffs and system
users so that they can get knowledge and skills to handle the system (Kloppenborg, Anantatmula
& Wells 2018, pp.506).
7.4 Lessons learned
1. The lessons learned from the project charter are to schedule the project plan and use of
project management tool to schedule each of the project activities.
2. Identification of the project risks by means of project risk management plan.
3. Communicate with the project stakeholders by means of communication management
plan.
7.5 Customer feedback
Project Customer Feedback
Project: Redesign Management Information System for Burger King
Item Rating (1=poor;
2=OK;
3=Excellent)
Comments – how can we improve?
Quality of deliverables 3 There is documentation of the project
related work into the project reports.

27PROJECT MANAGEMENT
Compliance with
schedule
2 There is proper scheduling of the project
activities.
Budget performance 2 There is proper estimating of the project
cost.
Stakeholder relationship
management
2 There is proper stakeholder engagement
for project success.
Communication
management
3 There is proper communication and
interaction among the project team
members.
Overall rating 12
Outstanding issues: There are issues related to project cost as it gets over budgeted.
8. Conclusion
It is concluded that the project work is succeeded if the project manger can perform a
proper project scheduling for each of the project activities. Each of the activities should schedule
with strict start and finish date. The project resources are assigned with activities and on time
they have to finish it to achieve profitability and success into the project. The risks are identified
so that t is prevented on time and each of them is required to overcome on time before it can
provide huge influence on project success. Each of the project team members communicate with
each others to meet with the project needs.

28PROJECT MANAGEMENT
References
Kloppenborg, TJ 2015, Contemporary project management, 3 edn, Cengage Learning, Stamford,
CT.
Kloppenborg, TJ, Anantatmula, V & Wells, KN 2018, Contemporary Project Management, 4
edn, Cengage Learning, Boston, MA, USA.