(Page 5)

Lark: Sprints 6 & 7 (April 22 - May 18, 2019)

GitLab links: https://gitlab.com/surfliner/surfliner/-/milestones/17 https://gitlab.com/surfliner/surfliner/-/milestones/14

Starlight

Starlight: Sprint 5 (April 8-19, 2019)

What was the goal of Sprint 5? Testing in staging environment at both campuses, bug fixes, theming (including the ability to apply a global theme), and getting Shibboleth configured for UCSB. What is the milestone that this sprint is supporting? Milestone 1 is to have an initial instance of the

Lark

Lark: Sprint 5 (April 8-19, 2019)

What is the goal of sprint 5? The sprint’s focus was on integrating the Postgresql persistence layer and Helm/Kubernetes deployment. What is the milestone that this sprint is supporting? The Milestone 1 is to have an initial stand-alone platform where we can create, edit, and retrieve authority records.

Sprint Review

Starlight: Sprint 4 (March 25-April 5, 2019)

What was the goal of Sprint 4? Get the Starlight code deployed to our both campus staging servers and UCSB production servers, testing new features in staging environment, theming, and setting up Shibboleth. What is the milestone that this sprint is supporting? Milestone 1 is to have an initial instance

Sprint Review

Lark: Sprint 4 (March 25-April 5, 2019)

What was the goal of Sprint 4? The sprint had two main goals: First and foremost, we set out to complete cloud-native deployments Lark into both campus’s environments. Second, we wanted to take our first steps toward configurable metadata models. This a key design goal and deliverable for the

Sprint Review

Starlight: Sprint 3 (March 11-22, 2019)

What was the goal of Sprint 3? Get the Starlight code deployed to our both campus staging servers and UCSB production servers, supporting single sign on with Shibboleth, and improving the test suite. What is the milestone that this sprint is supporting? Milestone 1 is to have an initial instance

Lark

Lark: Sprint 3 (March 11-22, 2019)

What is the goal of sprint 3? The sprint’s focus was on three areas: * Deployment * Documentation * Support expanded labels What is the milestone that this sprint is supporting? Milestone 1 is to have an initial stand-alone platform where we can create, edit, and retrieve authority records. Accomplishments of Sprint

Roles

What is a Product Owner?

Let’s start with the who. Who are the product owners? Currently, we have two products that we’re working on: Lark (the authority records platform) and Starlight (the digital exhibits platform). Each product has a product owner -- for Lark, it’s me (Jessica Hilt, UCSD) and Starlight, it’

Sprint Review

Lark: Sprint 2 (February 25-March 8, 2019, 2019)

What is the goal of sprint 2? We hoped to get to our first milestone -- an initial stand-alone platform where we can create, edit, and retrieve authority records. We did achieve this goal and we’re currently waiting to deploy. What is the milestone that this sprint is supporting?

Sprint Review

Starlight: Sprint 2 (February 25-March 8, 2019, 2019)

What was the goal of Sprint 2? Get the Starlight code deployed to our local staging servers, set up support single sign on with Shibboleth, continuing work on uploading and displaying PDFs as exhibit objects, and improving the test suite. What is the milestone that this sprint is supporting? Milestone

Sprint Review Featured

What is a Sprint Review?

If you are unfamiliar with Agile or Scrum, a sprint review is an informal meeting held on the last day of a sprint to review and share what the team has accomplished during the sprint. Typically (not always) this meeting will include some kind of demo. This meeting is an

Starlight

Starlight: Sprint 1 (February 11-21, 2019)

What was the goal of sprint 1? Setting up team environment. What is the milestone that this sprint is supporting? Milestone 1 is to have an initial instance of the Spotlight platform in production for both campuses. Accomplishments of Sprint 1: Collaboration tools - Really more of a Project Surfliner-wide

Lark

Lark: Sprint 1 (February 11-21, 2019)

What is the goal of sprint 1? The sprint’s focus was on establishing an initial direction and architecture for the project. As a push goal, we hoped to get to our first milestone -- an initial stand-alone platform where we can create, edit, and retrieve authority records. It was

Meeting

Data Model - Focus Group Update

We wanted to send out an update on the Project Surfliner data modeling focus group meeting we had on Monday, January 14th at UC Santa Barbara. The purpose of this meeting was to get Developers and Metadata folks on the same page about currently proposed metadata architecture (abstracting data model

Communication

Radically Transparent Communication

We don't want folks to feel left out, so we have adopted a strategy of radically transparent communication. It starts with this blog which will provide updates from meetings, sprint-reports, new releases, and general thoughts from the team. Feel free to follow the blog and get an email

Meeting

Project Surfliner Kick-off meeting

Overall the meeting was a success. We are still compiling our notes, and it will take some time to document our Spider Web exercise (so many post-it notes). By the Numbers: • We had 29 attendees • We had 22 UCSD Library attendees • We had 6 colleagues from UCSB join us • We

About

Project Surfliner - Our way forward

UCSD Library Information Technology Services (ITS) has been stalled from a development standpoint for the last year due to a few different factors. In particular, we have suffered from “analysis paralysis” in evaluating and selected a “solution bundle” from the Samvera Community. These solution bundles have names like Sufia, Curation