Statement of Work Usability Testing Lupine Project

desertdysfunctionalInternet and Web Development

Dec 4, 2013 (3 years and 6 months ago)

103 views


Statement of Work

Usability Testing

Lupine Project



(
For
Website
Professionalization
)



Document Number

RFP
-
Usability
-
iPlant.doc

Date Published

/ Version

December 4, 2013

/ 1.1

Document Location

Alfresco Share »

iPlant All

»

Documents
»

Website_Professionalization_Project






© 2009 iPlant Collaborative. All rights reserved.

P

2


www.iplantcollaborative.org


Table of Contents

Table of Contents

2

Introduction

3

About iPlant

3

Usability Objectives

3

Summary

3

Web Site Program (Lupine) Overview

4

Challenges With Site

4

Goals For Site

4

Overall goals

4

Usability Goals

5

High
-
Level Site "Professionalization" Process

6

Phase 1


Discover

6

Phase 2


Design

6

Pha
se 3


Refine

6

Phase 4


Deliver

6

Usability Program

7

Usability Process Details

7

Suggested Methodology

7

Possible testing locations

8

Lupine Project Timeline
-
Milestones / Vendor Deliverables

8

Resources

9

Provided by Vendor

9

Provided by i
Plant

9

Payment

9

Proposal Submission

9

Deadline and questions

9

Other Considerations

9

Criteria for Award

9








© 2009 iPlant Collaborative. All rights reserved.

P

3


www.iplantcollaborative.org

Introduction

About iPlant

The iPlant Collaborative's mission is to create a cyber
-
infrastructure to support a
community of plant and computing researchers in addressing the biggest issues in plant
sciences. The project
’s web site (
www.iplantcollaborative.org
) is the public’s gateway to
our informational site and public portal to our organization.

iPlant's core staff are located at the University of Arizona, Cold Sprin
gs Harbor Lab,
University of North Carolina at Wilmington, Arizona State University, and Purdue
University.

Usability Objectives

We are in the process of redesigning our public web site. Internally this is referred to as
"web site professionalization" with

a code name of "Lupine".

When the new site is launched at the end of September 2009, usability testing should
help ensure the site is:



Engaging, interesting, and aesthetically pleasing



Easy
-
to
-
use and easy
-
to
-
navigate



Consistent and logical



Provides usefu
l content to the identified audience



Encourages community and collaboration



Accessible to those with disabilities, meets section 508


Summary


IPlant is requesting bids from vendors to use usability testing methods to independently
evaluate and validate th
e design of our public web site. The vendor to provide services
including:



Usability study preparation



Assistance with participant screening



Setup and two rounds of usability testing



Conduct two rounds of usability testing



Analyze and report the data



Crea
te a high
-
level summary that can be presented to the iPlant management

Proposals are due on August 3, 2009, by 5:00 pm MST.








© 2009 iPlant Collaborative. All rights reserved.

P

4


www.iplantcollaborative.org

Web Site Program (Lupine) Overview


Challenges With Site

Community usage of the existing web site has revealed
challenges, prob
lems, and
weaknesses
. In order to fulfill our mission, we need to update our web site so it reflects a
professional appearance and provides meaningful opportunities for our community to
connect and collaborate.

The following types of existing problems hav
e been reported:



Weak visual design and appearance.



Broken site structure and navigation.

o

Inconsistent navigation

o

The “Search” function doesn’t work correctly.

o

Pull
-
down menus don’t work correctly.



Inconsistent terminology and acronyms.



Lack of collabora
tion and communication tools.



It is difficult for even authorized administrators to add and edit content. Content is
not presented well.



Doesn’t meet WAI (Web Accessibility Initiative) standards.



Lack of Search Engine Optimization.



Improve performance metr
ics.



Low community satisfaction.

o

50% of user survey respondents
disagree

that our site is "easy
-
to
-
use"

o

Only 18.2% agree our "
site is useful
"

o

Only 31.8% would
"recommend
" our site.

Our existing site is in Joomla and we are migrating to Drupal with the red
esign.


Goals For Site


Overall goals

The intended and desired
purpose
of the website redesign and professionalization is:



A gateway for the iPlant Collaborative.

o

A gateway or portal for tools and information sharing.

o

Educate people about the organization
al mission, activities, and the
ways the public can become involved.

o

A central source for news, updates, and resources.



A tool for the community to meet, connect, and collaborate.






© 2009 iPlant Collaborative. All rights reserved.

P

5


www.iplantcollaborative.org

o

Increase the community members (expand user base).

o

Provide means to contact
project personnel to become involved.

o

Assist in social
-
professional networking.

o

Links to computation, research and other online services.



Strengthen the iPlant brand.

o

Demonstrate the potential of the collaborative.

o

Present a professional and well
-
designed
brand, image, and reputation.

o

Publicly triumph successes and wins.



Get people excited about plant science.



A tool to measure and report community engagement.

o

Measure community engagement using standard web analytics.

o

Generate data to report to NSF.

Usabili
ty Goals

Specific usability goals fall into two categories, usability performance measurements and
subjective measurements. For usability performance measurements, we anticipate
testing standards to include:


Subjective measurements include better responses on user survey questions and
possibly Likert scale measurements. Specific usability goals related to user satisfaction
from the user survey are:

Metric

Baseline Response

Goal Response

Site is
easy
-
to
-
use

50% disagree

(Strongly disagree + Disagree)

25 % disagree [2x]

(Strongly disagree + Disagree)

Site is useful

18.2% agree

(Agree + Strongly agree)

54.6 % agree [3x]

(Agree + Strongly agree)

User would recommend

31.8% agree (yes, no one)

(Agree

+ Strongly agree)

63.6% agree [2x]

(Agree + Strongly agree)

Metric

Example

Goal Measure

Time on Task

Time to perform a key task, find things quickly

TBD

Task success rate

Success rate for information retrieval

TBD

Low error rates

Few user errors

TBD

Etc...








© 2009 iPlant Collaborative. All rights reserved.

P

6


www.iplantcollaborative.org

High
-
Level Site "Professionalization" Process

The
UX process we implemented follows a four
-
phased, user
-
centered design approach.
Each step is collaborative with stakeholders and the development team. This RFP is to
solicit an independent usability evaluation of our site, and make recommendations to help
us meet our success metrics. Specifically this RFP is for phase 3 of our process:

Phase 1


Discover



Create a UX program plan to guide the web site professionalization. Ensure the
redesign meets the needs for our complex and diverse audiences.



Gather user

needs and collect data from the field from our scientists, educators,
students, and staff.



Identify internal stakeholders, organizational goals, and strategy including
success metrics.

Phase 2


Design



Define the scope and content requirements; determine
what must be in this
release called “release 2.0”.



Create a conceptual model and information architecture.

Phase 3


Refine



Moia Group will deliver templates for the team to evaluate.



UX will conduct usability testing for design refinement with an independ
ent
usability vendor, and provide recommendations.

Phase 4


Deliver



Implementation of the design into a dynamically displayed site.



Add content to the site.



Final definition of success metrics, including SEO and reporting.







© 2009 iPlant Collaborative. All rights reserved.

P

7


www.iplantcollaborative.org

Usability Program

Usability P
rocess Details

Suggested Methodology

IPlant is requesting bids from vendors to independently evaluate and validate the design
and reveal what needs to be fixed prior to public release. iPlant and vendor to finalize the
methodology collaboratively.

The ven
dor to provide services including:



Usability study preparation, work with the iPlant team to:

o

Create a user screener

o

Write study plan

o

Finalize metrics and evaluation measures

o

Finalize a pre
-
study questionnaire

o

Finalize study protocol

o

Define test personnel

roles

o

Define number of participants, probably about 12 subjects / usability test
round. Other influences include:



Number of usability tasks



Types of subjects



Number of internal staff and external participants



Experienced members, non
-
experienced members



iPlant and vendor to work collaboratively to create participant screener. Vendor
to

o

Screen participants

o

Coordinate times and locations

o

Create solution for gratuity (being in the university, we can offer goods
but not cash). Potential solutions are a gift c
ard to the bookstore or
amazon.com



Setup two rounds of usability testing

o

Provide equipment to capture data

o

Computer for study could be provided by iPlant or vendor

o

Pick best testing location (UA office or vendor lab)

o

Note: video highlight and summary is no
t required, but session videos
would be a nice to have for sharing with remote teams



Conduct two rounds of usability testing

o

Welcome and instruct participants

o

Run participants through study and tasks

o

Administer questionnaires as appropriate






© 2009 iPlant Collaborative. All rights reserved.

P

8


www.iplantcollaborative.org



Analyze and rep
ort the data

o

Document with issues, observations, and recommendations

o

Working directly with the team to implement changes and
recommendations (hands on process)

o

Be available for questions and feedback



Create a high
-
level executive summary that can be presen
ted to the iPlant
management team, with talking points (probably 6
-
8 .ppt slides)

The vendor will work closely with multiple teams including:



Internal iPlant representatives including: User Experience, marketing,
development, and content creators / manager
s



External design and development vendor, Moia Group who is building our site in
the CMS, along with style sheets and templates

Possible testing locations

Testing may be conducted at vendor lab or iPlant offices.

The perceived advantage of a vendor lab is

usability testing measurement equipment,
one
-
way mirrors, and other equipment is setup and optimized for such studies. The
disadvantage is the team may need to drive to the vendor lab, thus lowering engagement
rate.

The perceived advantage of testing at i
Plant offices is higher team engagement rate, but
the lab setup would be "on
-
the
-
fly" and less formal. We expect the vendor to make
recommendations, based on experience.

Lupine Project Timeline
-
Milestones / Vendor Deliverables

Approximate timeline, to be
firmed up after vendor discussions.

Task

Details

Date

RFP Due


08/03/09

Vendor Selected


08/06/09

SOW signed


TBD

Study Plan/Protocols
Approved


08/19/09

Usability Test
-

Round 1


08/25/09
-

08/26/09

Usability Analysis and Results
Report
-

R1


08/31
/09

Usability Recommendations
Implemented
-

R1


08/31/09
-

09/04/09

Executive Summary
-

R1


09/02/09

Usability Test
-

Round 2


09/15/09
-

09/16/09

Usability Analysis and Results
Report
-

R2


09/21/09

Usability Recommendations
Implemented
-

R2


09/21/
09
-

09/25/09

Executive Summary
-

R2


09/23/09






© 2009 iPlant Collaborative. All rights reserved.

P

9


www.iplantcollaborative.org


Resources

Provided by Vendor



Usability lab equipment (permanent or portable)



Personnel: TBD


Provided by iPlant




User Experience Research Document including:

o

User Profiles

o

User Survey

o

Success Metrics

o

etc.

Payment

An initial payment shall be made to the vendor equal to half the total amount of the
award. After receiving and certifying all deliverables as complete, the remainder of the
award balance will be paid
. Vendor shall submit an invoice to iPlant before any payment.

Proposal Submission

Deadline and questions

iPlant team to meet with vendors and for any RFP before July 24 (Team is on vaction for
a week). Additional questions shall be directed to Brenton El
more at 520
-
907
-
5100, or via
email: brenton@iplantcollaborative.org.

Proposals are due by 5:00 pm MST, on August 3 by email to
brenton@iplantcollaborative.org. Please break down the pricing, work items, and
deliverables as appropriate.

Other Consideration
s

Vendors will be required to supply a complete description of the key activities. Wherever
possible, iPlant ask that you submit copies, outlines, or examples of your previous work
to assist in the evaluation. This includes a portfolio, list of previous cl
ients, and
information about your company and experience.

Criteria for Award

The selection of vendor will be based on a combination of factors including interviews,
organizational compatibility, technical expertise demonstrated by portfolio, examples,
pric
e, and other factors.

Please note that the acceptance of a proposal does not obligate iPlant to purchase any
service. iPlant reserves the right to reject all proposals and not to make a decision. All
costs for the proposal preparation are the responsibilit
y of the bidder.
Site Launch


Exact date TBD
-

by
end of Sept.






© 2009 iPlant Collaborative. All rights reserved.

P

10


www.iplantc
ollaborative.org

Please ignore this page.