Regular Attendees

• Andrew (on the road again)
• Bill
• Brad
• Chris (just can't wait to get on the road again)
• Dan
• Jonathan

General

• Call In To: Free Conference Call HD - DuraCloud Line

  Please note that we will be using the Free Conference Call HD line for this call. Information about calling into this line is available from the link above.

• - Indicates who will be taking minutes

Discussion Topics

Planning Board
Task Board

Actions from last meeting

Last meeting

Prepare Epics and start estimates - Dan and Brad
Prepare Stories with Estimates - All
Begin Closing initial Tasks - As Assigned in Jira
Get Remaining Budget Information - Jonathan

Related Information
DfR Software Next Steps - Jan 2012
2012-01-03 - Architecture Meeting, Temple University

Status

• Andrew
  • DuraCloud/Shib architecture updates
• Bill
• Brad
  • Unicon call today at 2:00 PM
• Chris
  • With Dan developed a strawman design for the Object Creation Service.
  • Continues to expand the design and incorporate feedback
• Dan
  • See Chris' note above.
• Jonathan
  • Scheduled Advisory Group Meeting Feb 3
  • Negotiating with Fluid
  • Discussions with Thorny, Mark

Minutes

• Jonathan:
  • Fluid preparing proposal for how to approach DfR; work with Smithsonian not clear yet.  Have a one pager discussing how to approach user experience for DfR proper:  6-7 weeks effort working with us and researchers to see what the researcher's current process is and their take on our direction.  Fluid will also be meeting with Thorny, date TBD in Toronto.
  • Drafting a plain engiish narrative of what the system does for use in future conversations and could use some help.  Target is to send end of day Wed to advisors.
  • Meeting Advisory group on Friday.
  • Draft arch document - can we get it in non- truncated form - See Dan's Arch Summary (link TBD)
• Discussion of Planning
  • Dan and Brad no coord last week;
  • Dan has added epics as the gold items on the planning board
  • Current epics will need to be broken into tasks, and may be spread across releases
  • Review of  Epics to see if they are complete:
    • Jonathan: What is the software developer view?  Is in it scope in the first phase.
    • Brad:  View as a high muckety muck: CIO or director of research (the pursestrings person), who wants to see aggregate usage statistics
    • DFR-18 (curator view) is considered low priority.
    • Chris: DFR-12 about backup / restore / monitor / sync? (duplicate = backup);  DFR-13 is the recovery
    • Hope to complete word smithing this week.

• • Meetings and Dev resources:
    • 1 hour per week on planning
    • Incremental releases: 3 as a target?
    • Link interations and releases at 2 month cycles?  Yes
      • 7 weeks of development and 1 of no code
    • How many F2F meetings?  2 initially
  • All please concentrate on near term getting the cards written for points assignment this week.  Followup via Skype chat.
  • Sync piece tasks are a high priority.
  • Steps are: Prioritize Epics, then write User Stories in the Epics, then break the User Story in Jira Tasks.
    • NB, Technical tasks can't be created without a userstory; so should we use a different issue type and link?
  •