Release 3
Release 3
Link to Minimum Viable Product for the Pilot updated 30/6/14
Iteration 10 goal:
- An External Examiner can copy and paste into the report
- An External Examiner receives a reminder to submit report
- A Key Contact can see the report status on the dashboard
- The distribution list for both colleges and schools is maintained so that users can be notified upon submission of a report by the External Examiner
Link to iteration 10 project report to Board
| Key | Summary | Status | Story Points (15) | ||
|---|---|---|---|---|---|
| STU235-34 | Amend Deadline Dates (SEE-42) |  Done | 2 | ||
| STU235-62 | Automatic prompt to Submit Report (SEE-81) | Done | 2 | ||
| STU235-63 * | Automated confirmation of Report Submission to EE (SEE-82) | Done | 1 | ||
| STU235-66 | Copy and Paste into Report (SEE-87) | Done | 2 | ||
| STU235-98 | Status Management | Done | 1 | ||
| STU235-100 | Usability enhancements | Done | 2 | ||
| STU235-105 | College/School Distribution Lists | Done | 3 | ||
| STU235-107 | Contributor Dashboard | Done | 1 | ||
| STU235-110 | Multiple Roles/Dashboards testing | Done | 1 | ||
Issues Not Completed | |||||
| Key | Summary | Status | Story Points (2) | ||
| STU235-47 * | DPA Check (SEE-96) |  In Test | 2 | ||
| STU235-113 | Importing External Examiners and Appointments into EUCLID (no build) | In Progress | 0 | ||
| STU235-118 * | MyEd Channel |  To Do | - | ||
Iteration 10 product review and retrospective
| Details | Actions | Owner | Status |
Story Points completed 15 (out of 17) | n/a | ||
Achievements
| n/a | ||
Issues - DPA check: this was delivered, however some final nice-to-have formatting changes to the DPA check, will be held back to next scheduled release after the pilot (the pilot will run from Sept to Nov) - Importing External Examiners and Appointments into EUCLID: to be done end August once data have been received by pilot Schools -MyEd Channel to be done as part of follow up project STU244 - Some new navigation issues were picked up during the last demos , these will be recorded (by Brenda) as new user stories to prioritise with the other feedback from users which will be captured during the pilot. Two prioritised user stories are being delivered for the start of the pilot as part of STU244 follow up project. | Manage EE data into EUCLID
| Brenda | on going |
| -Deploy BI Suite to Live still oustanding end July | Production to deploy | Brian | Done 12/8 |
Iteration 9 (26/6-9/7) goal:
- Corporate Reports Rework and use of the BI Suite Info Space facility to view quantitative details about EE process and Quality Assurance data have been demonstrated to User Representatives
- College staff can use Info View to monitor report receipt and progress
- All Users can access the Search screen & testing is completed
- An External Examiner can copy and paste into the report
- An External Examiner receives a reminder to submit report
- A Key Contact can see the report status on the dashboard
- The distribution list for both colleges and schools is maintained so that users can be notified upon submission of a report by the External Examiner
User Stories
| Key | Summary | Status | Story Points (20) |
|---|---|---|---|
| STU235-38 | Monitoring of Report/Receipt using InfoView (SEE-92) | Done | 1 |
| STU235-48 | Search screen to retrieve of Reports/Responses- SEE-33 | Done | 3 |
| STU235-62 | Automatic prompt to Submit Report (SEE-81) | Ready for Test | 2 |
| STU235-66 | Copy and Paste into Report (SEE-87) | Ready for Test | 2 |
| STU235-91 | Create an External Examiners Infospace providing EE Quantitative Data (SEE-60) | Done | 2 |
| STU235-92 | Create a set of reports providing Qualitative information from EE Universe (SEE-65) | Done | 5 |
| STU235-98 | Status Management | Ready for Test | 1 |
| STU235-110 | Multiple Roles/Dashboards testing | Ready for Test | 1 |
| STU235-114 | Testing final wording for notifications | Ready for Test | - |
| STU235-105 | College/School Distribution Lists | Ready for Test | 3 |
Iteration 9 product review and retrospective
| Details | Actions | Owner | Status |
Story Points completed 11 (out of 20) Others are at testing: to be completed when Brenda is back from Annual Leave, as agreed. | Test user stories | Brenda | Done |
Achievements - BI Suite demo to users and feedback/rework done - 2nd demo to the pilot schools: end to end process was shown and positive feedback received. - managed to turnaround change of requirements for the distribution list to accomodate the College group email list. - reviewed requirements for iteration 10 with Developer and User Rep | n/a | ||
Issues - testing feedback outstanding, to be done in iteration 10 - Info Space Test still not available. Used Dev pointing to Test database for demo. - BI Suite still be deployed to Live. Accounts are required and developer time required - fewer development days due to staff unavailability (3 days) | Organise BI deployment w/b 28/7 | Jamie | Done |
Iteration 8 (12/6-25/6) goal:
- Thematic analyst & administrator can run Corporate Reports and use the BI Suite to view quantitative details about EE process and Quality Assurance data
- User can search reports for current EE cycle with a set of search criteria
- Dashboards will be available to view for External Examiners, Key Contact and Contributor
- A college administrator can view the reports which are late
- A key contact or college administrator can write notes on a report
- A Payment administrator can view the reports requiring a payment to be initiated
- Users are notified of changes during the EE report/response lifecycle.
user stories
| Key | Summary | Status | Story Points (24) |
|---|---|---|---|
| STU235-31 | Recording and Viewing Notes (SEE-38) | Done | 2 |
| STU235-35 | Notification of change in the stage of a report (SEE-45) | Done | 3 |
| STU235-38 | Monitoring of Report/Receipt using InfoView (SEE-92) | Not completed: to be demo | 1 |
| STU235-48 | Search screen to retrieve of Reports/Responses- SEE-33 | Not completed: one test scenario outstanding | 3 |
| STU235-91 | Create an External Examiners Infospace providing EE Quantitative Data (SEE-60) | Not completed: to be demo | 2 |
| STU235-92 | Create a set of reports providing Qualitative information from EE Universe (SEE-65) | Not completed: to be demo | 5 |
| STU235-103 | External Examiner Dashboard | Done | 1 |
| STU235-104 | Key Contact Dashboard | Done | 2 |
| STU235-107 | Contributor Dashboard | Not completed: to be delivered by Search user story | 1 |
| STU235-108 | Payment Administrator Dashboard and Recording Payment request | Done | 1 |
| STU235-109 | College Administration Dashboard | Done | 3 |
Iteration 8 product review and retrospective
| Details | Actions | Owner | Status |
Story Points completed 12 (out of 24)
|
| Brenda | Done |
Achievements - handover of requirements done - testing started earlier in the ieration, providing earlier feedback to developers to work on - all dashboards completed with the search facility. To be reviewed by User Reps - Reports has been demo to users, and feedback reworked | Send Dashboards online links to Users for usability feedback. Can be tested on line | Brenda | Done 30/6 |
Issues - BI Suite was not stable. Prevented us from demo to users both Reporting rework and InfoSpace build. To be rescheduled | Reports demo 29/6- Info Space demo 29/6 using Dev environment pointing to Test database | Brenda: report Franck: InfoSpace | Done |
Link to Report sent to Board 4/7
Iteration 7 (29/5-11/6) goal:
- User can view the corporate reports.
- User can view the stages on an EE report.
- An administrator can view the report's coverage, response, key dates and people involved.
- Key contact can allocate a response co-ordinator to a report
- Key contact, EE and response co-ordinator dashboards are available. An EE can access key University information via links from the dashboard.
- Users are notified of changes during the EE report/response lifecycle.
| User stories | Category | Stories points | Status |
| Create EE Universe in BI Suite | Thematic Analysis | 5 | Done |
| Workflow Management | Report administration | 1 | Done |
| View Report Details | Report administration | 1 | Done |
| Allocate Response Coordinators | Report administration | 1 | Done |
| Key Contact dashboard | Report administration | 2 | Not Completed |
| EE Dashboard | Report administration | 1 | Not Completed |
| View EE Handbook | External Examiner | 1 | Done |
| Response Co-ordinator dashboard | EE Report Assessor | 1 | Done |
| Notification of change in a state of a report | Report administration | 3 | Not Completed |
| Create a set of reports providing Qualitative information from EE Universe | Thematic Analysis | 5 | Not Completed |
Iteration 7 product review and retrospective
| Details | Actions | Owner | Status |
Completed 10 Story Points out of 21 planned User stories not completed and status:
| carry over to iteration 8 | Franck | Done |
Achievements
| Set demo for InfoSpaces/Reporting with user reps w/b 16/6 | Franck | Done |
Issues -Some user stories have dependencies between each other, preventing sign off. Agreed that BA should only test the conditions of satisfaction listed in the user story. If they pass, BA will sign off. If it requires new conditions of satisfaction, this needs to be addressed as a new user story. | n/a | Brenda | Done |
- Set test data data for reviewing dashboards (on line) by user reps. Feedabck to be prioritised and some can be addressed in the Usability Enhancement user story: External Examiner dashboard: Ian Response Corrdinator dashboard John Key contact dashboard Rosie | prepare test data and contact user reps- emailed the reps with the dashboards and copies of the notifications 30/6 | Brenda | Done |
| -Fewer development days than planned (2 day leave) | n/a |
Link to report sent to Board sent 17/6
Iteration 6 (15/5-28/5) goal:
- Dasboards will be signed off by user representatives, and the BI Suite will have been built, so that reporting can start
- An administrator can amend key contact & payment administrator.
- The EE Reports will be finalised with the Questions & Sections following sign off from the Policy Working Group, as well displayed dependant on the nature of teh coverage.
| User stories | Category | Stories points | Status |
| Amend Key contact on a report | Report administration | 1 | Done |
| Manage Programme EE Questions | External Examiner | 2 | Done |
| Apply final Section and Question test to EE report template | System administrator | 1 | Done |
| Key contact/payment administrator maintenance | System administrator | 3 | Done |
| Dashboard design | External Examiner | 2 | Done |
| Allocate Response Co-ordinators | Report administration | 5 | Not Completed |
| Create EE Universe in BI Suite | Thematic Analysis | 5 | Not Completed (built but not tested) |
Iteration 6 product review and retrospective
| Details | Actions | Owner | Status |
Stories points delivered 9 out of 19 planned- Reasons: Fewer development days used (3d spent as training/holiday) Issues met during this iteration: -dependency with SAC028 Upload of Awards project, which deployment of EUGEX to Live was delayed until 19/5. This prevented the EE EUGEX code deployment to Test until 20/5. Then we found out that the streams in Test were broken. This was only rebuilt on 26/5: this delayed the Test sign off of the creation of EUGEX views/overnight import into EE and the testing of the Universe -Allocate Response Co-ordinators/Readers user story not completed as the user rep could not commit time for signing off the proposed design (Exam period) & product owner (Duncan) was on holiday for a week-Moved to iteration 7. Instead the developer started on the dashboard build, which design had been signed off. | n/a | ||
Allocate Response Co-ordinators/Readers requirement is best to be addressed as two separate user stories | create 2 user stories for iteration 7 (Co-ordinators) & 8 (Readers). The latter needs further analysis | Duncan | Done |
Lesson learned: should have done a separate design user story (spike) for earlier review by Pdt Owner, then sign off by user rep. With hindsight, product owner to plan/book time with user rep. Recommended to have face to face review with user reps
| review user story and identify need for design spike, then plan review with user reps | Duncan/Brenda | Done |
Link to Report sent to Board 9/6