Running head: PROJECT SCHEDULE

Project Schedule
CMGT/410

PROJECT SCHEDULE

2
Project Schedule

Tylers Cable Company (TCC) developed a project schedule for the management
of the new system. This schedule will include when each activity will occur, what has
already occurred for this project, and the order in which the activities will occur. Included
in the project schedule is the Business Requirements Document (BRD) and the Work
Breakdown Structure (WBS).
Business Requirements Document (BRD)
Problem Definition
The main problem at TCC involves their communication and data system. The
defining issue is that TCC relies heavily on a paper system for their daily functions and
billing.
Stakeholders and Their Roles
Tyler Hobson is the manager at TCC and will serve as the project data manager;
making sure that the new data system is compatible with TCCs. He has been with TCC
over the past ten years and he works closely with human resources and the database
operations. Cardell White works in sales and collections working closely with accounting
and with human resources on the companys contracts. Cardell will take on the budget
for the project making sure the team stays on budget. Sue Graham works in customer
services and does trouble shooting for the company. She has also been involved in
focus groups for TCC resulting increased customer satisfaction. Sue will help arrange
the training for TCC through the Penguin Data System. Cherry Meers works in
accounting and payroll. Her job is invaluable to the company. She also has a
background in customer service, corporate training, human resources, and IT

PROJECT SCHEDULE

networking. Cheery will take on the WBS of the project. Melissa Andrus is a Senior
Project Analyst managing projects for the company and keeping up with compliance
issues on both a state and national level. Melissa will serve as the project manager.
Scope
The project manager, Tyler, has set up the scope of the project so that it can be
completed within the three month timeframe. With 160 employees, it is important that
everyone be trained on the new information system once it is implemented. This three
month time frame will allow the project team to train on the new data system and work
with Tyler and the rest of the information technologists at TCC to implement the new
Penguin Data System. Once the project team has been trained, then Melissa would
provide the board and stakeholders a PowerPoint presentation on the new technology
at TCC. With the boards approval, the training for TCCs 160 employees can
commence. This training and schedule is being put together by Sue; the budget has
been approved for all of TCCs employees. Cherry will make sure the project areas are
flowing smoothly and according to the budgeted scope. The budget is being tracked by
Cardell and will be reflected in the PowerPoint presentation.
Scope Creep
TCC has to have a project scope and be able to stick to it. They want to prevent
the problem of scope creep where a company can go over their timelines and budgets.
Penguin Data Projects goal in aiding TCC is to prevent such occurrences. The objective
is to still provide quality customer service but not every customer demand can be met at
once. This will take time to transition to all customer requests. TCC wants to please all

PROJECT SCHEDULE

customers but scope creep can also occur when trying to meet extra demands that are
not a part of the original project scope.
Business Objectives
TCC objective is to improve overall company communication. They will be
integrating a multi-faceted online system that will have capabilities to manage all of their
multiple sites and locations by utilizing a database. With the help of the Penguin Data
Project; TCC can streamline its communications with this type of system. All locations
will be linked to a centralized online unit and with the database all information will be
categorized together.
Available Resources
The Penguin Data Project and TCC will take an inventory of all available
resources on hand to evaluate what is acceptable for the upgrade to the new system.
Savings costs by not having to purchase equipment already on hand are valuable. The
purpose is to utilize whatever possible to have a successful implementation. With an
online system there computer processors must be high speed and the database has to
be large enough to handle all of the multiple company locations. The Penguin Data
Project will verify that the systems hardware is acceptable in handling the upgrade and
if it isnt recommendations will be made for a more suitable replacement.
Constraints
TCC will have a lot of constraints when implementing penguin data. One will be
able to get penguin data to be used on all devices for technicians. Since TCC is
switching from paper to paperless it will be a hard task to make sure all mobile devices
for all employees are able to log into the server and submit the work orders they did for

PROJECT SCHEDULE

today. Another constraint that the company will have to incorporate with is making sure
that our company that submits paychecks is able to communicate with the penguin data
program to create paychecks for the employees in TCC. One of the most important
constraints that cannot be over look is that making sure the budget is correct for using
penguin data. That means by making sure the estimate time of completion and budget
are correctly analyzed to make sure that TCC is not going over budget and affecting the
overall quality and outcome of submitting and using penguin data.
List of Assumptions
There are a lot of assumptions that TCC can endure in implementing penguin
data into the company. One assumption is that it could take time for everyone to be on
board on using the program. That means employees will be hesitate to use the
program, due to it being new and employees not wanting to try a new system. Another
assumption would be that penguin data would crash the system and not be able to
improve the work effort for the company. By using penguin data the main goal is to get
rid of a paper in the company and use a paperless system to incorporate less work for
the company and too make work easier for the whole company. Another assumption
would be that the program could go over budget and not meet the completion date. This
is one of the most important assumptions dealing with implementing a new project for
the company. To make sure this is met the project manager will keep in contact on a
weekly basis making sure that the project is still on track to be finish at the right
completion time. Also the project manager needs to let the stakeholders know if any
unplanned expenses are needed to finish the penguin data implementation to make
sure it has great quality and able to use after the completion date.

PROJECT SCHEDULE

Specific Requirements
There are a lot of requirements needed to make sure that penguin data is
implemented correctly into the company. One is making sure that penguin data is
compatible with TCC's system. That means for one that all browsers that TCC will need
to be defaulted to either Google Chrome or Firefox. The reason is because the only way
to use and access penguin data is by using chrome or fire fox. To make sure this is
done correctly the project manager will need to make sure all servers on the companys
network to be switch to fire fox or chrome browser. TCC will also need to make sure to
have internet access and a VPN network to make sure all communication is locked out
from hackers or other intruders that could take information from the company and hurt
and the employees information saved on the network. Wireless internet and access
points are needed to make sure the whole company is able to access penguin data
wirelessly thought TCC. Also make sure all phones are able to access penguin data,
and incorporated webinar training for the company to learn how to use penguin data.
That means making a power point presentation about penguin data and showing the
features to the employees about how important and crucial using penguin data is.
Functional Requirements
Functional requirements of the new system for TCC will include applications that
will capture data and produce specific reports, such as a Comparative Analysis and
Trend Analysis. The Trend Analysis will create reports that will compare product
profitability and customer profitability. The application will also report monthly details of
TCC customers and sales analysis by location. A Daily Activity Report will allow users to

PROJECT SCHEDULE

view a summary of monthly sales, collections, disbursements, receipts, inventory,

monthly goals versus actual, accounts, and lead times.
Non-Functional Requirements
The new system will run seven days a week for 24 hours each day. The system
will link into an online help desk. This project must be completed within three months of
the development of this system. The project team will consist of five team members.
The testing of the system will be completed by someone other than the programmer.
The system must also be capable of running on operating systems with Windows XP,
Vista, and Mac computers.
Conclusion
The information included in the BRD details the new system for TCC and
includes the needs and expectations of TCC and its customers. This BRD is the
foundation for the project deliverables and the inputs and outputs that are associated
with the implementation of the new system.

PROJECT SCHEDULE

8
Work Breakdown Structure (WBS)
PENGUIN DATA SYSTEM
1

MANAGEMENT
1.1

Planning
1.2

Planning
1.1.1

Cost and Scheduling

1.1.2

Project Team
Meeting
1.2.1

Create Scope
Statement
1.2.3

Technical
Planning
1.2.4
Scope
Management
1.1.3

Task
Management
1.1.4

Communications
1.1.5

Human Resource Management

1.1.6

Space and Facilities

Requirements
1.1.7

Risk Management
1.1.8

Integration/
Development
1.3

Develop Project
Plan
1.2.5

Business
Requirements
1.2.6

Project Team
Meeting
1.3.1

Verify and Validate

User Requirements
1.3.2

Evaluate Resources
1.3.3

Installation
1.4

Develop
Installation
Plan
1.4.1

Site
Preperation
1.4.2

Install at
Locations
1.4.3

Test Software
for Upgrades
1.3.4

Project Plan
Approval
1.2.7

Procure
Hardware/Software
1.3.6

Perform Integration
Testing
1.3.7

Procurement
Management
1.1.9

Install Development
System
1.3.8

Quality Management
1.1.10

User Training
1.3.9

Hardware
Maintanance
1.5.1

Software Maintanace
1.5.2

Control
1.6

Project Management
1.6.1

Team Project Status

Meeting
1.6.2

Risk Management
1.6.3

Update Project Plan

1.6.4
Test System
1.4.4

Design the
System
1.3.5

Maintanance
1.5

CLOSEOUT
1.7

Audit
Procurement
1.7.1

Document
Learning
1.7.2

Organize Files
and Documentation
1.7.3

Get Final
Acceptance
1.7.4