| Table of Contents | ||||
|---|---|---|---|---|
|
...
What institutions are providing funding for this project?
Boston Library Consortium
Midwest Collaborative for Library Services
Duke University (potentially)
What ReShare groups have a stake in the outcome of this project?
Any consortium using or considering the use of Returnables with an interest in CDL.
What non-ReShare groups need to be kept updated on the status of this project?
Questions
What questions do the EC, SC, and PM team have about this swimlane?
...
Name | Role | Responsibilities |
|---|---|---|
Debra Denault | Product owner |
|
BLC or MCLS staff? | Product manager |
|
Jason Skomorowski Mike Taylor | Developers |
|
Documentation | ||
QA testing |
Requirements
Requirement | Number of Days | Number of People | mod-rs | ui-rs | OpenURL | VuFind | Totals | |
|---|---|---|---|---|---|---|---|---|
1 | A new service type of “digital” will need to be created | 4 | 1 | ☑️ | 4 | |||
2 | Create a new state model based on the returnable state model to handle CDL requests | 20 | 1 | ☑️ | 20 | |||
3 | Modify request confirmation form to offer option to chose delivery by CDL | 10 | 1 | ☑️ | ☑️ | 10 | ||
4 | Add an institution-level configuration option for “will loan via CDL” | 20 | 1 | ☑️ | ☑️ | 20 | ||
5 | When building data rota, reference institution-level configuration for CDL | 10 | 1 | ☑️ | 10 | |||
6 | Ensuring the audit log stores the history of CDL requests, viewable by staff | 0 | 0 | 0 | ||||
7 | Add request state of “Awaiting digitization” to put items in after they’ve been pulled from the shelf | part of #2 | 0 | |||||
8 | Create CDL request fulfillment interface, with fields for URL and loan expiration date | 4 | 1 | ☑️ | ☑️ | 4 | ||
9 | After lending library fulfills the request via the fulfillment interface, send URL and loan expiration date to borrowing library and then automatically to borrowing library’s patron | 20 needs further research to confirm | 20 needs further research to confirm | |||||
10 | Create email template for CDL loan info sent to patron | 2 | 1 | ☑️ | ☑️ | 2 | ||
11 | Add request state of “Loaned via CDL” for lending library | part of #2 | 0 | |||||
12 | Add request state of “Borrowing via CDL” for borrowing library | part of #2 | 0 | |||||
13 | Add request state of “Borrowed Digitally” | part of #2 | 0 | |||||
14 | Add request state of “Loaned via CDL” for borrowing library | part of #2 | 0 | |||||
15 | Automatically set the request to a state of “Needs reshelving” on the lender’s side and close out the “loan” with the ILS (check in item message if enabled), when the CDL loan expiration date is reached. | 4 | 1 | ☑️ | 4 | |||
16 | Send an email alert to lending library staff with info about which physical items to restore to the shelves after their loans have been closed in ReShare | 2 | 1 | ☑️ | 2 | |||
17 | Create patron interface in VuFind for viewing request history, with different views for active and inactive requests | 25 | 1 | ☑️ | 25 | |||
18 | [Ideal functionality] Enable ReShare to accept an ISO request (actually an OpenURL) from ILLiad, and create a new CDL request from it | 0 | ☑️ | 0 | ||||
Total number of days work for development | 121 days | |||||||
24 weeks | ||||||||
6 months | ||||||||
19 | Project implementation services 4 hrs/week over 24 weeks (includes sprint management, testing, and progress reporting to stakeholders, Executive Committee, and Steering Committee) | 96 hours | 1 | 96 hours | ||||
Development: 121 days x 6 hrs/day = 726 hrs x $165/hr = $119,790 | ||||||||
Project Management: 96 hrs x $165/hr = $15,840 | Cost based on Index Data rates | $135,630 | ||||||
Scope
What is in scope for this swimlane?
What is out of scope for this swimlane?
Estimated Schedule
Deadline
Sprint cycles
Completion Criteria
This swimlane will be considered complete when…
Dependencies
What other projects/tasks depend on this swimlane being completed?
What other projects/tasks must be completed before this swimlane can begin?
Implementations & Other ReShare Priorities
...
Monthly reports by the product owner and product manager to ReShare Executive Committee and Steering Committee
To which non-ReShare groups?
Risks
Risk Area | Risk |
|---|---|
Scope | |
Resources | |
Schedule | |
Budget | Resource / time overruns |
Technology | |
Industry or market |
|
Other |
Timeline
Project Milestones | Estimated Completion Date | Notes | Communication Requirements |
|---|---|---|---|
Development of high-level workflows and needs | ~Fall 2022 | ||
Start of software design/development | ~January 2023 | ||
Request form | ~April 2023 | ||
Staff workflows | ~May 2023 | ||
Pilot testing | June-August 2023 | ||
Phase 2 | ~Summer 2023 |
Change Management
What is the process for changing timelines and resourcing?
Budget
Description | Amount | Date |
|---|---|---|
Development environment set up | ||
Development | 24 person-weeks | |
Project management | 96 hours | |
QA testing | ||
Deployment | ||
Ongoing maintenance |
Ownership of Intellectual Property
Describe who will own any intellectual property created as a result of the Contract. This may include aspects relating to work-for-hire, confidentiality, open source, derivative works, etc.
Payment Schedule and Sources of Funding
...
Who will develop technical documentation?
Development team
Who will develop user (library staff) documentation?
Product owner and stakeholder-contributed staff
Where will these live?
In the ReShare Returnables documentation system
Project Maintenance Plan
ReShare Core Implications
...
ReShare Adjacent Implications
What components of this project will be maintained by a Certified Service Provider?
Ongoing Support
What types of issues will be resolved by the CSP only?
Deployment and configuration;
Tier-1/tier-2 support
What types of issues will be considered as the responsibility of the ReShare community?
Foundational software support and maintenance
...