Tech Assessment & Acquisition Final Project Paper - WordPress.com

stuckwarmersMobile - sans fil

14 déc. 2013 (il y a 3 années et 4 mois)

80 vue(s)

Wentworth

Learning System Search

A Work In Progress










By Charles Angotto & Ryan McDowall


Table of Contents




I.

Business Need
…………………………………………….
page 3

II.

Project Charter
…………………………………………
...
page 5

III.

Project Sponsor
…………………………………………
..
page 7

IV.

Project
Manager
………………………………………….
page 8

V.

Project Plan
……………………………………………

page 9

VI.

Project Schedule
………………………………………….
page 10

VII.

Scoring Matrix
…………………………………………
.
.
page 11

VIII.

Project Team
…………………………………………
..
.
page 12

IX.

Negotiation Strategy
………………………………
…….
page 13


X.

RFP
……………………………………………
………..
page 15

XI.

Benchmark/Pilot
………………………………………….
page 22

XII.

Vendor Sales Team
……………………………………….
page 23






Business Need

1.

Context

Wentworth Instit
ute of Technology provides
great resources for its faculty, staff,
and student body.
There are

multiple ways for members of all party’s to delegate
work and or information to one another. For its current email service, Wentworth
uses
Microsoft Outlook.
This software is an effective and convenient way for the
Institute to communicate with the whole
faculty and student body.

This is one of
the few effective

ways to issue alerts to let everyone know what’s occurring at
any given time on campus

or in classes
. In addition to Microsoft Outlook
Wentworth students and professors have access to
Blackboard
, a

website that
allows professors to issue work, quizzes and much more to students. Blackb
oard
is said to be a great learning tool just as long as you
keep a close eye what needs
to be done and when it needs to be done by. Deadlines can be set by the profess
or
at his or h
er digression and once the dead
line is missed you as a student are
usually out of luck. With the life of a college student
being so stressful it’s
important
to keep organized and

have a constant reminder

of everything that is
due.
Thus being
said it would be wise at this point in time for Wentworth to

consider acquiring the newer version of Blackboard

or another learning system
.

2.

Business Need

Wentworth should try and make it easier for students and faculty to manage work

both at and away from
said desk.


Need the ability to manage and be reminded of the due dates for
important projects and or assignments without access to a
computer.


Need the ability to submit and download important documents
from limitless locations.


Need the ability to be in c
ontact

with fellow class mates and course
instructor.

3.

Supporting Facts

If Wentworth were to upgrade to Blackboards newer version

or switch to another
learning system

it will introduce many
new
possibilities. It will address
everything stated i
n the
business need and possibly

much more.
For example if
the new version of Blackboard is implemented s
tudents will be able to do
approximately 80% of all user functions without use of a computer, they will have
access to all documents and or posts from any lo
cation, and they will have the
ability to view and communicate with all members of the course.

4.

Assumptions

Assuming that students and staff take advantage and have access to the new
technology acquisition we are expecting the level of missed assignments to

decrease thus increasing the over all grades of the student body.

5.

Approvals

In order for this to come into effect the project team will need to seek approval
from multiple departments including the Department of Technical Services
(DTS), and possibly the

president of Wentworth.


Project Charter

1.

Executive Summary


Blackboard Corporation currently hosts a website where schools can sign up and
purchase a license that will allow professors to post assignments, host discussions,
issue exams, and share vital information with their students.


2.

Business Need

Wentworth shou
ld try and make it easier for students and faculty to manage work
both at and away from said desk.



Need the ability to manage and be reminded of the due dates for
important projects and or assignments without access to a
computer.


Need the ability to subm
it and download important documents
from limitless locations.


Need the ability to be in contact with fellow class mates and coarse
instructor.

3.

Project Objectives


The project team would like to present Wentworth students and staff with the
option of
accessing their Blackboard accounts on both their mobile smart phone
as well as on their laptops.


4.

Impact Assessment



(POSITIVE) The ability to access Blackboard anywhere and at any time would be
a great option for both students and teachers. Having this o
ption would
hypothetically increase a student’s success by assuring student assignments go
unmissed and not forgotten.


(NEGATIVE) The only way in which you can use Blackboard Mobile is if you
possess either an Android device or Apple iPhone. However it is
said that nearly
80%

of college students have a smartphone.


5.

Measures of Success



As a whole if students were to show at least a 33% increase in assignments
submitted on time resulting in better grades, then we can without a doubt consider
this operation s
uccessful.


6.

Scope



This project addresses the matter of reminding students of assignments soon to be
due and or submitting in assignments promptly on the go without the use of a
computer.


7.

Risks



Students are more tempted to download and possibly share ass
ignments via
multimedia messaging on their smart phones.


Faculty doesn’t embrace the full functionality of Blackboard over the mobile
version as they are limited to what they can do.


8.

Time Constraints



This project will be completed by the end of the
current semester to ensure a
decrease in late or missed assignments, resulting in an increase of the student’s
grades in upcoming semesters.


Position Title

Person

Signature

Project Manager

Ryan McDowall


Project Sponsor

Charles Angotto






Project
Plan

1.

Project Management Plan



In order to increase the likelihood for timely success w
e plan to
use

what is known as

the
“timeline”

method for the project.
Step one

of the project would be to
construct a rough, but at the same time accurate schedule

for
the completion of various parts of
the project.
This timeline will include

all said activities and tasks the project team

plan
s

to
accomplish and when

the project team feels they should be completed
in order of priority.

2.
Risk Management Plan



The
project team currently plans to gather and evaluate all possible
risks that might be a result of the implementation of this project. The project team will also take
research from all parts of this project to help manage possible risks or negative outcomes.

Then
we shall execute and log risk responses to later review them.

3.
Issue Management Plan



Prioritization will be an integral part of the project plan and
will
be
included in our timeline in order to ensure
that
there are no iss
ues when it comes to mee
ting

deadlines. Delegation will be ta
ken care of via Outlook emails and in some instances cellular
devices. The project team reserves have the option of posting statuses

of the project
on an
assigned
Facebook page.
Lastly, the

resolution of
possible
projec
t issues will be dealt with
through in person discussions.

4.
Change Management Plan



Post discussion, a
ny changes made to the project plan
shall be
proposed to
by
both team members

to whom it concerns. Subsequently, the project team

will

then

weigh the
p
ros and cons

of potential changes.

5.
Quality Management Plan



Quality management will be
foreseen

by constant checks of the
excellence level of each
aspect of the project
. Quality will be controlled by ensuring that each
part of the project is produced t
o the utmost level

before proceeding further
.

6.
Product Management Plan



Product requirements, definitions, and design specification will
be drawn up in PowerPoint and
or

Adobe Photoshop

to then be viewed by whomever is directly
involved
.

7.
Release Management Plan


The project team will release one version of the management
plan, only if needed will

an upgraded version
will be constructed
.

Note that this could potentially
happen if major alterations are made to the overall project.

8.
Human
Resources Management Plan



Every major part of said project will be first planned
out and then equally divided
between both group members.

This includes any possible
encountered problems and or difficulties.

9.
Cost Management Plan



Overall project cost
will be kept to a minimal

by using the internet
and other relatively cheap resources as the main source of research. S
ince the product is digital,
there are not raw materials
that need to be

purchase
d
.

Only if the project proposal is put into
effect will t
here be any actual costs.

Project Schedule




Task Name

Duration

Start

Finish

Project Schedule

85
-
90 days

9/1/2011

11/23/2011

Business Need

3 days

9/1/2011

9/3/2011

Define Business Need

5 days

9/3/2011

9/8/2011

Review Business Need

1 days

9/9/2011

9/10/2011

Project
Charter

3 days

9/11/2011

9/14/2011

Develop Project Charter

4 days

9/15/2011

9/19/2011

Review Project Charter

2 days

9/20/2011

9/22/2011

Project Plan

3 days

9/23/2011

9/26/2011

Develop Project Plan

4 days

9/27/2011

10/1/2011

Define Vendor List

1 days

10/2/2011

10/3/2011

Develop RFI

3 days

10/4/2011

10/7/2011

Select Vendor List

3 days

10/8/2011

10/11/2011

Decision Scoring Matrix

3 days

10/12/2011

10/15/2011

Develop Decision Scoring Matrix

3 days

10/16/2011

10/19/2011

Reviewing Decision Scoring
Matrix

2 days

10/20/2011

10/22/2011

RFP

7 days

10/23/2011

10/30/2011

Vendor Scoring

4 days

10/31/2011

11/4/2011

Negation

3 days

11/5/2011

11/8/2011

Implementation

3 days

11/9/2011

11/12/2011

Deployment

5 days

11/13/2011

10/18/2011

Operation

4 days

11/19/2011

11/23/2011

Scoring Matrix



Category
Points

Group
Points

Vendor A

Blackboard

Vendor B

Moodle

Functionality

30




The ability to
manage and
be reminded
of due dates




10



8


8

The ability to
submit and
download
important

documents






10




9



6

The ability to
contact
involved
members





10


7


9

Technology

40




Compatible
with WIT
Network




15


15


15

Compatible
with
Windows 7
and OSX




15


15


15

Compatible
with multiple
Web
Browsers




10


10


0

Strategic
Partnership
Potential


20




Automated
Maintenance


10

9

4

Instructional
Assistance


10

7

6

Costs

10




Initial Cost


5

2

5

Ongoing
Costs


5

1

5

Totals

100

100

83

73



Project Team


Charles Angotto
-

Project Sponsor

Junior at Wentworth Institute of
Technology in Technology Management

Ryan McDowall


Project Manager

Junior at Wentworth Institute of Technology in Technology Management


Negotiation Strategy

1. Summary

The project team has selected Blackboard Inc. as the vendor of choice for
implementation
at Wentworth. One reason being the new version of said Blackboard will allow
Wentworth’s faculty and student body to take advantage of mobile access via
smartphones and other devices. On the other hand Moodle Inc. was truly a close
competito
r throughout most of the research allocation primarily due to fact it’s free. The
reason why Moodle wasn’t chosen is because it can’t operate via WEB. In order to use
Moodle software must first be installed on every computer, where Blackboard requires no
s
oftware. Thus being said the project team believes that both companies would operate
well for the needs of the project in different aspects and would like to negotiate a
functional plan for both vendors.

2. Initial Terms


Below are
rough

estimates of the c
ost for each potential vendor.


Blackboard Inc.



Moodle Inc.

Initial Cost

Software




Options Starting at 10k



0k

Hardware




0k






0k


Labor


0k


2
.5
k

Total





10k+






2
.5
k


3.
Agendas

As the project team we must spend
the necessary time to negotiate the best financial and
beneficial options. During this time pros and cons of each vendor will be taken into great
consideration by all involved parties.


Vendor Agenda


Choose the best possible learning system software for
use at Wentworth.


Choose most cost effective program to increase student’s timeliness and productivity.

4.
Leverage


Wentworth’s Leverage


Potential future sales are possible from Blackboard due to mass license quantity.


Multiple options are available for W
entworth to potentially choose from. (Bargaining
Power)


Long term future business is a strong possibility.



Vendor Leverage


Blackboard is very well known and has a highly recognizable name in the market.


Moodle is free; however it will take ample time to
be put on every computer.


Blackboard is accessible without use of software and makes it very compatible.

5.
Objectives

We plan to find the most suitable and cost effective learning system software to be used
at Wentworth in near future.

6.
Strategy

Direct
ly imply to vendors that both options are capable of meeting the majority of the
requirements. Also state that this is a budgeted project to try and negotiate a better overall
deal in the end, both long and short term.

7.
Potential Tactics

Allow each vendo
r to showcase their best features and functionalities and make a final
statement and or deal before the start of the decision making process.




8. Negotiation T
eam and
R
oles

Purchasing lead


Pursue the most aggressive deal possible

Project manager


Faci
litate constant and quality communications

Business lead


Communicate future business propositions with each said vendor

Legal


Advise negotiation team


Request for Proposal (RPF)

November 14
th
, 2011

Letter of Intent

Dear Possible Vendors

On behalf of
Wentworth Institute of Technology as the project sponsor I wish to seek out a new
piece of Learning System Software. The current one in use has served us exceptionally well for
quite some time, however we feel it is time for an update. Being a technical co
llege we are
constantly looking to stay up to date with in given reason. When problems arise at the school we
are constantly searching for answers and ways to address them accordingly.

In the average college students life it can be easily said that many di
stractions are presented
daily. This without a doubt makes it more difficult for some students to remember important
tasks and their corresponding due dates. That being said, there are several things in which we as
a school would like to include in the upd
ating of this software. We would like to make it more
convenient for students and faculty to exchange and be reminded of soon to be due work. We
hope to see at least 1/3 of our students will show a decrease in missed or late assignments, thus in
theory res
ulting in better overall grades.

Personally speaking I don’t believe that this shouldn’t be a problem to address, but that doesn’t
mean it should go overlooked. Organization is key to the success to any individual and here at
school we try to make it poss
ible for everyone to achieve success.

Thanks once again,



Charles A. Angotto IV (Project Sponsor)

Table of Contents

1

General Information

1.1

Purpose of RFP

1.2

RFP Communications

1.3

Timeline

1.4

RFP Preparation

1.5

Vendor Responses

1.6

Vendor Site Visits

1.7

Evaluation Criteria

1.8

Right to Reject

2

Vendor Guidelines

2.1

RFP Response Format

2.2

Exceptions to the RFP

2.3

Confidentiality

3

Product Information

4

Functionality Requirements

5

Technology Requirements

5.1

Client

5.2

Network Architecture, Scalability, Extensibility

5.3

Integration

6

Strategic Partnership Pot
ential

6.1

Vendor Profile

6.2

Training

6.3

Support

6.4

Implementation Plan

7

Costs

7.1

Initial Costs

7.2

Long
-
Term Costs


1.

General Information


1.1

Purpose of RFP

The purpose of the Request for Proposal (RPF) is to set forth the technical
requirements and operational aspects for the
Learning System search project that
best meets Wentworth’s needs.

1.2

RPF Communications

Please direct all aspects of communications regarding this RFP to one of the
following:

Charles Angotto



Ryan McDowall

Wentworth Institute of Technology

Wentworth Institu
te of Technology

550 Huntington Ave



550 Huntington Ave

Boston, MA 02115



Boston, MA 02115

(617) 123
-
4567



(617) 765
-
4321



1.3 Timeline






1.4

RF
P Preparation


In the possible
but unlikely event that modifications and or additions to the RFP
become necessary, both vendors will be notified accordingly and given ample
time to respond.


1.5

Vendor Responses

RFP Submission date

November

15
th

2011

Proposal Due Date

December 6
th

2011

Vendors are required to submit multiple copies of a formal written response to
either Charles Angotto or Ryan McDowall at the address provided above. This
must be submitted no later than December 6
th

2011.

1.6

Vendor Site Visits


The Wentworth project team reserves the right to visit and thoroughly view all
said vendor’s facilities at
any given time.



1.7

Evaluation Criteria

Vendors will be evaluated using the following pre
-
generated criteria:


The
ability to manage and be reminded of the due dates for
important projects and or assignments without access to a
computer.


T
he ability to submit and download important documents from
li
mitless locations.


T
he ability to be in contact with fellow class mates and coarse
instructor.

1.8

Right to Reject

Wentworth project team has every right at any given point to either accept and or
re
ject any offers or submitted proposals and it’s down discretion.

2.

Vendor Guidelines

2.1 RFP Response Format

All responses from vendors should be an attempt to describe all the positive
aspects as well as the negative aspects to the project team. We as the p
roject team
want to know as much of this useful information as possible for our selection
process.

Also vendors should provide an approximate cost of operation.



2.2 Exceptions to the RFP

Some vendors might not be affected by some parts of the RFP. For e
xample of the
cost of operation is nonexistent the project team will not require any information.

2.3 Confidentiality

All that is stated in the RFP by any given vendor is completely confidential and
will not be shared even upon request to other vendors. Th
is will ensure that
reliable responses are given.


3.

Product Information

Vendors should include a semi detailed overview of how they think Wentworth will
benefit from the use of their product. Vendors have the options of visuals and or screen
examples to
display their statements.

4.

Functionality Requirements


In this category it will be determined by the project team if each given vendor meets the
general requirements. These functionally requirements are simple, it’s whether or not
your will improve the
overall level of organization and convenience of students.





5.
Technology Requirements

In this category it will be determined by the project team if each given vendor meets the
overall technology requirements. This means that a vendor’s software

must be compatible
with all hardware that is currently in use at Wentworth by both students and faculty.



6.
Strategic Partnership Potential



6.1 Vendor Profile



Vendors must provide the project team with the following information:


Describe the ove
rall background of your company with the Learning
System marketplace and how you got to where you are today.


If possible provide reports
of past business history to show how
prestigious you are as a company.


Describe any possible problems that may occur wi
th your software and
any given time. This includes scheduled maintenance.


If not confidential please provide us with any possible software changes
and or upgrades in the near future.

6.2 Training

Vendors must provide the project team with the following inf
ormation:


Describe whether or not there will be training provided for Wentworth’s
technical department and its users.


Will there be available resources to be used for training at any time?


6.3 Support

Vendors must provide the project team with the
following information:


If any problems surface will there be representatives from your company
that will fix it?


How frequently will routine maintenance be done on your site or
program?


Describe
your company’s policy regarding system upgrades, new releases
,
and
or improvements. I
s

it

covered under your ma
intenance and support
agreement?


6.4 Implementation Plan

Vendors must provide the project team with the following information:


Describe what it is you’re going to do in order to implement your
software if
a deal is made. Do we have to do it on our own?


What is the typical time frame for the implementation process? If
possible show specific time frames.


How long before the process is 100% completed?

7.
Costs


7.1 Initial Costs

Describe to the project team cl
early as to what the initial cost will cover and how
long before another payment is required.

Software


Cost per user?


Flat fee?


Duration of license?


Number of members before excess charge is implemented?

Hardware


Do we require any hardware upgrades?


Other
Possible Expenses?



Additional Services

Vendors should include a list of other services that they have to offer that
don’t necessarily have to directly connect to the current product.






Pricing Options


Are there different pricing options that we are entitled to choose
from?


If a certain number of licenses are purchased do we receive a
discount?



7.2
Long Term Costs

Over long term periods of time and investment will any special discounts be taken
into
consideration?

Vendor Feedback


In the space provided each vendor must respond to the following statements to the best
of their
ability. The project team finds it very important to hear how you can amount to the requirements
.

Requirements

Blackboard Inc.

Moodle Inc.

The ability to manage and be
reminded of due dates.





The ability to submit and download
important documents.





The ability to contact involved
members.





Compatible with WIT

Network.





Compatible with Windows 7 and
OSX.





Compatible with multiple Web
Browsers.





Automated Maintenance





Instructional Assistance





Costs





Implementation


As for the overall implementation process of this project it can be agreed that depending on
which vendor is chosen the process may v
ary. Wentworth is willing to provide some help if
absolutely needed to meet a said deadline. That being said if on track the implementation process
should ideally be addressed by the vendor and there team. This includes the design,
development, testing, an
d deployment aspects of the project. Lastly the overall process will be
supervised by the project manager of the project team at Wentworth throu
ghout the whole period
of time.

Operations


Support

If a problem, issue, or complication arises at any given
time after the implementation
process is complete will you representing the vendor be able to provide Wentworth’s tech
staff with assistance

in resolving said issue
?

Thus being said please provide us with
support information to use if absolutely necessary.

Project

Closure

It has been previously agreed upon that once every aspect of the vendors product has
been implemented, tested, and has successfully been operating for an agreed upon period
of time is when the project is closed. This doesn’t include any
technological difficulties
further down the road.

This project will be considered successful only if students show signs of improvement as
a whole. Also students and faculty must agree that the new acquisition was beneficial and
helped make them more organ
ized.

Success will be measured by the overall average increase in student’s grades by
collecting data from teachers grade books and the end of next semester. Also the project
team will gather information on the number of assignments that were either misse
d or
forgotten and compare those numbers to previous semesters.