Evergreen DokuWiki

User Tools

Site Tools

You are here: start » webteam » user_stories » 2011
webteam:user_stories:2011

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
webteam:user_stories:2011 [2011/02/02 21:58] – jimcranerwebteam:user_stories:2011 [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Visitor Analysis: Users, Personas, and User Stories ======+====== Criteria for New Website: Content and Functionality User Stories ======
  
-This page is for final refinement of the User Stories created by the EG community (and originally documented [[webteam.visitor_analysis|here]].)+This page is for final refinement of the User Stories created by the EG community.
  
-Evergreen Website User Stories (1/25/2011 draft)+When planning a new website, it's important to make sure that we consider 1) all of the various groups of users that will be using the new website, as well as 2) all of the various tasks that each group of users will need to perform upon the site.  We develop the website's requirements by exhaustively collecting and cataloging these various tasks.  The process we use for doing so is called "User Stories."  User stories are simple descriptions of features, written in plain English, that help us effectively plan a new website.
  
-User stories are simple descriptions of features, written in plain English, that help us effectively plan a new website.  Since different groups of website users have different requirements, some user stories may only apply to certain user groups, e.g., "Evergreen Developer" or "Potential Evergreen Implementers."+This document contains user stories collected from the Evergreen community and refined through collaborative discussion.  As described below, there are two main kinds of requirements: functionality-related requirements and content-related requirements.  Since different groups of website users have different requirements, some user stories may only apply to certain user groups, e.g., "Evergreen Developer" or "Potential Evergreen Implementers."  In addition, some groups may have certain content requirements but no separate functionality requirements, and vice versa.
  
-This document contains user stories collected from the Evergreen community and refined through collaborative discussion.+====== Defining our User Groups =======
  
-===== Functionality-related Requirements =====+"Potential" users are those considering an implementation of Evergreen for their organization. 
 + 
 +"Administrator" users administer or maintain an existing Evergreen implementation. 
 + 
 +"Consultant" users provide services to one or more Evergreen-using organizations. 
 + 
 +"Skeptic" users are potential users that are explicitly unsure of open source development methodology, support models, open source ILS in general, or Evergreen specifically. 
 + 
 +"Migration" users are planning or in the middle of a migration to Evergreen. 
 + 
 +"Standalone" users are existing or potential Evergreen users of a single-library implementation of Evergreen. 
 + 
 +"Developer" users are developers of Evergreen software. 
 + 
 +"Extenders" include third-party developers, integrators, and other "unofficial" developers with an interest in Evergreen development and source code. 
 + 
 +"Install" users are seeking information about Evergreen software repositories and related downloads. 
 + 
 +"Documentors" help create and maintain the official Evergreen project documentation. 
 + 
 +"Translators" participate in translating the Evergreen software and/or documentation. 
 + 
 +"Accessibility" users participate in ensuring Evergreen software, documentation, and website are as accessible to as many users as possible. 
 + 
 +"Governance" users are members of the Evergreen Governance Committee 
 + 
 +"Webmasters" maintain the existing website and underlying infrastructure 
 + 
 +"LIS" users are professors, teachers, or students interested in studying Evergreen and other ILS software in a LIS or other academic context. 
 + 
 +====== Functionality-related Requirements ======
  
 User stories can be related to website functionality, such as activities, applications, and tasks that users perform.  For instance, an online event calendar that allows committees to schedule recurring monthly meetings is an example of a  functionality-related user story. User stories can be related to website functionality, such as activities, applications, and tasks that users perform.  For instance, an online event calendar that allows committees to schedule recurring monthly meetings is an example of a  functionality-related user story.
Line 27: Line 57:
 5. Website users can add resources, including file attachments and/or third-party URLs, to an online resource directory available to other users. 5. Website users can add resources, including file attachments and/or third-party URLs, to an online resource directory available to other users.
  
-==== B. Evergreen Administrators administer one or more Evergreen systems for their organization. ====+==== B. Evergreen Administrators ====
  
 1. Administrators can participate in an online forum to ask questions and share best practices with other Administrators. 1. Administrators can participate in an online forum to ask questions and share best practices with other Administrators.
Line 35: Line 65:
 3. Administrators on the website can easily reach the Bug Reporting feature on Launchpad. 3. Administrators on the website can easily reach the Bug Reporting feature on Launchpad.
  
-==== C. Evergreen Developers work on the actual Evergreen software.  Evergreen Documentors are members of the DIG and other participants in the documentation process.  Evergreen Consultants are consultants that work with Evergreen implementations in some capacity. ==== +==== C. Evergreen Developers, Documentors, and Consultants ====
  
 1. Documentors and Developers can maintain the official project documentation in a repository apart from the community EG resource/contribution library.   1. Documentors and Developers can maintain the official project documentation in a repository apart from the community EG resource/contribution library.  
Line 42: Line 71:
 2. Developers and Consultants can participate in the Administrator "feature percolator" discussion forum mentioned above as well as view the forums in detail. 2. Developers and Consultants can participate in the Administrator "feature percolator" discussion forum mentioned above as well as view the forums in detail.
  
-==== D. Governance users are members of the Evergreen Governance Committee. ====+==== D. Governance users ====
  
 1. Governance users can easily add content to the website as needed. 1. Governance users can easily add content to the website as needed.
Line 48: Line 77:
 2. Governance users can easily generate a report of website users that have completed the user or organizational profiles mentioned above. 2. Governance users can easily generate a report of website users that have completed the user or organizational profiles mentioned above.
  
-==== E. Webmasters represent the group of users that maintain the website. ====+==== E. Webmasters ====
  
 1. Webmasters can easily manage and update the website, including the ability to delegate permissions to other users. 1. Webmasters can easily manage and update the website, including the ability to delegate permissions to other users.
Line 54: Line 83:
 2. Webmasters can easily identify and purge outdated content. 2. Webmasters can easily identify and purge outdated content.
  
-=== Content-related Requirements ===+====== Content-related Requirements ======
  
 User stories can also be related to content on the website, such as specific documents, materials, multimedia, or pages.  For instance, having a special page on the website explaining the benefits of Evergreen to people who don't currently use it is an example of a content-related user story. User stories can also be related to content on the website, such as specific documents, materials, multimedia, or pages.  For instance, having a special page on the website explaining the benefits of Evergreen to people who don't currently use it is an example of a content-related user story.
  
-==== A. User groups for the purpose of creating specific website content ==== +==== A. Content requirements applicable to all users. ====
- +
-"Potential" users are those considering an implementation of Evergreen for their organization. +
- +
-"Consultant" users provide services to one or more Evergreen-using organizations. +
- +
-"Skeptic" users are potential users that are explicitly unsure of open source development methodology, support models, open source ILS in general, or Evergreen specifically. +
- +
-"Migration" users are planning or in the middle of a migration to Evergreen. +
- +
-"Standalone" users are existing or potential Evergreen users of a single-library implementation of Evergreen. +
- +
-"Developer" users are developers of Evergreen software. +
- +
-"Extenders" include third-party developers, integrators, and other "unofficial" developers with an interest in Evergreen development and source code. +
- +
-"Install" users are seeking information about Evergreen software repositories and related downloads. +
- +
-"Documentors" help create and maintain the official Evergreen project documentation. +
- +
-"Translators" participate in translating the Evergreen software and/or documentation. +
- +
-"Accessibility" users participate in ensuring Evergreen software, documentation, and website are as accessible to as many users as possible. +
- +
-==== B. Content requirements applicable to all users. ====+
  
 1. Users can find updated information on connecting with EG community via IRC, mailing lists, and other formats. 1. Users can find updated information on connecting with EG community via IRC, mailing lists, and other formats.
Line 90: Line 95:
 3. Users can browse or search a categorized collection of Evergreen-related resources. 3. Users can browse or search a categorized collection of Evergreen-related resources.
  
-==== C. Content requirements applicable to Potential users. ====+==== B. Content requirements applicable to Potential users. ====
  
 1. Users can view a “one-pager” offering a high-level overview of both EG software and the EG community. 1. Users can view a “one-pager” offering a high-level overview of both EG software and the EG community.
Line 110: Line 115:
 9. Users can search for individuals in the EG Community based on certain criteria. 9. Users can search for individuals in the EG Community based on certain criteria.
  
-==== D. Content requirements applicable to Migration users. ====+==== C. Content requirements applicable to Migration users. ====
  
 1. User can access (browse/search) a hierarchically-categorized collection of resources aimed at libraries performing a migration. 1. User can access (browse/search) a hierarchically-categorized collection of resources aimed at libraries performing a migration.
Line 116: Line 121:
 2. Users encountering problems during migration are encouraged to join and participate in the general mailing list for assistance. 2. Users encountering problems during migration are encouraged to join and participate in the general mailing list for assistance.
  
-==== E. Content requirements applicable to Consultant users. ====+==== D. Content requirements applicable to Consultant users. ====
  
 1. Users can view a list of potential Evergreen related service providers and request that her organization be added to the list. 1. Users can view a list of potential Evergreen related service providers and request that her organization be added to the list.
Line 122: Line 127:
 2. Users can view a “one-pager” offering a high-level overview of both EG software and the EG community. 2. Users can view a “one-pager” offering a high-level overview of both EG software and the EG community.
  
-==== F. Content requirements applicable to Extender and Install users. ====+==== E. Content requirements applicable to Extender and Install users. ====
  
 1. Users can find information on Evergreen software repositories and how to use them. 1. Users can find information on Evergreen software repositories and how to use them.
Line 134: Line 139:
 5. Users are easily directed to on-site and off-site information, discussion, and examples of ways to configure Evergreen. 5. Users are easily directed to on-site and off-site information, discussion, and examples of ways to configure Evergreen.
  
-==== G. Content requirements applicable to Skeptic users. ====+==== F. Content requirements applicable to Skeptic users. ====
  
 1. Users can find out why open source is a good idea. 1. Users can find out why open source is a good idea.
Line 144: Line 149:
 4. Users can view curated case studies of successful Evergreen migration and implementation projects. 4. Users can view curated case studies of successful Evergreen migration and implementation projects.
  
-==== H. Content requirements applicable to Standalone users. ====+==== G. Content requirements applicable to Standalone users. ====
  
 1. Users can find a page of resources for stand alone Evergreen libraries. 1. Users can find a page of resources for stand alone Evergreen libraries.
Line 150: Line 155:
 2. Users can find and contact other stand alone libraries that have moved to Evergreen. 2. Users can find and contact other stand alone libraries that have moved to Evergreen.
  
-==== I. Miscellaneous content requirements ====+==== H. Miscellaneous content requirements ====
  
 1. Developers, Documentors, and potential Documentors are directed to on-site or DIG-maintained documentation for procedures on submitting code to the the community. 1. Developers, Documentors, and potential Documentors are directed to on-site or DIG-maintained documentation for procedures on submitting code to the the community.
Line 164: Line 169:
 6. Accessibility users can access a high-level overview of project accessibility efforts describing people, organizations, teams, and processes involved. 6. Accessibility users can access a high-level overview of project accessibility efforts describing people, organizations, teams, and processes involved.
  
 +7. LIS users can access a high-level overview of the Evergreen project organized in a way to help professors and students study it in an LIS or other academic context.
  
 ---- ----
 +
 ===== Deprecated Files ===== ===== Deprecated Files =====
  
Line 185: Line 191:
  
 [[http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen_community_web_team_planning_committee_page|WebTeam Home Page]] [[http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen_community_web_team_planning_committee_page|WebTeam Home Page]]
- 
  
webteam/user_stories/2011.1296701892.txt.gz · Last modified: 2022/02/10 13:34 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.