yari conferencing kiosk
TRANSCRIPT
-
7/29/2019 Yari Conferencing kiosk
1/1
YARI CONFERENCING KIOSK
PRODUCT FEATURES
Yari is a computer-based controller for managing a lecture and video
conferencing facility for Madeira Interactive Institute of Technology.CLIENT
Madeira Interactive Institute of Technology
role
Scrum Master| Agile UX Designer
team size
8
duration
4 months
skills
Agile UX Project Planning | Focus Setting | Activity
Modelling (Activity Map, Participation Map,
Performance Map) | Navigation Map | Heuristic
Evaluation | User Tests | Collaborative Examination |
User Centered Design
tools
Flash Builder CS5 | Illustrator CS5 | Photoshop CS5 |
Balsamiq | Visio
Remote Lecturing Made Easy
PROTOTYPE
RESEARCH
DESIGN
Research Goal
To observe and understand the process and breakdowns in managing a remotely presented lecture in order to build a workingdemonstration of interaction design for an efficient computer based controller for managing a lecture and video conferencing
facility.
RESEARCH METHODS
Affinity Diagraming was used to set focus for the
model driven inquiry process. Some of the themes
that emerged were input/output management,
presentation management, profile management,typical settings etc.
PROBLEM SOLVED
Can you see me? No Can you hear me? Not really How about now?..... Hello? Hello?
Dont let meta-communication take over your lecture time! Yari addresses this problem space through
easy, efficient and adaptive conferencing made possible by our computer-based kiosk.
Value Delivered
Managing lectures and video conferencing made easy and efficient; breaking the geographic barrier and
facilitating distant learning; improving teacher-student interaction.
The welcome screen gives the user easy access to
four possible actions. Each selection presents the
user an appropriate view and corresponding options.
The navigation bar and language selection options areavailable across all the screens.
Welcome screen
The first phase of the Model Driven Inquiry
process was Extensive observation and Interviewing
in context. As a result, lots of data was generated
that had to be analyzed and organized.
Activity Modeling was used as a formal and
systematic means of consolidating and making
sense out of data. The models we generated were
Activity Map and Participation Map.
FINDINGS and INSIGHTS
The same video conferencing equipment is used for
multiple purposes - giving local lecture, giving remotelecture, attending remote lecture and video
conferencing. The steps and procedures for each
purpose are different.
Multipurpose equipment Switching settings is Time Consuming
Different professors need different arrangements
depending on the purpose but they have little time atthe beginning of a lecture to switch settings.Althoughthis is a commonly faced challenge,settings processes
are still time consuming in available products.
The Lecture & Video conference tab allows the user to
select sources and adjust sound. The user can
change the currently selected mode to any of the
other three modes available and the options are
updated automatically. The scroll list is ordered from
the most to the least likely source for the modeselected. The user can also record any or all the
screens and sound for future playback.
Lecture & Video
conference
The Make a Call tab allows the user to make a call to
a member on the contact list or either by dialing the IPaddress. Feedback messages appear within context
indicating the system state, like indicating when the IP
address is valid, when the call is being made and
when a connection has been established. The contact
list allows contacts to be added, edited or deleted.
Make a Call
DESIGN METHODS
We created a Content Inventory and
Navigation Map to understand what the
interaction spaces are and how these are
interconnected. For this we reviewed semantic andprocedural relationships among activities, roles, and
tasks.
The User Tests, Interviews and
Inspections served as a reality check at each
major turning point in the user centered design
iterations.
We realized that we cannot always rely on users to
formulate each and every requirement.
Collaborative Examination, Heuristic
Evaluations and Critics played a major role indelivering a successful product.
User Centered Design Iterations
MORE
online content download
http://bit. ly/M8Np7L https://dl.dropbox.com/u/14689889/yari_prototype.swf
The Incoming Call tab informs if there is any incomingcall. User may answer or reject the call. The tab
flashes to indicate an incoming call.
Incoming Call
Plenty of ideas were in the making for a truly efficient
help system. This screen shows the team and product
logo. Our team name is Yari. Yari is a Japanese name
for antique swords. These swords were big and heavy,
but Yari warriors used them with strength and
courage. We selected this concept to represent our
team values: courage and fellowship.
HELP & ABOUT
The paper prototype was the first abstraction attempt
of the design created using the content inventory
and navigation map as guidelines.
After critiquing and evaluating the paper prototype,
we created low fidelity mock-ups. During this processwe had to reconsider the design due to change in
screen dimension requirements.
Thereafter we moved to more graphical versions of
our design. These were provided to the development
team as an initial guide to prototyping.
The final design was a result of intensive user testing
and collaborative examinations. This thentransitioned into a working prototype.
IMPLEMENTATION
HUMAN CENTERED SOFTWARE ENGINEERING
Transferring Requirements from design team
and making sure the prototype accurately reflected the
original design was a challenge resolved through
detailed annotated wireframes. This also served as a
basis forFunctional Requirements.
Development team used Pair Programming -
programming as a collaborative conversation. This
led to continuous code reviews, cross-training and
mentoring, motivation as well as sanity checks, and
building teamwork.
Each development team member had to make a
backup of the working version before integrating
changes and also update the sprint backlog and
change log thus establishing Version Control.
The testers and designers were responsible forevaluating the working module forQuality
Assurance.
MANAGEMENT
PROJECT MANAGEMENT TOOLS
All individuals involved in the project came from
different backgrounds. As a part ofTeam Buildingactivity, the team met up to understand each others
individual values, come to consensus on a team name
and lay some ground rules on communication and
commitment.
As a part of my role as the scrum master, I laid out a
comprehensive Project Plan for each sprint.There were five two week sprints and each had a
defined start and end deliverable.
Throughout the project, I actively tracked progress
and resolved challenges and impediments throughdaily Stand Up Meetings and Burndown
Charts and managing Sprint Backlog.
Bilingual support
Some professors are comfortable with Portuguese
as their primary language while some others use
English. Just like switching settings, professors needto reset language between two lectures as well as
during lectures.
https://dl.dropbox.com/u/14689889/yari_prototype.swf
TECHNOLOGY
Flash | Flex | CSS