Child pages
  • Requirements Coordination
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Current »

Actionable Items
1) Share practices for collecting local requirements priorities (IU, Stockholm)
2) Establish processes for sharing local priorities with community
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 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
  • No labels