“agile” as key to collaboration on nyu digital collections discovery initiative
TRANSCRIPT
“Agile” as Key to Collaboration on NYU Digital Collections Discovery Initiative
Daniel LovinsJune 26, 2016
Intro
05/03/23 2
Top Down?
Intro
05/03/23 3
Collaboration Across Subcultures
Overview• Agile Development
• Implementing a Strategic Initiative
• Hydra Project
• From User Stories to Features
• Next Steps
Overview
05/03/23 4
Background
Background
05/03/23 6
Case Studies
Background
05/03/23 7
My Case Study
Background
05/03/23 8
Goal 4: “Establish processes and support structures that ensure we can select, acquire, preserve, and provide access to the full spectrum of research materials”
Initiative 4.3: “a plan to provide intellectual access to NYU-curated digital collections via the library's primary discovery-and-access interfaces”
Background
05/03/23 9
Background
05/03/23 10
Web Archives
Faculty Digital Repo
Spatial Data Repo
Lib Guides
BobCat (discovery Portal)
Hydra/ Fedora
Digital Library Pub.
Patrons
credit: http://rones.su/
Hydra as Middleware
Background
05/03/23 11
Credit: abkldesigns.com
Agile Development
Agile
05/03/23 13
Scrum Framework
Agile
05/03/23 14
Evolution of User Stories into Product Features
• Library ITS• Digital Library Technology Services (DLTS)• Collections & Research Services• User Experience (UX)• Knowledge Access Design & Development (KADD)
• Part of Knowledge Access & Resource Management Services (KARMS)
Agile
05/03/23 15
Initiative Participants
• Scrum Master• Product Owner• Development Team
Agile
05/03/23 16
Roles
• Library ITS• Digital Library Technology Services (DLTS)• Collections & Research Services• User Experience (UX)• Knowledge Access Design & Development (KADD)
• Part of Knowledge Access & Resource Management Services (KARMS)
Agile
05/03/23 17
Initiative Participants
• backlog grooming• sprint planning• daily scrums• sprint reviews• sprint retrospectives
Agile
05/03/23 18
Scrum Events
Agile
05/03/23 19
Agile
05/03/23 20
Backlog grooming
Agile
05/03/23 21
Evolution of User Stories into Product Features
Agile
05/03/23 22
Sprint planning
• Spatial Data Repository (SDR)• Faculty Digital Archive (FDA)• Ephemeral NGO Reports• Numeric Datasets• Archived Web Sites• Digital Library publishing (Drupal sites, digitized texts, video, audio,
etc.)
Agile
05/03/23 23
Initial Target Collections
Agile
05/03/23 24
Dedicated Portals
Agile
05/03/23 25
BobCat
Agile
05/03/23 26
User Story in Pivotal Tracker
Agile
05/03/23 27
User Stories into Product Features
Agile
05/03/23 28
Sprint planning
Agile
05/03/23 29
Cucumber Tests
Agile
05/03/23 30
SDR record in its native environment
Agile
05/03/23 31
SDR record as it appears in Ichabod
Agile
05/03/23 32
In-browser editing form in Ichabod
Agile
05/03/23 33
SDR record in Bobcat
Agile
05/03/23 34
Agile
05/03/23 35
More Complex Story 1
“As a curator, I want to be able to describe existing resources at the collection level so that I can add information to them.” Acceptance criteria: •All existing collections in Ichabod are changed to use a Collection object rather than Resource Set to store collection information
•Collection Abstract field exists, and is editable
•UI is unchanged as a result of this modification.
More Complex Story 2
As a collection curator, I want to see my resources organized in Ichabod by collection, because that’s the way I think.
Acceptance criterion: • There is a collection object in Rails with these fields: Collection Name,
Abstract, Rights, Discoverability Flag, Provider, and Department.
Agile
05/03/23 36
Next Steps & Conclusions
•Collect and refine user stories for additional resource sets• ISAW Flickr channel for archeology images• Ancient World Online blog posts• Digitized special collections (via finding aids portal)• Indian Ocean Postcards
•Integrate UX assessment more tightly into feedback loop
•Expand range of assessment inputs to include • application transaction logs• web analytics• direct interviews with students and researchers
Next Steps
05/03/23 38
Recap
05/03/23 39
Strategic Initiative: Bring together disparate collections
Agile Development• User story
• Functional requirement• Keep focus on user needs
• Backlog grooming• Sprint planning• Daily scrum
Support interdepartmental collaboration
