How to use our new tool

• 43 members • 28 contributing • 15 in training

Our Team:

cut work by about 30%

Our WorkflowRequirement

Task breakdown

Code

Check

Test

Release

• What needs to happen • How does it need to

happen • What data does it need to

affect / might it break? • How is the interaction seen

• Database changes • What Java needs to be

written • What styling / usability

considerations are there?• Java • JSP • HTML • JavaScript • MySQL• Does it fulfil the criteria?

• Does it break anything else?

• Can the user accomplish their requirement?

“As a volunteer department helper I'd like to be able to insert volunteer details”* The user should fill in a web form with a layout similar to the S-82 Regional Building Committee Volunteer Application * The New application/Update of personal data checkboxes on the paper form are not required **On the blur event of the forename (field 1(a), part 2) we should try to find a matching person **Search for exact match first and last names in the existing persons table **If there are matches display the list of people: Surname, forename and congregation **User should be given the the option to select a match, or ignore them **If user selects a person that is already a volunteer, redirect to the volunteer edit form **If a user selects a person that is not a volunteer, pre-fill the form. Changes to these pre-filled values will cause the person to be updated * The date fields 2(a), 2(b) should use a date picker ** Name of mate (field 6) should be displayed as two input boxes: surname and forename. ** On the blur event of the forename we should try to find a matching person in the existing persons table ** If there are matches display the list of people: Surname, forename and congregation ** User should be given the the option to select a match, or ignore them * Emergency contact (field 6) should be displayed as two input boxes: surname and forename. ** On the blur event of the forename we should try to find a matching person in the existing persons table ** If there are matches display the list of people: Surname, forename and congregation ** User should be given the the option to select a match, or ignore them ** If a user selects a person we should pre-fill the phone and address fields. These should not be editable. ** A note on the form should indicate that to edit the emergency contact details they will need to edit the person (out of scope: the volunteer view form will have a link to the emergency contact person/volunteer page) * The emergency contact relationship should be a dropdown option. the congregation field should be a type-ahead. ** We should force the user to select something from the typeahead

• 13 separate tasks • 39 commits - updates to our code base • 4.5 months

1 star = OK 3 stars = difficult

• 51 completed requirements • 33 current requirements • 14 documented waiting requirements • Many more requirements to document

ROME(also not built in 1 day)

Login

Dashboard

(not built yet)

use these

use these

Looking for a volunteer

Volunteer record

volunteers or persons?

Look up volunteers using fields provided Create new volunteers Alter volunteers details View departments details View department assignments

Current Tools:

Look up volunteers using any field Create new projects Alter project details Add / edit project stages, activities, tasks, etc Some dashboard functionality Probably other stuff

In the Next Release:

(not built yet)

(not finished yet)

• Monthly progress meeting • Last Sat of month • Hounslow Kingdom Hall

• Laptop (not Windows 8) • Some IT skills • iOS development (Objective C) • Android development (Java)

Volunteers needed!

They Will Need: