Child pages
  • A Community Process for Requirements Gathering

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • We may want to discuss different processes for each of the three types of requirement gathering noted above, this might go something like:
    • Functional Visions
      1. Start with some type of fundamental learning theory, assessment model, etc. that would be important to support with Sakai (e.g. constructivism)
      2. Select a functional "theme" to brainstorm around (e.g. student created content, group work, interacting with guest experts, etc.)
      3. Brainstorm with a group of early adopter faculty at your local institution, record/capture outcome
      4. Write a narrative that captures the outcomes from the brainstorm (maybe also connect it back to underlying theory)
      5. If needed/possible, create a "persona" that would represent a composite of the early adopters at your local institution.
    • Use Cases
      1. Start with either an existing tool/workflow or one that is being consider for or already in development.
      2. Select an instructional theme or objective (e.g. students working on a group project)
      3. Through interviews/focus groups/brainstorms gather ideas on how the tool/workflow needs to be developed/designed to best support the theme or objective.
      4. Write a narrative or storyboard that captures the key ideas/outcomes.
      5. If needed/possible, create a "persona" that would represent a composite of the users.
    • Tool Requirements (this is mostly what we do today, IU has a well established and successful model for this)
      1. Start with an existing tool/early prototype/contrib.
      2. Collect feedback from users on challenges/problems they encounter using it.
      3. Develop solutions to challenges and review with users.
      4. Post JIRAs for those solutions that appear to have consensus support.

...