Child pages
  • Requirements Coordination

Versions Compared


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

Actionable Items
1) Share practices for gathering institutional requirements gathering (IU, Stockholm)
2) Establish processes for sharing local requirements with community and discussing

 Use Confluence to capture context specific Scenarios or workflows that can be translated into Use Cases and finally requirements

3) Situate requirements within context of Usage scenarios or pedagogical workflows
4) Capture usage scenarios and context in confluence for comment/critique
5) Meet on a monthly basis to discuss context specific Scenarios or workflows

Engage UX community experts in translating scenarios and workflows into requirements

Try to Avoid

Tool-centric discussions of "fixing" existing tools or matching functionalty in existing systems. 

review and comment upon scenarios
6) Work with UX community to translate usage scenarios into concrete requirements
7) Circulate requirements for comment -

Try to Avoid
1) Tendency to become tool centric-respond to existing functionality and seeking to "fix" or adjust or retrofit onto practice or alter to emulate design paradigms of existing systems
2) Creating requirements out of context