Iteration 1.0A
Planning
| Release | Iteration | Start Date | End Date | Planned Stories | Planned Story Points | Planned Hours | Actual Stories | Actual Story Points |
|---|---|---|---|---|---|---|---|---|
| 1 | 1.0A | 08/04/13 | 19/04/13 | 6 | 16 | 66 | 2 (plus 2 x 50%) = 3 | 5 (plus 5 x 50%) = 7 |
User Stories in this iteration
| Title | As a . . . | I need . . . | so that . . . . . | Conditions of Satisfaction & comments | Story Points | Status |
| Maintain users | H&S (& School Co-ordinator) | to add/amend/remove users | I can maintain an up-to-date list of who should have access to the system | User can be assigned role of Admin (H&S), Co-ordinator or Researcher Admin users can add Admins, Co-ordinators and Researchers. Co-ordinators can only add Researchers. A list of existing users can be seen (Admins see all, School Co-ordinators only see their School) School can be amended (as source data not always correct) New users entered by uun, then automatically looked up against EASE & their name, email, School pulled through Removed users are made 'inactive' not deleted (for archive reporting purposes) Audit trail of who last upated the record | 3 | Done |
| Maintain disposal routes | H&S | to add/amend/remove disposal routes | I can maintain an up-to-date list of valid disposal routes | As this list is small & fairly static, could this be de-prioritised to after release 1? Initial values include bin, sink, air etc Does the disposal method still count towards building level Y/N (e.g. bin does, sink doesn't) Removed routes are made 'inactive' not deleted (for archive reporting purposes) | 2 | Done |
| Maintain Schools | H&S | a master list of College/Schools based on Org Heirarchy | School drop-down lists can be populated in other parts of RETAIN | List uploaded from Org Heirarchy (annually?) New units since the last upload are automatically added Deleted units are marked as 'inactive' (not removed, as needed for reporting). Any with users attached are flagged as a warning to the user & not processed. What about users still assigned to old units? | 3 | 50% c/fwd |
| Maintain substances | H&S | to add/amend/remove substances and which categories they belong to | I can maintain an up-to-date list of which substances fall under which regulations | Can enter substance name, reportable element (isotope) name, valid units of measure, valid disposal routes Substance can be allocated to one or more categories | 2 | 50% c/fwd |
| Upload EBIS data | H&S | to upload building/room data from EBIS | I don't have to manually maintain all of the basic room info | Manual upload from csv file exported from EBIS Room name, number, floor (?), building, campus, owning School New rooms since the last upload automatically added Deleted room with substances attached just flagged as warning to the user | 3 | c/fwd |
| Maintain locations | H&S | to add/amend/remove locations (labs?) | I can control where substances are stored | Base data loaded from EBIS but this allows rooms to be further classified as secure bio lab, radioactive storage rooms etc Removed locations are made 'inactive' not deleted (for archive reporting purposes) Room can belong to more than one School Controlled area Y/N Bio security level (1-5?) Free txt field for comments on security measures etc Friendly room name | 3 | c/fwd |
Review & retrospective (learning points)
Attendees - Candice Schmid (Product Owner), Mike McMonagle (Developer), Jonny Mayo (Developer), Dawn Nicholls (Project Manager)
- Review of delivered User Stories (demo)
- Retrospective (how did we do?)
- Start/stop/continue listed in table below
- More time lost to office move than expected
- Conflicts for Mike's time with other projects - flagged to IS management
Start  | Securing meeting room/area for regular catch-ups for developers to improve collaboration. Using Greenhopper and team whiteboard to manage Story cards Using Jira to manage issues/tasks Aiming to get Stories to test earlier by making non-Agile day later in the week Creating User Stories for high-level design in iteration 1 for future Agile projects |
Stop  | Scheduling Mike at 80% as this seems to be unachievable - use 70% for planning next iteration. |
Continue  | Daily stand-ups. |