ReShare Swimlane Project Template

Summary

• What 3-4 functions will result from this swimlane?

Rationale and Strategic Fit

• Who does this benefit?  What impact will it have on library users?

• How does this advance the ReShare product and/or serve the ReShare community?

Goals

• What measurable or demonstrable outcomes should be achieved by the end of this project?

Stakeholders

• What institutions are providing funding for this project?

• What ReShare groups have a stake in the outcome of this project?

• 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?

Project Team

Requirements

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

• How will this work impact planned ReShare implementations?

• How will planned or unplanned implementations impact this swimlane?

• What projects do we say “no” to during this swimlane development?

• What will be delayed because of this project?

• What simultaneous work do we deem to be acceptable?

Collaboration and Communication Strategy

• When will reports on progress be made?

• By whom?

• To which ReShare groups?

• To which non-ReShare groups?

Risks

Timeline

Change Management

• What is the process for changing timelines and resourcing?

Budget

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

• What amounts will be paid by ReShare?  To whom?  When?

• What amounts will be paid to ReShare?  By whom?  When?

Hardware and Software Technology Requirements

• What server or cloud resource requirements are needed for this swimlane?

• What operating system?

• What development languages will be used?

• What will be included in the software stack?

Testing & QA

• What continuous testing procedures will be followed during this project?

• What community testing procedures will be followed during this project?

Deployment

• What are the anticipated deployment procedures?

• What impact will deployment have on other ReShare functions?

• What impact will deployment have on existing ReShare users?

Documentation

• Who will develop technical documentation?

• Who will develop user (library staff) documentation?

• Where will these live?

ReShare Core Implications

• What components of this project will ultimately be added to the core?

• What are the projected resources required to maintain this as part of the core?

• What is the source of funding for ongoing maintenance?

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?

• What types of issues will be considered as the responsibility of the ReShare community?

Future Development

• What planning process will be used to move the swimlane beyond MVP?

• Who should be involved in this planning process?

• What is the estimated timeline for beginning this planning process?