A core tenant of agile is that you can be flexible on features or timelines, never both.
We have a fixed or inflexible timeline – we have to migrate by 2023, when current systems will not be supported. Below is a story to communicate status and timeline.
The story below explains DSS as a book bindery and UFDC as a library built by that bindery.
Long ago, there was a book bindery. Thanks to technology magic, it could keep a copy of each book it bound. With this magic, the book bindery opened a library in the bindery building. Thus, two things were in 1 building:
This was fine at first, with only an occasional patron. The library grew and grew, with more and more patrons. Now, the library has millions of patrons. And, no elevators, and other things that are not okay. A new library is needed. And, now there is a hard deadline. The current building will be demolished in 2023. Also, the building is starting to fail because it cannot hold up under so many books and so many patrons and the building could collapse before 2023.
Thus, a plan was developed:
For the new library building, many other things are wanted (the new location has space for more, and things wanted include a garden and a colonnade connecting to archives; also, everyone wants improvements in how the books are classified, which requires working with many people in order to develop a plan). [Not MVP]
There is only 1 building and organization crew. If we spend time talking to them about the garden and other improvements, it takes time away from building the library. If we work on anything outside of core requirements, we are at risk of not having a new library before our current one ceases to exist. Anything not MVP must be treated as outside (garden/colonnade), and dealt with later, to ensure we have a new library before the old one is demolished.
While we only have 1 building crew (Digital Development Team), we do have library workers (DSS, SASC, LT&DS, Social Media, Curators, others), who are preparing for the new library (new UFDC), with clean-up projects underway:
FAQ in development - https://guides.uflib.ufl.edu/lts/newufdc
LTS Digital Development Team & Stakeholders are working on:
Items for user FAQ with new UFDC release
Garden (non-MVP items)
The new UFDC will use standard technologies and practices in use by other webscale systems as with UNT, Europeana, NARA, Getty, and others. Technologies include: Python, APIs, ElasticSearch, ReactJS, PostgreSQL and more. The new UFDC will have separate production and patron databases and operations.
The new UFDC relies on now mature standards and practices for digital libraries, with extensive information and exemplar systems available (e.g., UNT). Additionally, usability studies are informative from the old system for existing limitations and problems: