1. Group 5’s Project Plan
(12/9/2015)
Ka Chun Chan
Michael Lim Meng
Bingyue Xu
Aaron Huang
Anthony Mottla
Project Summary:
Our project is to implement a way for people to order their items manually while they are inside
the store through a tablet. They will be able to do this either by manually ordering from a table or
if they want to place an order to go at the front desk. This idea is for customers to have the ability
for themselves to order without having to go to the front register. The organization which this
project will be used for is at, Buccini’s Mr.Subs at 64 Billings Rd, Quincy Ma. Our main contact
person will be our group member, Michael Lim Meng who currently works there. The group
members who will be working on this project will be, Ka chun Chan (KC), Michael Lim Meng,
Bingyue Xu, Aaron Huang, and Anthony Mottla whom are part of group 5.
2. 1
Problem Statement:
The Buccini’s Mr.Subs has been using “Food Tech Inc.” as its cashier and delivery system
for many years. At the beginning of the last fall, The Food Tech Inc. announced that the whole
cashier and delivery system will end mainstream support on December 31, 2015 and end
extended support on December 31, 2016. That means Food Tech Inc. will not fix any
vulnerabilities for the system and it would impact all of Buccini’s Mr.Subs’s business.
There has been a weak business continuity plan for the machines or system if they are
having issues and the dealer of Food Tech Inc. said that they will cancel the same day
maintenance support in December 31, 2015. That means Buccini’s Mr.Subs would need to wait a
day or more if the server down. Most importantly, Buccini’s Mr.Subs will need to pay additional
money for the extended support, but they are not including vulnerabilities fixes. Since the cashier
and delivery system are important for Buccini’s Mr.Subs, management had to begin seeking
viable alternatives to replace and upgrade the current cashier and delivery system.
Mission Statement, Goals, and Objectives
Project Mission
To enhance the ordering system through the replacement of the current outdated
system with the new, easily adaptable and more efficient hardware and software solutions, which
would:
Implement a way for people to order their items more efficiency.
Apply the tablets PC (For example, iPad) on each table for customers to place orders by
themselves.
Project Goals
· Grasp an opportunity to advance the ordering system and provide effective support to all
the employees and customers.
· Enhance the existing ordering hardware with the new tablets to improve overall efficiency.
3. 2
a. Within a time frame of five months and
b. Within a budget of $31,500
1) Salary cost for the implementation team, $11,500
2) $20,000 for purchasing the tablets and other accessories
· Become a successful restaurant using a tablet ordering system.
Project Objectives
· Complete the planning and requirements gathering stage within the first month from the
project start date.
· Meet deadlines for the deliverables throughout the project’s life cycle.
· Closely monitor the project’s performance and effectively apply any change to the
ordering system.
· Within two months of the project, make sure all the employees master the steps of the new
ordering system skillfully.
· Successfully convert the old ordering system to the new solution.
· Analyze the customer satisfaction and compare the requirements of the users to rate the
success of the project. In detail, examine:
a. Interface
b. User-friendly system
c. Customer satisfaction
· Maintain both ordering systems until December 31, 2016 and after this date use only the
new ordering system.
Project Strategy
SWOT Analysis
In order to better understand the gains and risks of this project, analysis of environmental
factors specific to the business must be conducted. Factors internal to the business will be
considered strengths and weaknesses, and factors outside the business will be called
opportunities and threats; this is called SWOT analysis. SWOT analysis is important to
understand the resources and capabilities this project will have.
Strengths
· Good location for consumer testing.
· Small constrained environment.
o Both the physical location and the environment needed to develop the program.
Weakness
· No current database for the program.
4. 3
o A new database has to be developed for the program, that means resources have to be
set aside for the database.
Opportunities
· Increased company appeal.
o Making the business look more appealing through adapting new technology.
· Increased business and revenue.
· Marketing a new software to other businesses.
o Selling or leasing the software to other businesses in order to gain a new source of revenue.
Threats
· There is the potential threat that neighboring restaurants will adopt and implement this
idea before this project is finished.
o To address this, we have to run them out of business, or finish the project on time.
· The software being developed may become outdated.
o Address this by hiring another person onto the team to ensure the software is
continuously maintained and possibly improved upon.
· Tablet hardware may become outdated.
o To address this, the software will have to work in all sorts of environment, from
phones to computers.
· There may be bugs with the software.
o Address by creating a stable version of the software to be used. Any patches or
improvements done will have to be tested in an environment outside the restaurant before
implementation.
Risk Analysis
Risk Impact Probability Consequences Decision
1 Possible bugs
and glitches
M H -Unable to use or
start the program.
-Application may
have to be
reworked or
restarted if bugs are
persistent.
Ensure there is a
stable working
version of the
program. Any
patches or
improvements will
be added in testing
environment.
2 Delay in meeting
deliverables
M L -Project completion
becomes delayed.
Increase work
hours, allow for
overtime if the
budget allows it.
5. 4
Possibly hire
another member to
the team.
3 Outdated
Hardware
L L -Application has to
be updated to
support the new
hardware.
Create the
application to be
flexible so that it
can adopted onto
other technology.
4 IT Team Quits M L -The project
becomes stalled.
-We have to find
new IT team to
handle the software
development.
Find an immediate
replacement
member for the
team.
5 Undeveloped
Database
H L -The database does
not connect to the
application.
-Transfer resources
to further develop
the database.
6 Over-budget H L -Not enough of the
budget to complete
the other tasks.
-Reevaluate budget
plans and see where
cuts can be made.
Internal Analysis
The importance of doing an internal analysis of the project is to better understand the
situation and environment the project will be developed in. Knowing the strengths and
weaknesses of the business and the project itself will allow the team to know its advantages and
disadvantages.
The location of the business Buccini’s gives the IT team a way to test its beta applications
before its launch. Because Buccini’s has an environment in which customers can sit down and
order, it is possible to section off certain parts of the restaurant to allow the testing of the newly
developed application. By sectioning off parts of the restaurant for testing, the team can gather
real world data on the application. They can also gather reports from customers themselves
which will help them improve the application.
Because the project is on a smaller scale, this allows the overall project to have more
focused goals. The project is developed to work with machines that use iOS so the development
environment can be any environment.
6. 5
The database currently for Buccini’s maintains inventory and checks sales. The database
will have to be modified so that orders placed on the application will show up on the database, or
at least allow the application to have information from the database.
External Analysis
Aside from the strengths and weaknesses this project has, opportunities and threats may
arise as the project goes on. Because of this, it is important to also analyze the environment
outside the business, such as market competition and possible opportunities.
Because there are not a lot of restaurants that have adopted this model of service, by
developing the application, Buccini’s will become more appealing in aesthetics and its technical
side.
If Buccini’s wishes to sell or license their application to other businesses, it will open up
a new source of revenue for Buccini’s. To do this, the application has to be flexible in adopting
new databases, and also accessible.
Because application development is never perfect, the application being developed for
this project will come across some bugs. To iron out the bugs that may appear, QA testers will
have to be hired to check the application. Also, the application will have to be tested on a small
number of customers to get their feedback as well.
Project Deliverables
The project deliverables are tangible or intangible objects to be delivered to the customer
throughout the duration of the project. These deliverables include:
● A project charter to identify and outline the scope and requirements of the project.
● A work plan document to outline the specific work breakdown structure, schedule, and
budget of the project.
● Modifications to the current database so inventory, ordering, and sales all work
seamlessly with the new software.
● Initial version of ordering software for tablets capable of running iOS.
● Training program and procedures for employees to learn new software after the first
month.
● Reports and analysis on employees’ feedback to be considered for the next phase of the
software.
● Updated version of ordering software capable of running on other devices in addition to
tablets, such as computers and smartphones. To be implemented on tablets in designated
testing section.
● Reports and analysis from both employees’ and customers’ feedback for the final version
of the software.
● Completed project: A customer friendly, fully operational ordering system implemented
on all tablets in the restaurant by December 1, 2015. It must allow customers to place
orders while keeping track of inventory, orders, and sales on the back end.
7. 6
● Final evaluation document detailing the improved ordering system and customer
satisfaction.
Project’s Schedule
Group 5’s WBS
0 Group 5 Project
1 Evaluate and Recommend
1.1 Evaluate Current Hardware
1.2 Evaluate Current Software
1.2.1 Evaluate User Interface
1.2.2 Evaluate Database Management
1.3 Milestone
2 Develop Project Charter
2.1 Define Scope
2.2 Define Requirements
2.3 Identify High-Level Roles
2.4 Develop High-Level Budget
2.5 Identify High-Level Control Strategies
2.6 Review Meetings
2.7 Revise Project Charter
2.8 Milestone
3 Planning
3.1 Develop Work Plan
3.1.1 Develop WBS
3.1.2 Develop Project Schedule
3.1.3 Develop Budget
3.2 Develop Project Control
3.2.1 Develop Communication
3.3 Finalize Project Plan
8. 7
3.4 Milestone
4 Design
4.1 System/Interface Design
4.1.1 Design Content
4.1.1.1 Design Layout
4.1.1.1.1 Create Home Menu
4.1.1.1.2 Create Tabs for Categories
4.1.1.1.3 Assign Items to Category Tabs
4.1.1.1.4 Assign Prices to items
4.1.1.1.5 Assign Pictures to items
4.1.1.1.6 Add Descriptions to items
4.1.1.1.7 Add ingredients to items
4.1.1.2 Implement Company’s Logo to layout
4.1.1.3 Design Database
4.1.1.3.1 List Items and Prices
4.1.1.3.2 Establish relationship with database and applications
4.1.1.4 Design User Interface
4.1.1.4.1 Design application thumbnail
4.2 Milestone
5 Installation
5.1 Install Hardware
5.1.1 Install Docking System for Ordering System
5.1.2 Install Cabling
5.2 Install Software
5.2.1 Internet Establishment
5.2.2 Update Software
5.2.3 Security System
5.2.4 Payment Methods
5.3 Milestone
6 Testing
6.1 Test Phase
6.1.1 Test the System/Interface
6.1.1.1 Test Usability of System
6.1.1.2 Test Usability of interface
6.1.1.3 Test for bugs and glitches
6.1.1.4 Test for Quality
6.1.1.5 Test for Responsiveness
6.1.2 Gather User’s feedback
6.1.2.1 If Negative Feedback
6.1.2.1.1 Determine Level of importance
6.1.2.1.1.1 Low Priority
6.1.2.1.1.1.1 Fix if deadline/budget allows
6.1.2.1.1.2 High Priority
6.1.2.1.1.2.1 Fix immediately
9. 8
6.1.2.2 If Positive Feedback
6.1.2.2.1 Optimize current application
6.2 Milestone
7 Training
7.1 Develop Training Manual
7.1.1 Provide Appropriate Training
7.1.1.1 Online Training
7.1.1.2 Instore Training
7.1.2 Train Managers
7.1.3 Train Employees
7.1.3.1 Full Time
7.1.3.2 Part Time
7.2 Milestone
8 Control
8.1 Project Case Meetings
8.2 Risk Management
8.3 Update Project
8.4 Milestone
9 Close Project
9.1 Conduct and evaluate project’s success
9.2 Milestone
Activity Description Estimated Duration
(Days)
Predecessor
A Conceptualize and
Initialize
3 None
B Develop Project
Charter
27 A
C Planning 17.5 A
D Design 8 A
E Installation 2 B,C,D
F Testing 20 E
G Training 13 E
H Control 25 E
10. 9
I Close 1 F,G,H
Arrow on the Node Network Diagram (AON)
Possible Paths Paths Total
Path 1 A+B+E+F+I
3+27+2+20+1
53
Path 2 A+B+E+G+I
3+27+2+13+1
41
Path 3 (The Critical Path) A+B+E+H+I
3+27+2+25+1
58
Path 4 A+C+E+F+I
3+17.5+2+20+1
48.5
13. 12
Control and Evaluation
To ensure that the efforts of the implementation team are not wasted and that the envisioned
performance is achieved, four main stages methodology was devised to establish, monitor and
control the issues that might happen during the implementation of the system. Those stages are:
· Budgeted Cost of Work Scheduled (BCWS)
· Control procedures for
14. 13
o Cost
o Quality
o Risk
BCWS
The physical work scheduled, plus the authorized budget to accomplish the scheduled
work.
a. Within a time frame of five months and salary cost around $11,500 for the
implementation team
b. Within a budget of $20,000 for purchasing the tablets and other accessories
Cost Control
A series of steps that the implementation team uses to maintain proper control over its cost.
· Budget. Change control over the project estimated money that spend on each part while
implementing.
· Decision. Knowledge of effectively and reasonably designs the cost control plans used for
choosing different kinds of tablets and software.
· Organization. Knowledge of organizing the team according to the results of the decision.
· Implement. Knowledge of implementing the project to all the sections.
Quality Control
Focus on assuring a well-designed system that would work stable in the restaurant. The
effectiveness of the system need to be ensured.
· Network. Change control over the network status with implementation.
· Responsibility. Change control over the physical deterioration for the tablets and other
accessories.
· Targets. Aims that will be carried out through to the end. For example, both the hardware
and software must meet the needs for the restaurant.
· Supervision. Rationalize all the work.
Risk Control
The process to deal with problems once the project delay in meeting the deliverables,
over-budget, or poorly performing.
· Stability. Knowledge of controlling some possible bugs and glitches, we want to make sure
that there is a stable working version of the program.
· Completion. Change control over different deadlines for different parts of the project.
· Loyalty. Knowledge of methods that used for the team cohesion.
Organization
15. 14
Buccini’s Mr. Sub is a privately owned restaurant with a small staff of 15 employees.
Because the staff of Buccini’s is split into different groups based on their function, the
organization structure of the project team will mainly be functional, with some cross-
functionality. Dividing the project team into smaller groups who will focus on their specific
tasks will allow the Buccini’s business to complete the project in a timely fashion. The IT
team will mainly be focusing on the development and testing of the application, while the
restaurant staff will be assisting with the testing of the application; while also focusing on
training employees on using the application.
Work Distribution Table
