March 3, 2015 - RostarSynergistics/ShinyExpenseTracker GitHub Wiki
Demonstrated Huboard
SCRUM:
Alex
Done:
- gave review
- marked UML
Going to do:
- another review
- respond to emails if any
Adam
Done:
- set up Huboard
- wrote expense claim stuff
Going to do:
- test written code
- help others
No blockers
Sarah
Done:
- expense item stuff
Going to do:
- finish expense item stuff and write tests
No blockers
Oleg
Done:
- assigned myself task
Going to do:
- implement through tdd
- ask for help
No blockers
Rajan
Done:
- opened coding convention issue
- assigned claim list controller to self
Going to do:
- work on task
Blocker:
- lack of clarity
Tristan
Done:
- converted UML to skeleton code
Going to do:
- view expense claims+tests
No Blockers
Ramish
Done:
- started on expense claim
Going to do:
- what assigned
No Blockers
Discussion of feedback
- tdd is important
- commented out tests should be deleted or uncommented and stubs made
- write javadoc. it is very helpful. use soft documenting method (meaningful function names) when possible format: what class is, why it is needed, how to use it
- rest almost fixed
Buttons: function before look
UML has to be updated on the go
- e.g. when adding a new method
Discussion of part 3 feedback
- dia file is online now
- more optimistic section names (or are they sarcastic?)
- put roles