Team Members

27NMP1
8
27NMP5
6
27NMP6
2
27NMP7
4

Lavanya Baskaran
Mayank Ashok Mirani
Punit Pandia
Varun Kalra

Husky air assignment Pilot Angels

Stake Holder Analysis
Stakehold
er

Interest

Influenc
e

Potential
Conflicts

Role

Objectiv
e

Strate
gy

Project
Champio
n

Provide
approvals
and
authorize
payments
for the
project.

To open
open
commu
nication
.

L. T. Scully

+1

Competition
for
resources
especially
cost with
other
managers.

Alma
Coleman

-1

As
Foe
Experienced
personnel,
Alma had
been using
a Manual
System. She
is not
pleased that
this project
was chosen.

Has a
negative
interest in
the
projects
success.

Maintai
n open
commu
nication
, use
project
sponsor
s

influenc
e as
necessa
ry.

Tim
Williams

+1

Resources
not made
available as
promised by
functional
managers.

Project
Manager

Lead and
Manage
the
project so
that it
achieves
its MOV.

Work
closely
with
project
stakeho
lders
and
project
team.

Sitaramin,
Yan and Pat

+1

Users
affected by
Project
change may
resist
change by
withholding
information.

Sitarami
n, Yan
Systems
Analyst,

Provide
expertise
to
complete
the
project
work

Support
project
team
with
adequat
e
resourc
es while
minimiz
ing
distracti
ons.

Pat
Network
specialis
t

Volunteer
Pilots

+1

Volunteers
can abstain
from
transporting
patients in
case of lack
of time or
resources.

Support
er

Provide
the
means for
transporti
ng
patients,
organs or
medical
personnel

Plays a
vital
role in
the
overall
success
ful
implem
entation
of the
pro

Passengers

+1

Patient

Advocat

Strong

Keep

conflicts
e
with Medical
personnel.

interest in
regaining
the
patients
health.

coordin
ating
with
other
stakeho
lders,
as and
when
request
ed by
them.

Project Name
The project name is Virtusa.

Project Team
The group that will be implementing the project is our team which includes
Lavanya Baskaran, Punit Pandia, Mayank Mirani and Varun Kalra.

Team Members
Lavanya Baskaran, Punit Pandia, Mayank Mirani and Varun Kalra.

Project Description
Our team is seeking to develop a database backbone for the Husky Air
Company. In the following proposal, our team will attempt to outline and
explain what our proposed solution for the revamp of their current data
storage system. Our goal is to create a database system that will keep Husky
Air's day-to-day operations more efficient and effective. Database systems
organize and catalog data to better aid in using information effectively.
Husky Air's current data organization system is ineffective for the changing
market and to keep their company competitive; revamping the back end
operations will help move them forward.

Measurable Organizational Value (MOV)

The Desired Area of Impact
First and foremost, our interest is in helping Husky Air in their Operational
flow. Improvement of operations describes maintaining a system that will
create a lowered cost and overall improvement in task completion. Since
Husky Air's current system has proven to be less-than useful for the changing
demands of today's electronic-focused world, our new system will focus on
improving their operations. Our next concern is the improvement of the
Strategic element of their business. To expand and grow, a company should
move forward technologically regularly. Companies that don't use
computerization in their business plan are prone to being market-starved
against companies that will. Tying into this, improving the Strategic area will
improve the financial area as well. With improved growth, a company would
naturally see an increase in revenue. Plus with the reduced cost of
maintaining a lower profile file management system, profit margin will also
see an increase. Customer relations will likely improve with a more
streamlined file system as entering and retrieving data will allow for quicker
turnaround times and improved accuracy. Finally, we can examine the
improvement for Social concerns. However, the focal point of this project is
to improve the Operational concerns of the company as that is where we will
see the largest benefit.

Desired Value of the IT Project

As the focus of the project is to improve operations, in general we are trying
to lower time taken to handle requests for data entry or retrieval. With a nondatabase system, much time and energy is lost in trying to maintain and use
data. Using physical data storage requires a manual organization system and
having to peruse through file cabinets or bookshelves of paperwork to find
one piece of information or enter a new piece of information is inefficient in
today's computerized society. As such, in the interest of making a more
effective operation for Husky Air, computerizing their data storage will
remove the need to physically organize data. Database software like SQL
Server and MySQL are designed to collect and manage data on behalf of the
user, freeing up their time. In addition, time lost on in accurate data entry
due to errors in human organization of information can be averted with a
computer data storage system as a computer data storage system reduces
the number of variables a user must know about the data to organize it
(organization on the computer level can be preprogrammed and thus

blunting the risk of erratic data entry). Time lost is money lost and in the
business world, any gain in time improves the possibility for improved
earnings.

Appropriate Metric
By implementing a pilot supply database it would be possible to increase
productivity by at least 50%. This is due in part because of the ability to
make certain tasks automated. For instance, when certain supplies become
low, it would be possible to automatically order more to keep inventory up. It
will also allow the workers to see how many items they have in inventory and
be able to work accordingly. Also, by implementing a user-friendly interface
the users will be more likely to adopt the system and make use of its
beneficial qualities.

Set Time Frame for Achieving the MOV

Once the data is added to the database and set up then it will be possible for
the workers to be trained to take advantage of the system and begin to feel
the beneficial effects of the system at least 1-2 months after its
implementation.

Summarize the MOV

By implementing this system, there will be a noticeable increase in
operational efficiency. Workers will be able to access information more
efficiently than was previously possible. It will also be possible to improve
operations by automating inventory orders. The system will provide a
productivity increase of at least 50% after the workers have been trained to
use the system. The project will be successful if the users are trained and are
willing to use the new system.

Deliverable Structure Chart (DSC)

Use Case Diagram

Deliverable Definition Table

Scope Change Process

When a change to the scope of the project needs to be changed, the person
making the change should enter a request. The formality of making a
change request is important because multiple factors could be affected. The
group of people, which should include the project manager, who review the
request make sure that each change will not conflict with other changes that
have been recently requested or changes made in the past. Each request
should be given a priority to ensure that important changes are made ahead
of less critical changes. The group also determines if a change is necessary
or not. The budget and schedule of the project could determine whether or
not the change should be made.

When a change is requested, a form should be filled out so the group who
approves changes has all the necessary information to make the correct
decision. The form also provides consistency and understanding among the
project team. The form should look something like the table seen below.

Scope Change Request Form

Requestor Name:_________________________ _____ Todays
Date:___________________________

Request Number: ___(auto generated)___

Implementation Date:____________________

Short Description:
________________________________________________________________
Full Description:

Business
Reason:______________________________________________________________________
_

Test Plan:

Backout Plan:

Approved? Y / N

Authorized by:_______________________________________________
Date: ____________________

Scope Change Request Log

A change request log should be kept by the group who reviews changes. A
log keeps track of what changes were previously made and data pertaining
to those changes. An example is seen below.

Reque
st No.

Requestor

Chang

Priority

(1= high,

Date

4 = low)

Chang

Priority

(1= high,

Date

4 = low)

Approve
Approver

d?

Short Description

Reque
st No.

Requestor

Short Description

Approve
Approver

d?

Detailed Project Plan

The costs for each resource are as follows:

Database Specialist

$35.00/h

Programmer

$35.00/h

Project Team

$25.00/h

Project Manager

Systems Analyst

Coordinator

$30.00/h

$35.00/h

Client of project

Project Sponsor

Client of project

Key User Pilots

Client of project

Resources have been assigned within the WBS file (MS Project file). Some
tasks have been linked and some labeled as start-to-start.
The project will start 6/8/15 and is scheduled to end 49 days later. The end
date is 8/15/15. Most steps through the implementation phase are on the
critical path. The close and evaluate phases are not on the critical path. The
project manager and project team are over allocated. I leveled the project
manager, but since the project team is comprised of multiple people, the
work can be split up. Another systems analyst might have to get involved in
the project to level out the work assigned to that position.

Work Breakdown Structure

Work Breakdown Structure

Pilot Angel Project
Initialize & Conceptualize Phase 1
Business Case
Project Charter & Plan Phase 2
Charter and Plan
Milestone: Planning Complete
Execute & Control Phase 3
Analysis
Collect Informatin & Requirements
Admissions & Requirements Plan
Design
System Design Plan
Interface Design
Milestone: Design Complete
Construction
Database Creation
User Interface Creation
Program Operational Fuctions
Pilot Records
Plane Records
Patient & Passenger Records
Flight Records

Conclusion
The project scope defines how the Pilot Angels project will be completed. It
specifies deliverables and who is responsible for completing and approving
each one. If changes need to be made to the deliverables, a scope change
process is in place, including a standardized request form and request log, to
manage the changes.
The work breakdown structure breaks up each phase into detailed tasks.
Each task has a resource, completion time, and defined deliverable.
Milestones have also been included. The project budget and schedule have
also been taken into consideration.