2013-06-12 scrum call

Attending

Items covered for this sprint

Scruminess

Need to adjust priority - 374 is more critical than 609 for 0.8.1
Need to more thoroughly define 374: when something like adding an address, editing a name, you have an option of hitting save or hitting cancel - one problem is that the wording on the button is not consistent (may not always say "cancel") also not sure you always go back to a logical place. So, step one, work through all the possible flows (which is what Marie's spreadsheet is going to do)
Where we have forms where there is a save button but the "save" doesn't apply to everything, we may want to do an inventory of what makes sense; maybe a new parent ticket "review user experience flow, and move 374 under it and add additional tickets or subtasks) - will do that after we get a little farther


2013-06-14 dev call

Attending

Items covered for this sprint

Scruminess

Dev business