Differences

This shows you the differences between two versions of the page.

--- webteam.visitor_analysis [2011/01/11 23:50] – jimcraner
+++ webteam.visitor_analysis [2011/03/18 15:24] (current) – Deleted - Page moved aatre
@@ Line 1: / Line 1: @@
-====== This page has been replaced - please don't edit ======
-Further refinement of the user stories is taking place on the [[webteam.user_stories_2011|User Stories 2011]] page.
-====== Visitor Analysis: Users, Personas, and User Stories ======
-User stories are a method of creating software requirements for software applications and in our case, online communities. First, we define our website visitors by grouping them into personas based on shared objectives and characteristics.  For instance, the first visitor group we've defined below, given the name "Patty Potential," represents the Potentials user group - non-Evergreen users considering a move to EG adoption.
-There are various things to consider when grouping users into personas, including:
-  * stage in OSLS/EG adoption process
-  * role of user within own organization
-  * geographic locations of users (languages)
-  * web site/community/tool savvy
-  * referral source of inbound visit
-  * user goals -- "why is this visitor here?"
-  * site owner goals -- "what constitutes success from site owner/admin perspective?"
-Once we've identified a user persona, we can develop "user stories" for the persona.  These are sample activities representing every task that a user from that role may wish to perform - everything from finding certain info to participating in online discussions.  Some user stories may overlap; that is, some stories will be common to multiple personas, such as the ability to search for specific resources using a search engine.
-When developing our user personas and user stories, we want to make sure that we are satisfying all of the requirements that we defined on our [[webteam.strategic_goals_requirements|strategic requirements page]].
-After a comprehensive list of user stories has been developed, we'll work as a community to refine and prioritize that list as the next stage in our planning process.
-=== EG Community Members: ===
-**Please review the list of existing personas and the stories for each role.  The Web Team is eagerly seeking additions and suggestions from as many people in the EG community as possible; please submit your suggestions to the general mailing list.**
-----
-**A) Patty Potential is a Circulation Manager at a regional public library system. Patty's libraries are currently running a proprietary ILS and she is interested in learning more about Open Source Library Systems (OSLS) and Evergreen in particular.**
-  - Patty can easily find a centralized and authoritative EG site with a minimum of searching.
-  - Patty can view a "one-pager" offering a high-level overview of both EG software and the EG community
-  - Patty can view contextual background information on Open Source Software
-  - Patty is directed to visit a "Considering Evergreen?" web page which offers a curated introduction to EG resources, created by EG community experts. This page presents links to decision-making information in a logical order, aimed at the potential implementer. The functionality of this page is currently served by the E-ILS.org's "About Evergreen" page.
-  - Patty can browse through a hierarchical list of resources aimed at potential implementers
-  - Patty can use keywords and filtering to search for a specific resource aimed at potential implementers
-  - Patty can pose questions a community of existing users, using the existing IRC channels, existing mailing lists, and/or a web-based forum
-  - Patty can easily find a demo "sandbox" implementation of Evergreen to examine
-  - Patty can search for an EG Service Provider based on certain criteria
-  - Patty can search for existing EG libraries based on certain criteria
-  - Patty can search for individuals in the EG Community based on certain criteria
-**B) Max Migration is a System Administrator at a regional public library system. Max's library is in the process of planning and performing a migration to Evergreen from their proprietary ILS.**
-  - Max can easily find a centralized and authoritative EG site with a minimum of searching.
-  - Max can easily find a collection of resources targeted at libraries performing a migration
-  - Max can search for specific resources (by keyword) concerning a specific aspect of the migration
-  - Max can pose support questions if he encounters a problem during his migration planning or implementation
-  - ...
-**C) Addie Admin is a System Administrator at a regional public library system that uses Evergreen ILS. Addie is tasked with ongoing maintenance, administration, and user training for her library's ILS.**
-  - Addie can easily find a centralized and authoritative EG site with a minimum of searching
-  - Addie can learn about news and developments in the EG community
-  - Addie can choose to be notified about news and developments in the EG community
-  - Addie can search for specific EG-related resources by keyword or other criteria
-  - Addie can browse a categorized collection of EG resources
-  - Addie can participate in a user forum of other administrators to ask questions and exchange best practices
-  - Addie can easily request a new feature that she feels would be beneficial for the larger EG community
-  - Addie can review and comment upon new feature requests suggested by other users in the EG community
-  - Addie can easily access the EG Bug Tracker and submit a bug report
-  - ...
-**D) Dave Developer is a developer on the Evergreen project, employed by a consortium of EG libraries.**
-  - Dave can keep official project documentation maintained in a doc repository separate from the overall EG resource library/collections.
-  - Dave can see a summary of Feature Requests submitted by members of the community
-  - Dave can see a detailed history of each Feature Request including commentary from members of the community
-  - Dave can see documentation for procedures on submitting code to the the community.
-  - Dave can see documentation and tutorials on Evergreen system architecture.
-  - Dave can see a list of other developers he can contact for advice.
-  - ...
-**E) Gertie Governance is a volunteer on the Evergreen Foundation management board's Communications Committee. Gertie is tasked with utilizing the website and user community systems to enhance growth and development of the greater EG community.**
-  - Gertie can easily generate (and export) a list of website users that have registered, filtered and sorted by role, location, and any other info useful to the CommsCommittee.
-  - Gertie can easily add content to the website as requested by other members of the management team
-  - ...
-**F) Wally Webmaster is the webmaster of the newly-overhauled Evergreen web portal.**
-  - Wally can easily manage and maintain the website and associated properties, including the ability to securely delegate authority for administration to other users
-  - Wally can easily identify and purge outdated content.
-  - ...
-**G) Carla Consultant is a representative of an organization that is considering offering Evergreen related services.**
-  - Carla can view view a “one-pager” offering a high-level overview of both EG software and the EG community
-  - Carla can view a list of Evergreen implementations by certain criteria such as geographical area or specialty.
-  - Carla can view a list of potential Evergreen related service providers and request that her organization be added to the list
-  - Carla can view a list of Evergreen feature requests.
-  - Carla can view a list of Evergreen related services, RFIs, and RFPs from members of the community.
-  - ...
-**H) Sally Skeptic isn't sure what the big fuss is about open source but she's been asked to look at Evergreen by her boss, either for informational purposes or because her library is seriously considering migrating to it.**
-  - Sally can find out why open source is a good idea.
-  - Sally can learn about the differences between Evergreen and Koha.
-  - Sally can see clearly that people using Evergreen are happy with their choice.
-  - Sally can learn about the pros and cons of open source on a "Why Open Source?" page.
-**I) Sarah Stand-alone is looking at an open source system for her library. Sarah likes the idea of open source, but thinks that Evergreen might be for networks.**
-  - Sarah can find a page of resources for stand alone Evergreen libraries.
-  - Sarah can get in touch with other stand alone libraries that have moved to Evergreen.
-  - Sarah can do everything Patty can do, without feeling like an afterthought.
-**J) Vanessa Vendor - may be a print management company who needs to know how to set up a SIP for use with Evergreen. Or a vendor who may want to develop an OPAC skin to be used with Evergreen.**
-  - Add stories!
-**K) Dora Documentor works in a regional public library system that uses Evergreen ILS. She is a potential volunteer for reviewing and updating Evergreen documents.**
-  - Dora is knowledgeable about Evergreen and is familiar with the available documentation.
-  - Dora has a sharp eye: she has issues with the existing documentation, has noticed various errors, and even made notes about needed corrections.
-  - Dora would like to help but doesn't know how to get her updates into Evergreen.
-  - Dora has access to the usual set of Microsoft Office tools.
-**L) Tara Translator works in a regional public library system that uses Evergreen ILS. She is a potential volunteer for translating Evergreen documents. **
-  - Tara is proud to be multilingual and is fluent in English, and Elbonian, and even a little Slobbovian.
-  - Tara is knowledgeable about Evergreen and is familiar with the available documentation.
-  - Tara believes she could translate parts of the documentation into Elbonian, and could even help with Slobbovian.
-  - Tara has never written technical documentation before, though she is familiar with the process of translating written documents.
-  - Tara would like to help but doesn't know how to get her updates into Evergreen.
-  - Tara has access to the usual set of Microsoft Office tools.
-**M)  Peter Power Patron **
-Peter is an avid library user, and codes as a hobby.  He has written browser "gadgets."  He is currently interested in mobile apps and would like create some for the OPAC and release them into the wild.  His latest app was single use mobile app that allowed him to type in an ISBN into his smart phone while in a bookstore. (He's working on taking a picture of the barcode on the cover instead of typing in the ISBN)
-His app would query the Worldcat xISBN service (http://www.worldcat.org/affiliate/webservices/xisbn/app.jsp) for a  list of "related" ISBN's and then query his local library to see if it had any of the books.  He is curious about how easy apps such as this would be to write for EG.  And where the documentation needed can be found.  His impression, knowing that EG is Open Source, is that this should be easier than with other ILS's.
-**N) Edna Extender**
-  * Edna’s library has been using Evergreen as it comes "out of the box."  Edna's library colleagues, who work mostly in large academic libraries, have all been talking about "discovery layers" such as Blacklight and VuFind.  [[http://groups.google.com/group/ils-di/web/ils-interop-discussion-home?pli=1|Link]]
-  * She lurks on the code4lib web site and email list. [[http://www.mail-archive.com/code4lib@listserv.nd.edu/msg02954.html|see this]]
-  * She has recently read the following article: [[http://journal.code4lib.org/articles/4165|“The Integrated Library System’s APIs, an Open-source Web 2.0 Catalog, and University Computing Live Happily Ever After” by Birong Ho.]]  Edna is curious about EG's capabilities in this area.
-**O) Irene Install**
-Irene is a system administrator currently using a proprietary ILS. Irene's consortium will be migrating to Evergreen and Irene wants to install a test system so she and her colleagues can learn more about Evergreen.  Irene has tried to keep up with the technologies relevant in the proprietary vendor environment.  She knows some perl, SQL, and unix administration.  Irene can likely install the latest Evergreen tarball but may have some installation and configuration questions.  Irene is new to the developer environment and is mystified by things like software repositories, subversion, git, patches, trunk, and branches. Irene would like to find resources that would help her get up to speed so she and her colleagues can test the latest development.
-  - Irene can find information on Evergreen software repositories and how to use them.
-  - Irene can download test marc, copy, and user data.
-  - Irene can find discussion, specs, or documentation describing features.
-  - Irene can find information on how to build, rebuild, and update Evergreen.
-  - Irene can find information, discussion, and examples of ways to configure Evergreen.
-**P) Ari Accessibility works in a regional public library system that uses Evergreen ILS. She is a potential volunteer for testing and reviewing accessibility issues in
-Evergreen documents and in the Staff Client. **
-  - Ari is visually impaired.
-  - Ari is competent with commercial screen readers and audio web browsers, and is knowledgeable about assistive technologies.
-  - Ari is aware of accessibility issues related to documentation and web design, but is not a software or web developer.
-  - Ari has issues with existing Evergreen documentation and with the Staff Client, has noticed various accessibility problems, and has made notes about needed corrections.
-  - Ari would like to help but doesn't know how to get her updates into Evergreen.
-=== Grouping / Sorting Considerations ===
-  * stage in OSLS/EG adoption process
-  * role of user within own organization
-  * geographic locations of users (languages)
-  * web site/community/tool savvy
-  * referral source of inbound visit
-  * user goals -- "why are they here?"
-  * site owner goals -- "what constitutes success from site owner/admin perspective?"