In Scrum, an agile methodology of software development, a sprint is a set period of time during which specific work takes place. Tasks and goals for the sprint are identified in a planning meeting that precedes the sprint. At the end of the sprint, the team meets to review the success of the sprint and identify lessons for the next sprint. See the Sprint Breakdown for the general timeline of the work expected from both Technology Services and campus offices and individuals (i.e., "Clients") involved in each sprint.
The current sprint (Sprint 18) runs from February 1, 2016 to March 11, 2016. See the Complete Sprint Schedule for links to past sprint details and the sprint calendar through March 2016.
|Project Name||Brief Description||Owner||Status|
|UP_ADM_EVENT_VW speed fix||Improving query performance while using this view.||Admission||Development|
|SAG: Financial checkbox||Will properly identify financial related concerns in relevant alerts.||Advising||Development|
|ReportExec patron data interface||ReportExec patron data interface (BOSS replacement.)||Business Services||Development|
|Campus Bundle 40||Install Campus Solutions Bundle #40 to ensure financial aid regulatory compliance and apply bug fixes and updates.
Will be installed Saturday, February 27.
|Financials 9.2 upgrade||Upgrade the Financials pillar from 9.1 to 9.2||Finance||Support|
|Payment Manager - Credit Card/ACH enrollees||Send Credit Card/ACH enrollees to the bank.||Finance||Development|
|ACA patch||Additional Oracle patch supporting ACA||Human Resources||Development|
|Financial Aid 2016-2017||Support for Financial Aid process 2016-17.||Student Financial Services||Development|
|Financial aid award letter - Ordering of awards||Change the order of awards that are listed on the paper award letter||Student Financial Services||Development|
|Person Info Enhancements||Various additions to the Person Info tool.||Student Affairs||Development|
|Identity Management- Phase 2 Design||Continuing to design overall system architecture.||Technology Services||Analysis|
|TS Responsibility||Client Responsibility||Current Sprint
|Week 1||Development||Respond to developer questions
Develop test plan
|February 1 - 5|
|Week 2||Development||Respond to developer questions
Review test plan, set up test data
|February 8 - 12|
Review client's test plan
|Respond to developer questions
Finalize test plan, test data
|February 15 - 19|
|Week 4||Provide testing support
Fix identified bugs
|End-to-end testing - Round 1
Document bugs in issue tracker
|February 22 - 26|
|Week 5||Provide testing support
Fix identified bugs
Prepare for Deployment
|End-to-end testing - Round 2
Proof of Testing due - WED 5 p.m.
Sign-off due FRI 5 p.m.
|February 29 - March 4|
|Week 6||Deploy to Production- TUE
Refresh Development- THUR
Refresh Test- FRI
|Prepare for deployment
Review in production
Communicate to users
|March 7 - 11|
Sprint 24: October 17 - December 2, 2016