Skip to content

Working Process for the Site

Simon Worthington edited this page Jan 10, 2022 · 14 revisions

There are two work processes for committees to input into the site:

See instructions below

  • UX persona and process setup for committees to be able to run UX design and evaluation processes, and
  • Work packages management using GitHub wiki, projects, and issues - 30 minutes minimum setup, depending on work package size.

Reference examples provided for Groups:

  • UX persona and process setup: See the Groups UX Plan here - 4 hours setup;
  • Work packages management: followed by Groups work package management here - minimum 30 minutes setup per work package, but depends on work package size.

Instructions: UX persona and process setup for committees

UX FORCE11 Committees

UX Personas: How it works

User Experience (UX) analysis method works by describing user groups and defining these as personas. Wants and problems are then assigned to the personas and the UX process is to storyboard the personas 'experience' with say your website to see how to satisfy these personas and what questions arise.

Example process

  • Persona: name (define)
  • Wants - list
  • Problem - list
  • Storyboards
  • Test: Does what is produced, messaged - facilitate the persona’s requirements
  • Rinse-repeat

Example personas

Personas: Groups

Groups Personas have been through one round of development (Dec 21: SW, TC)

  1. Proposer;
  2. Participant;
  3. Peer

See the groups UX Plan here.

Personas: Overall website

  • Members
  • Researchers
  • Stakeholder scholcomms organisations

Instructions: Work packages

Work packages that are coordinated using GitHub wiki and GitHub issues and Slack. If a private work package is needed with a private GitHub repository or GitLab project can be used.

A coordinator from a FORCE11 Committee will need to be assigned responsibility for a work package and will work with the Web Committee.

Process

  1. Review coordinator appointed
  2. Short description made
  3. A limited number of goals are set
  4. Deadline date set
  5. Task assigned and resolved

Tools and protocols

  1. Use one GitHub wiki for all of a Committee work package descriptions
  2. Use one GitHub Project for all of a Committees work packages
  3. Use GitHub tasks to log jobs
  4. use GitHub Labels to ID tasks etc. Use work package number #wp1 etc., use short committee name to ID work packages #groups etc.

Examples:

Overviews