attending via Zoom: lora, jim, joel, tyler, wayne, frank, mary, ken, paul, ralph

Discussion: 

  • 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

Jim wants to start the sprint two today {note: we almost did at the end but Ralph got a call and it did not happen. It did happen at the Wednesday General Meeting, after the Team Update.}

Much of this meeting was spent going over the figuring out the correct code - the nav bar was not displaying the hamburger correctly in the mobile view. 

An issue came up whereas the team decided RELATIVE CODE ONLY in the html code, no ABSOLUTE. 

The code sent 31-may-2018 was resent and tested with all watching. 

It worked in the CODE Editor.

It did NOT work in the HTML Editor. 

More work would have to be done on this outside of the meeting. {it was found the HTML Editor w/ the host (Bluehost) was striping out some of the Bootstrap code - specifically the line "navbar-toggler-icon"}

We could all see the logo size affected the navbar and caused the header text to go under the navbar. {Joel and Lora found that putting to logo into the navbar eliminated that problem}

Jim plugged in a different microphone, very loud noises - far more conversation about the noise that keyboards bring to waste meeting time.  

{prompting Lora to send an email to the web team a week later

18-jun-2018 another one to consider: MUTE ON IF AS LITTLE AS ONE FINGER IS ON KEYBOARD

We make it a rule that all have 'mute' on while one person is talking, opening up to all going back and forth at the end - and anyone typing must be in mute. 

Amazing how much time, conversation and frustration the keyboard takes away from the meeting. 

Phones ringing, dogs barking seem very okay. They don't interfere in the three ways above that the keyboard does.

I cannot see the make & model of the HTML Editor. I used to use a local HTML editor (Adobe GoLive) and uploaded the files to the host. I haven't used GoLive for about a decade now, they discontinued the product. I loved that one though - could easily do grids.}


  • 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

  1. Job Seeker questions answered, about 14 hours ago • updated by Anonymous • view change
  2. Word reduced and Images added, yesterday at 10:25 PM • updated by Anonymous • view change
  3. GM Schedule / Calendar, yesterday at 4:29 PM • updated by Lora L. Bates • view change
  4. Check the Current TSSG Schedule, yesterday at 1:58 PM • updated by Lora L. Bates • view change
  5. Schedule Prototype, yesterday at 1:47 PM • created by Lora L. Bates
  6. 2018-06-2018 Meeting, Jun 11, 2018 • updated by Lora L. Bates • view change
  7. 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: 

  1. having to be linear 
  2. size by day vs. sized to each other


Regarding Schedule Page: 

  1. (Ken) Concern for maintainability 
  2. (Jim) May need a 3rd Party API 
  3. (Ralph) Need a Wireframe in ticket 
  4. (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. 





  • No labels