Category: Project Management

FOLIO Sprint Review 60-61

  1. 0:00 Welcome, new team coming in Sprint 64: Concorde (members currently on Foliojet and Core Functional); focus coming soon.
  2. 1:43 new team members on Core Functional:  
    1. Volodymyr Rohach -EPAM (Concorde)
    2. Dmytro Popov – EPAM (Concorde)
  3. 2:00 new team member on Stripes Force: Ryan Berger (EBSCO)
  4. 2:20 new team members on Thunderjet:
    1. Andrei (Anddrews) Kandratsenka – JS Developer
    2. Mikita Siadykh – JS Developer
  5. 2:40 new team members on Folijet:
    1. Anatolii Starkov – BE Developer
    2. Taras Tkachenko – FE Developer
    3. Viktor Soroka – FE Developer (Concorde team)
    4. Sergiy Sergienko – FE Developer (Concorde team)
  6. 3:03 All Concorde Team members:
    1. Viktor Soroka
    2. Oleksii Popov
    3. Dmytro Popov
    4. Sergiy Sergienko
    5. Volodymyr Rohach
  7. 3:19 Q2 2019 Release details
    1. Interim release (Q2.1) May 17th
    2. Q2 release July 1st
  8. 5:16 Definition of done (no change)
  9. 5:24 slides for team highlights of last couple of sprints
  10. 6:14 Thunderjet/Acquisitions demo: organizations (formerly vendors) module; serials check-in; interaction between check-in and inventory
  11. 20:50 Folijet demo: backend infrastructure — source record storage, connecting to inventory and marccat, data import UI/job profiles
  12. 30:00 Vega demo: requests
  13. 33:50 @Cult demo: editing, cataloging workflow
  14. 40:00 ERM demo: integration of agreements app and eholdings app
  15. 47:45 Core Functional demo: requests and locations, check-in/out notes
  16. 1:01:40 FOLIO Quality Dashboard highlights
  17. 1:06 next up:
    1. Sprint 62 (April 22nd-May3rd)
    2. Sprint 63 (May 6th-17th)
    3. Interim Q2.1 Release May 17th
  18. 1:06:14 Plans for coming sprints
    1. Core Platform
    2. Core Functional
    3. Stripes Force
    4. UNAM
    5. @Cult
    6. Acquistions
    7. ERM
    8. Folijet (Data Import)
    9. Spitfire
    10. Vega
    11. Concorde

FOLIO Sprint Review 58-59

0:00 Welcome; only a couple of team changes for Core Functional
1:06 Q1 2019 Release details
3:04 Definition of Done
4:49 Sprint Highlights for the various groups
5:55 Thunderjet/Acquisitions demo; purchase orders
17:08 Folijet demo; file extensions, uploading marc records
28:45 Vega demo; notice templates, request expiration feature
37:45 Spitfire demo; eholdings application
44:00 Stripes Force demo; UI menus
48:15 Core Functionality demo; requests, item missing, circulation rules editor
1:06:30 Core Platform demo; developer utility for parsing log files, response time improvements, utilities, edge modules
1:20 QA Update Q1 2018 Bug Fest Report; Bug Triage Process, bug priority

EBSCO Beta Partners meeting

The three institutions partnering with EBSCO as Beta partners for FOLIO implementation and support services met on March 25th-27th in the DuBois Library at  UMass / Amherst .   The Folio implementation teams  from Chalmers University in Sweden, The University of Alabama, and the Five Colleges met over the course of three days along with staff from EBSCO representing implementation services, FOLIO support, and FOLIO product owners from various functional areas.  The teams had a chance to meet each other and various EBSCO personnel in person for the first time.   They also discussed local implementation and communication plans, heard updates on the status of various modules and the overall FOLIO project from various product owners The FITs and product owners also spent significant time reviewing features and gap analysis related to FOLIO feature development.   The various FOLIO implementation teams hope this is a start of a long and fruitful collaboration on the path to implementing and using FOLIO.

FOLIO Timeline

The FOLIO Implementation Team (FIT) has been reviewing our criteria for determining when we will go live with FOLIO. Go-live is when FOLIO becomes our system of record for all primary functions and we discontinue use of Aleph. Some of our fellow early adopters have reached their established decision point for go-live by July 2019 and the required features are not fully developed. Most have pushed back their go-live date to July 2020 in order to stay aligned with their fiscal year start.

FIT is reviewing the list of go-live features and determining a date by which those features need to be functional in advance of go-live. The goal is to choose a software release by which we would need to have functionality developed in order to go live up to 6 months later. We are currently looking to asses the software releases in  Q3 (October 2019) and Q4 (January 2020) for required functionality.  This would provide a implementation window with a go-live date in the Summer of 2020.

 

FOLIO Sprint Review 56-57

https://www.youtube.com/watch?v=0M2AnQyMphQ

  1. 0:00 Welcome; new team members:
    1. Anatolii Starkov on the Core Functional Team
    2. Ruslan Lavrov on Folijet
    3. Arton Agroni and Irene Chang on UX Designers.
  2. 1:37 Q1 2019 Release details
  3. 4:13 Definition of Done
  4. 8:25 Sprint Highlights
  5. 9:15 Thunderjet/Acquistions demo; acquisitions & inventory integration
  6. 20:48 Folijet demo
    1. file support functionality
    2. circulation module notice policies
    3. due date functionality
  7. 41:55 Core Functionality demo
    1. request policies
    2. print slip print defaults
    3. hold shelf expiration at service point
    4. ui-check-in
  8. 51:45 ERM sub-group demo
    1. license functionality
  9. 1:03:01 QA Update
    1. Escaped Defects
    2. Integration Testing
    3. UI Automated Testing
    4. Performance
  10. 1:22:22 Next sprints:
    1. Sprint 58 (February 25 – March 8)
    2. Sprint 59 (March 11 – March 22)
  11. 1:22:45 Plans for Coming Sprints
    1. Core Platform
    2. Core Functional
    3. Stripes Force
    4. UNAM
    5. @Cult
    6. Acquistions
    7. ERM
    8. Folijet (Data Import)
    9. Spitfire
    10. Vega

FOLIO Sprint Review 54-55

 

https://www.youtube.com/watch?v=I8yWa_zJxnM&t=3s

  1. 0:00 Welcome; Core Team split into two groups: Core Platform and Core Functional
  2. 1:12 Core Platform Team Force membership update
  3. 2:00 Core Functional Force membership update
  4. 2:49 Stripes Force membership update
  5. 3:07 UNAM Team membership update
  6. 3:31 Q4 Release notes
  7. 4:37 Q1 2019 Release details
  8. 5:08 Definition of Done
  9. 10:23 teams’ sprint highlights slides
  10. 11:12 Acq-Orders demo
  11. 26:52 Folijet demo; file uploads, extensions
  12. 34:45 Stripes Force demo; UI filters
  13. 38:03 Vega demo; renewal overrides
  14. 44:31 UNAM demo; patron blocks
  15. 100:52 Core Functional Team demo; status views, notes
  16. 109:45 next sprints:
    1. Sprint 56 (January 28 – February 8)
    2. Sprint 57 (February 11 – February 22)
    3. 1:10:58 Plans for Coming Sprint(s)
    4. 1:10:19 Q4 QA Update – Bug Fest Week (1/7 – 1/11), Escaped Defects, UI Automated Testing, Performance slides

 

First Named release

Patrick Zinn, Director of Marketing, University Libraries at Texas A&M is the creator of the Bee logo for FOLIO. If you would like to know the history of the bee for FOLIO you can read this story posted by Patrick. “To bee or…Hey there is a Bee”. In the world of nature bees must be able to find plants and flowers to both pollantate and feed from in order to survive.  In the world of FOLIO we need librarians, developers, designers, and service providers to contribute to the community and to the project so that it matures into one of those products that is globally trusted and supported. The people that are active in the FOLIO community now can say, “we were there when….” One way to ensure the bees survival in nature is to plant wildflowers and when a FOLIO group started to think about what to start naming product releases the decision came easy, wildflowers are found everywhere and are needed for a health bee community. The very first named release is called Aster. All releases from now on will be named for wildflowers in ABC order.  If you would like to know what all was included in the Aster Release please click on the release notes.

Record Merge Working Group

The first meeting of the Five College record merge working group will be later in February.  This group will establish a charge based on some previous brainstorming. Some examples of the recommendations this working group has been asked to develop are:  What is the scope of records we want to include for de-duplication?

  • What local fields from each record needs to be included in a new record?
  • What record should be used as base for a new record?
  • What criteria should be used for matching?
  • Should this work be done in conjunction with another vendor? With EBSCO? In-House?

The members of the committee are Rebecca Henning (Amherst), Colin Van Alstine (Smith),  Jennifer Eustis (UMass), Sharon Domier (Five Colleges/UMass) and Steve Bischof (FIT)

How decisions are made: FIT Funnel

FIT Funnel for decision making
FIT Funnel for decision making

FIT has created a graphical representation — a funnel  — to help clarify roles and responsibilities and conceptualize decision-making. The funnel is specifically for the Five College beta testing and migration aspects of the project; we know that many staff are becoming involved with the open source FOLIO community and that is great! We are happy to encourage that as well. The funnel image outlines the responsibilities and expectations of staff participating in each part of the FC project and illustrates how recommendations, feedback, and decision-making will proceed.

Look for your local FIT member to be discussing the funnel at an upcoming institutional staff meeting.