Sprint 12 Basin Access and notes from Driver and Participant

Notes for Driver and Participant

There are lost of edge cases that would be too expensive to implement given the amount that they would be used.  This was a business value call.  I felt that we could mop up all of these edge cases with a simple notes field that could be used as a workaround.  I could monitor these notes and introduce features that came up regularly.

Participant notes

Car/Driver notes

Basin Access

Initially, I envisioned this to be part of the boat booking or joining a trip, but on further though I realised that this makes more sense if it is part of the car.  It is the driver's responsibility to arrange access to the basin to pick up boats and equipment.  I wanted it to be something that could be added after (and separate from) adding a car.  

Has Key / Needs Key

Also for basin access it is important to know which cars have keys and which cars will need to get keys from the caretaker.  This needs to be arrange in advance, so providing that info here gives the equipment officers the information they need.

Basin access can be added to a car or removed by the driver.

The weekly access report has been updated to show basin access rather than cars.

End of Core Feature Build

The end of sprint 12 marks the end of the core feature build.  I believe this should now be ready to deliver into trial and be used for a real trip.  

For the next phase I will be concentrating on the following:

I want to transfer focus on the following areas:

• Equipment officer boat management features
• Treasury features - deposits / expense
• Private Trips

Sprint 11 - Exceptional cases and self support

Exceptional Cases

After 10 sprints of building the core features and adding feedback to the backlog, it is now getting to the point where it's becoming more difficult to decide what to work on next.  This is because most of the 80:20 items (80% use from 20% effort) have now been completed.  I'm now left with the 20:80 items (20% use from 80% effort).  So, as part of the sprint planning, I've been asking myself the following questions:

• Can we provide a work-around the user story? If yes, leave till later
• Can we provide a simpler solution until we understand how often an ideal solution would be used?  If yes, implement the simpler solution.
• Will the item help self support the application?  If yes, implement as simply a possible now.
• If we cannot provide a work around, implement now.

Pull out of Trip

Pulling out of trip is a new feature that allows a user to pull out and free up group, car and boat for another member.  The key requirement of the feature was to record the drop out so that the organiser can report this to the Treasurer, who may choose to charge the user some of the trip costs.

The user is warned about this prior to confirming, so that they know they could be charged.

Drivers and Group Leaders cannot leave a trip.  Drivers would have to asks their passengers to move onto another car and then remove their car first.  Group Leaders would need to join a group as a participant before leaving the trip.

Changing details of a trip

This allows the organiser to change the trip title, location and additional details. This allows the organiser to add details that weren't known when the trip was created (e.g. accommodation, evening meal table bookings, etc).

Dismiss-able Notices

These are designed to give guidance to new users but be dismiss-able for regular users.  They give reminders to follow club protocol when joining cars and joining groups.

What for sprint 12?

I want sprint 12 to be the final core club trip planning sprint (3 months).  It should have over 90% coverage of what we will need for standard club trips.

After sprint 12, I want to transfer focus on the following areas:

• Equipment officer boat management features
• Treasury features - deposits / expense
• Private Trips