Difference between revisions of "Other Meetings and Notes"

From Metadata-Registry
Jump to: navigation, search
Line 14: Line 14:
  
 
* 10:00-11:00
 
* 10:00-11:00
** Define feature set, with basic tasks to accomplish for each
+
** Define coarse feature set, with basic tasks to accomplish for each
  
 
* 11:00-noon
 
* 11:00-noon
** Attach priorities to each feature  
+
** Attach priorities to each feature in terms of stakeholder and client satisfaction:
 +
***A (must have)
 +
***B (nice to have)
 +
***C (add it if we can)
 +
***D (future grants)
 +
** Determine complexity and assess risk for each feature
  
 
* 12:30-1:30
 
* 12:30-1:30
 
** Road map, includes timelines and milestones [a.k.a. "release dates"--may be internal]
 
** Road map, includes timelines and milestones [a.k.a. "release dates"--may be internal]
 +
*** Try to assign 'must have' features to milestones
  
 
* 1:30-2:00
 
* 1:30-2:00

Revision as of 14:17, 13 October 2005

F2F Meeting, Oct. 14, 2005, Ithaca, NY

Agenda

  • 9:00-10:00 Goals for the project: defining "success"
    • Is it usage? If so, how many (users, vocabularies, terms?)
    • Is it functionality? (can do all five below? and are all functions equally important?)
      • Creating/registering/maintaining a scheme (controlled vocabulary) and its member terms
      • Creating/registering/maintaining a schema (element/property set) and its member terms
      • Creating/registering/maintaining an application profile
      • Creating/registering/maintaining of a scheme-to-scheme mapping (value spaces)
      • Creating/registering/maintaining of a schema-to-schema mapping (element/properties)
    • How many "tools" will we need to build to accomplish these functions?
  • 10:00-11:00
    • Define coarse feature set, with basic tasks to accomplish for each
  • 11:00-noon
    • Attach priorities to each feature in terms of stakeholder and client satisfaction:
      • A (must have)
      • B (nice to have)
      • C (add it if we can)
      • D (future grants)
    • Determine complexity and assess risk for each feature
  • 12:30-1:30
    • Road map, includes timelines and milestones [a.k.a. "release dates"--may be internal]
      • Try to assign 'must have' features to milestones
  • 1:30-2:00
    • Review progress
    • Review task lists
  • 2:00-3:30
    • Add external review and testing tasks/timelines?
  • 4:00-5:00
    • Communication, documentation, meetings
      • Can we agree on "communication protocols" amongst the group?
      • How often do we need F2F meetings, telecons?
      • What are our expectations re: internal and external documentations?