ADMIRAL PlanMeeting 9

From ImageWeb

Jump to: navigation, search

Contents

Sprint 9 Planning meeting

Meeting held on: 07-Jul-2010, 10:15-11:00

Present: DG / GK

Sprint Dates Effort Plan Planning meeting Review meeting
Sprint 9 07 Jul - 16 Jul 8 days sprint 9 plan sprint 9 planning sprint 9 review

Agenda

This was a very simplified planning meeting for a short sprint, with a focus on scheduling priority tasks from those already planned.

  • Calendar, duration and effort available (10 mins)
  • Task selection (activities for this sprint) (30 mins)
  • Scope barter, allocate effort and confirm plan (5 mins)

Meeting

Sprint duration and calendar

Duration 8 days: 07-Jul to 16-Jul (8 days).

A short sprint aimed at rebuilding momentum around priority tasks.

Record time available after committed activities

Total sprint duration: 8 days

Group planned activities:

  • Sprint planning (7 Jul, 0.5 day)
  • ICTF meeting (14 Jul, 1 day)
  • Project partners meeting (15 Jul, 0.5 day)

Available to schedule: 6.0 days

GK: 6.0-2.5 = 3.5 days available to schedule

  • CLAROS/MILARQ (8 Jul, 1.0)
  • Day off (9 Jul, 1.0)
  • ESXi/Datacite setup with Ben (16 Jul, 0.5)

DG: 6.0 days available

Focus for sprint

  • Test suite for RDFDatabank
  • User interface for viewing RDFDatabank submissions
  • Schedule meetings with Development and Behaviour groups
  • RDF support in Shuffl

Working towards:

  • Front-to-back, researcher-to-repository, test deployment
  • Capture dataset description as RDF
  • Package data+description and submit to Databank test system

Identify activities

  • Project partners meeting preparation (GK:0.25)
  • ICTF meeting preparation (GK:0.5)
  • Repository submission test suite (GK:0.5, DG:3.5)
  • Reposory submission display web page (DG:2.5, GK:0.25)
  • Shuffl load/save RDF (GK:2.0)

Tasks in possible scope for sprint

Project management and meetings

Technical debt and bugs

Shuffl load/save RDF

  • Add test cases for saving and loading RDF
  • Implement saving and loading RDF

Initial annotation tool based on Shuffl

  • Implement and test Shuffl card for dataset annotation

ADMIRAL access control configuration

  • Survey available tools, summarize problems
  • Propose outline design for configuration tool
  • Review/discuss design for access control configuration tool
  • Create test cases for access control configuration
  • Implement access control configuration

User configuration and training for Development Group

  • Meeting to articulate security policy, name for system, group members, etc.
  • Create and deploy ADMIRAL data store instance
  • Face-to-face introduction, training, password changes
Personal tools
Oxford DMP online
MIIDI
Claros