Release 2
Release 2 goal:
- The EE report will have system validations in place and be pre-populated with the EE personal details and course/programme coverage. It will have the final Section and Question text completed.
- The Response coordinator will be able to notify the EE with his response.
- The system administrator/support officer can view the set deadlines, create new report, maintain a list of key contacts at schools and colleges. He will be able to allocate to each EE report a response coordinator and readers. He will be able to monitor EE report receipt and response.
Iteration 3 (3/4 to 16/4 ) goal:
An External Examiner will be able to view the categorised response. The EE report validation will be working. The Response coordinator will be able to send the response to the EE by notification. Deadlines will be set and the system administrator can view them.
| User stories | Category | Stories points | Status |
| Usability on response coordinator view | Response Coordinator | 1 | Done |
| View Response by EE | External Examiner | 3 | Done |
| Send the response to EE | Response Coordinator | 2 | Not completed |
| EE report validations | External Examiner | 3 | Done |
| Define default deadlines for each stage | System administrator | 3 | Done |
Iteration 3 product review and retrospective (16/4)
| Details | Actions | Owner | Status |
Stories points delivered 10 out of 12 planned. Send the response to EE (2) was 50% built, there was issue with the format of the html version on the email sent. Product demonstrated Ok (https://www-beta.eers.is.ed.ac.uk/index.cfm) | n/a
| ||
Validation Story originally estimated as 3 story points required in fact an effort of 8 story points. The discrepancy in initial and real estimation was caused by:
| n/a | ||
During the review meeting it was confirmed that we are legally obliged to provide reasonable accommodation for users. User can’t use java version confidentially therefore we need to provide baseline version. However, it shall be discussed and agreed by Project Board, Product Owner, Anne-Marie and Project Manager if that approach is correct and what shall be considered to be the reasonable accommodation. | To define level of reasonable accommodation.30/4 Agreed with Greg, Duncan and Franck to take the existing approach to manage the baseline version (as most work already done) | Duncan | Done |
During the review meeting it was highlighted that due to the pressure from the Project Board and unexpected additional effort it wasn’t particularly good iteration. Once the difference in estimation was determined it wasn’t appropriately actioned and the validation story wasn’t re-estimated from 3 to 8 points. This created pressure within a team that aimed to respond to the Project Board expectation of delivery of 12 story points per iteration. It was highlighted that the team doesn’t have to deliver to the same velocity consistently. It shall be noted by the Project Board that especially at the beginning of the project the estimation may not be very precise. This changes as the project team goes along with the project but the velocity may still vary and non-delivery of 12 story points per iteration shouldn’t be seen as a failure. | To liaise with Project Board and explain velocity variation in Agile project. | Franck | in progress |
Product was demos to user group reps (Rosie, Kathryn, Ian and John) - Positive feedback was received and recognised by the team as a very good indicator on functionality improvements. As an implication of that meeting, the design of notification email has been agreed. Additional story that expresses users’ feedback will be added to the backlog with a title – UI Usability. | To add UI Usability user story. | Duncan | Done |
It was suggested that the user’s representatives could write down different scenarios of completing the report. That shall help identify more real issues that users may encounter whilst completing the report. | To liaise with user representatives to test the usability of the form Greg meeting Vicky on 20/5 | Duncan | in progress |
| It was requested that additional story points are required for having testing in order | add this in usability user story | Duncan | Done |
It’s been noted by Product Owner that the next iteration (5) may require more resources for testing. | To estimate additional support required.30/5: SSP will be testing the MV change, FB to help 14/5: SSP to test EUGEX views, Brenda to test | Duncan | Done |
| Backlog review meeting shall be arranged by the end of May. | To arrange backlog review meeting.due 12/5 14/5 3 new user stories created | Franck | Done |
| Kathryn Nicol notified that she will be on holiday for 3 weeks starting from 05.05 and replacement shall be seek. | To see replacement for user representative-David Williams will step in | Franck | Done |
Lesson Learned 1. Planning meeting shouldn’t be rushed – all stories shall be discussed in detail to reduce the risk of story to be underestimated 2. We need to be more proactive at the stage when we know that a story is bigger than expected. It could help to agree on behaviour in this type of situation. The options are:
3. Until DevTech procedures are adapted to Agile approach it shall be highlighted as early as possible that DevTech support will be required. This shall allow the TAD sign off process to be completed and resources to be secured.
| n/a |
Link to project update sent to Board 24/4
Iteration 4 (17/4 to 30/4 ) goal:
The Response coordinator will be able to send the response to the EE by notification. Data about the External Examiner details and course/programme coverage will be fed from EUCLID into the Reporting System. The External Examiner will get a pre-populated form. Usability will be addressed.
User stories | Category | Estimate (Stories Points) | Status |
Sending the Response to External Examiners (carried over from iteration 3) | EE Report Assessment | 2 | Done |
UI Usability Feedback | Usability | 3 | Done |
EERS Import and Data model | System Administration and Support | 3 | Not completed (2/3 done) |
| EE Report Pre-Populated | External Examiner | 3 | Done |
Iteration 4 product review and retrospective (30/4)
| Details | Actions | Owner | Status |
| 8 Stories Points (SP) done out of 11. User story remaining Data Model: 1SP left-Notifications User story: took longer than expected SP: 2, was more like SP: 5 | n/a | ||
| For future notifications' user stories: agree exact content and format (reuse 1st notification sent to EE as a benchmark)- | Review next notifications User Stories14/5 progressed with Brenda for iteration 7 | Brenda | Open |
| Ensure there is an agreement on the conditions of satisfaction, and awareness of the constraints | Spend more time at planning stage | Duncan | closed |
| Organise User Reps meetings | Schedule requirements meeting, then testing meeting with admin user reps for Release 214/5:- met with Rosie to prep admin user stories of iteration 6: on going-To request feedback from EE once latest changes on final report questions have been applied in iteration 6, then from assessors | Duncan | Open |
| Review product backlog | Review Stories Points on the pdt backlog, identify common points for re-estimation14/5: new user story created: workflow and status management (3 SP)2 new user stories (2 SP each) to deal with usability enhancement | Ryan/Greg | Open |
| SAN failure caused testing delays (3 days 23/25 Apr)- | n/a | ||
Iteration 5 (1/5 to 14/5 ) goal:
Data about the External Examiner details and course/programme coverage will be fed from EUCLID into the Reporting System (work started in earlier iteration, to be completed). Each year a new External Examiner report is created.Key contact and payment administrator can be maintained within the system.
User stories | Category | Estimate (Stories Points) | Status |
| EERS Import and Data model (carried over from iteration 4) | System administration and support | 3 | Done |
| Creation of EUGEX Views to supply data to EERS | System administration and support | 2 | Done |
| Create New Report Instance | System administration and support | 5 | Done |
| Key Contact/Payment Administrator Maintenance | System administration and support | 3 | Not completed (build done, test outstanding) |
Iteration 5 product review and retrospective (14/5)
| Details | Actions | Owner | Status |
10 Points completed out of 13-milestone to complete the data integration with EUCLID completed. Issues: - User stories not tested in TEST, but in Dev, due to dependency of another project's late deployment (Upload and Communication of Awards) -description of UG/PG reports in report summary to be done within existing usability user story | n/a | ||
| New user story for testing the data feed and new report instance in TEST. Would only require IS time to deploy, and BA/SSP time to test | Create new user story | Duncan | Done |
| Handover to Brenda the testing with user reps | Split requirements analysis between both BAs | Duncan | Done |
| Definitions of conditions of satisfaction has improved, easier for build team | n/a | ||