Difference between revisions of "ESC User Stories"

From Earth Science Information Partners (ESIP)
(Created page with "==What do we do?== * Develop user stories so for: ** ...you to illustrate the concept of the ESC to your constituents. ** ...as input to other tracks (Technology, Sociological Im...")
 
m
 
(One intermediate revision by the same user not shown)
Line 6: Line 6:
 
** ...minimally PPTs (already have three from [[Earth Science Collaboratory User Stories | ESIP July 2011]]:  The "Novice" Researcher (Lynnes); The Expert Researcher (Kuo); Science Assessment (Wee)
 
** ...minimally PPTs (already have three from [[Earth Science Collaboratory User Stories | ESIP July 2011]]:  The "Novice" Researcher (Lynnes); The Expert Researcher (Kuo); Science Assessment (Wee)
 
** ...possibly indexed by some canonical representation of discipline, audience type (can we use [[Earth Science Collaboratory User Model]]?), <others> (see below)
 
** ...possibly indexed by some canonical representation of discipline, audience type (can we use [[Earth Science Collaboratory User Model]]?), <others> (see below)
** ...possibly indexed by EarthCube capabilities (see below)
+
** ...possibly indexed by NSF Earth^3 capabilities (see below)
 
* Develop canonical representation for index to enable
 
* Develop canonical representation for index to enable
** ...identification of missing user story types
+
** ...identification of missing user stories
** ...identification of opportunities that have been missed (e.g. if somebody realizes a powerful user story that can be enabled by some combination of the index)
+
** ...identification of opportunities that have been missed (e.g. if somebody realizes that a powerful user story can be enabled by some combination of the index)
* Develop mapping of user stories to NSF EarthCube capabilities list? (http://earthcube.ning.com/page/capabilities, dated 2012-12-16), but first:
+
* Develop mapping of user stories to NSF Earth^3 capabilities list? (http://earthcube.ning.com/page/capabilities, dated 2012-12-16), but first:
 
** ...are the 14 capabilities useful for this purpose?  (some are more obviously useful than others)
 
** ...are the 14 capabilities useful for this purpose?  (some are more obviously useful than others)
** ...is the capability mapping useful in forming requirements in the Technology track?
+
** ...is the capability mapping useful for informing requirements development in the Technology track?
* Questions to start on:
+
* Questions:
** Which is more useful for the development of user requirements in the Technology track?  Index or capabilities?   
+
** Which is more useful for the development of requirements in the Technology track?  Index or capabilities?   
** If we proceed with developing some form of an index, ideas for dimensions of this index (e.g. audience type, discipline, etc) and identify small group of persons to create values for each dimension?
+
** Ideas for dimensions of this index (e.g. audience type, discipline, etc)?  (Again, see [[Earth Science Collaboratory User Model]] to avoid starting from scratch on one possible dimension)
** Similarly, if the capabilities mapping activity is useful, small group of persons IDed to take charge of it?
+
** Do we need to modify the capabilities list proposed by NSF Earth^3 for ESC story purposes?
* Proposed activity: strawman to for shooting arrows at... present existing 3 use cases against the (A) index and (B) capabilities to generate ideas about how to iterate this forward (BW to come ready with a slide or two)
+
* Proposed activity: Strawman for shooting arrows at... present existing 3 use cases against the (A) index and (B) capabilities to generate ideas about how to iterate this forward (BW to come ready with a slide or two)
 
* Comments?
 
* Comments?
  

Latest revision as of 14:45, December 29, 2011

What do we do?

  • Develop user stories so for:
    • ...you to illustrate the concept of the ESC to your constituents.
    • ...as input to other tracks (Technology, Sociological Impacts, Programmatic constraints)
  • Continue developing the repository of stories
    • ...minimally PPTs (already have three from ESIP July 2011: The "Novice" Researcher (Lynnes); The Expert Researcher (Kuo); Science Assessment (Wee)
    • ...possibly indexed by some canonical representation of discipline, audience type (can we use Earth Science Collaboratory User Model?), <others> (see below)
    • ...possibly indexed by NSF Earth^3 capabilities (see below)
  • Develop canonical representation for index to enable
    • ...identification of missing user stories
    • ...identification of opportunities that have been missed (e.g. if somebody realizes that a powerful user story can be enabled by some combination of the index)
  • Develop mapping of user stories to NSF Earth^3 capabilities list? (http://earthcube.ning.com/page/capabilities, dated 2012-12-16), but first:
    • ...are the 14 capabilities useful for this purpose? (some are more obviously useful than others)
    • ...is the capability mapping useful for informing requirements development in the Technology track?
  • Questions:
    • Which is more useful for the development of requirements in the Technology track? Index or capabilities?
    • Ideas for dimensions of this index (e.g. audience type, discipline, etc)? (Again, see Earth Science Collaboratory User Model to avoid starting from scratch on one possible dimension)
    • Do we need to modify the capabilities list proposed by NSF Earth^3 for ESC story purposes?
  • Proposed activity: Strawman for shooting arrows at... present existing 3 use cases against the (A) index and (B) capabilities to generate ideas about how to iterate this forward (BW to come ready with a slide or two)
  • Comments?

How do we do it?

  • Use input from other tracks (Technology, Sociological Impacts, Programmatic constraints).
  • ID small groups of three persons to create short two page deliverables as input to other tracks (schedule and actual deliverables to be determined)
  • Comments?