Child pages
  • Requirements Coordination

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

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

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

 Meet
3) Situate priorities within context of Usage scenarios or pedagogical workflows
4) Capture usage scenarios and context in Confluence for public 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) Establish channels of communication and processes for working with UX community to translate usage scenarios into concrete requirements
7) Circulate requirements for comment/review
8) Work with designers and developers to identify core services that are needed across tools to accomplish key pedagogical objectives
9) Document core processes and application of tools to these (ie what tools are your faculty using for notification, content creation, sequencing, presentation, etc)

Try to Avoid
1) Tendency to become tool centric-respond to existing functionality
2) Fixing, adjusting, or retrofitting functionality onto practice
3) Emulating design paradigms of existing systems
4) Creating requirements out of context
5) Gratuitous proliferation of tools

Requirements Coordination Group Discussion:

  • Stainablity vs Number of tools: what does "gratuitous" mean in #5?
  • Key item: TandL needs a key voice in the requirements process
  • Better job of documenting and sharing documentation