User Tools

Site Tools


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 22:09] jimcranerwebteam:user_stories:2011 [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Criteria for New Website: Content and Functionality 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 (2/2/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. 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.
  
-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."+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.
  
 ====== Defining our User Groups ======= ====== Defining our User Groups =======
  
 "Potential" users are those considering an implementation of Evergreen for their organization. "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. "Consultant" users provide services to one or more Evergreen-using organizations.
Line 32: Line 32:
  
 "Accessibility" users participate in ensuring Evergreen software, documentation, and website are as accessible to as many users as possible. "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 ====== ====== Functionality-related Requirements ======
Line 163: 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.
  
 ---- ----
webteam/user_stories/2011.1296702559.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.