...
- Wayne will have to take a call from a recruiter
- Paul is also leaving early
- Wayne & Jim need Scrum Master coverage for 2 weeks ---- week 1: dd-mmm-2018___ week 2: dd-mmm-2018___
- Lora should stay in Product Owner role so not an option
- Ralph may cover the role those two weeks
- Ken or Joel may cover the role those two weeks - if the focus is on writing code
- Paul thinks he also may be able to cover the role those two weeks
- Jim may be able to get in on the Wednesday, June 27th General Meeting
GOAL FOR THIS MEETING:
Backlog grooming - get all into JIRA
...
- Wayne dropped to do interview
- Joel requested the html code issue wait until after this meeting as it was too time consuming to resolve
Backlog Grooming Started
the following information was shared at the 13-jun-2018 general meeting
Started JIRA issue review - prioritized, estimated, moved into backlog
Confluence Updates
- Job Seeker questions answered, about 14 hours ago • updated by Anonymous • view change
- Word reduced and Images added, yesterday at 10:25 PM • updated by Anonymous • view change
- GM Schedule / Calendar, yesterday at 4:29 PM • updated by Lora L. Bates • view change
- Check the Current TSSG Schedule, yesterday at 1:58 PM • updated by Lora L. Bates • view change
- Schedule Prototype, yesterday at 1:47 PM • created by Lora L. Bates
- 2018-06-2018 Meeting, Jun 11, 2018 • updated by Lora L. Bates • view change
- Developmental Issue, Jun 11, 2018 • updated by Lora L. Bates • view change
...
end of what was shared at the General Meeting
...
Team needs to further discuss the SIZING OF STORIES, not all agree on:
- having to be linear
- size by day vs. sized to each other
Regarding Schedule Page:
- (Ken) Concern for maintainability
- (Jim) May need a 3rd Party API
- (Ralph) Need a Wireframe in ticket
- (Lora) No Wireframe, we already have a prototype.
Regarding Audio-Video MP3's:
(Ralph) A-V Intro to TSSG need a Narrator and a script, may do on Zoom
(Wayne) Each team needs to add their own
conversation back-forth, the conclusion being the wording is CAN not MUST but Andy Leuper would like if each team does it.
(Ralph) Cool new view - instead of looking at Minimum Viable Product, the better term out there is Minimum Loveable Product as it brings the customer back into being the one who is most important.