Date
Attendees
Goals/Items discussed
- We'd like to get a MVP web site up and running for TSSG.
- We will NOT have a meeting on Memorial Day.
- Jim is gone for 2 weeks in June.
- There will be a special Sprint Planning meeting tomorrow from 2 - 3 to attempt to start a sprint for the MVP site and have it end by 5/21 so that Lora can finish up with the team. A backlog of stories need to be entered in JIRA and some of those stories need to be joined into the MVP Epic for our sprint.
- At some point, we may want to invite a UX designer into the group during an Acton Networkers meeting for help on the TSSG web site.
- Paul S. sent us this article related to design: http://alistapart.com/article/priority-guides-a-content-first-alternative-to-wireframes
- Lora reminds us: Priority guides help avoid the focus shifting away from the content and user toward specific layout elements too early, and keep us from falling into the “designer trap” of visual perfectionism.
- Lora pointed out that it's difficult to present a status for the Web group in the Wednesday meeting after our Monday meeting. Not enough time has passed to prepare.
- Joel reviewed his latest set of MVP wireframes. He will check in with Ken H. for possible development help. Suggestions included:
- Have the TSSG Logo at the top of the page.
- Have the navbar under the TSSG Logo, but remain at the top as the page is scrolled.
- Use a data-spy to highlight navbar tabs as the user scrolls between sections (General Meeting, Web, Mobile, QA Study and Data Analytics). No need for a Home tab.
- Try a smaller logo/icon at the far left of the navbar instead of "TSSG". Background of navbar is white to match the logo/icon.
- No need for a footer other than something to mark the bottom of the page. (no logo)
- Each section will be stacked vertically and scrollable on the page. Possibly use a grid pattern for the General Meeting information (info, agenda...). The grid should end up single column on mobile for responsive design.
- Jim may discuss an Agile topic on Wednesday if we have nothing much to report.
- Ralph estimates that the team will need 5 meetings for a full Agile sprint: backlog grooming, sprint planning, daily scrum, sprint review (demos), and sprint retrospective.
- Ralph stepped us through JIRA's way of setting up a sprint by creating an epic and attaching backlog tickets/stories to the epic.
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
Action items
Lora will send a message to the other TSSG group leaders to help them post preferences for specific text content on their sections of the web site. Each group will follow the same format for their requests (for a consistent look and feel). And she will send them a link to confluence.
Joel Sharasheff Joel needs to write backlog tickets for work that is necessary to finish development of the MVP. Small, incremental changes.
Ralph A. Navarro Jr. Ralph will set up a Zoom Sprint Planning Meeting for a few of us to attend (tomorrow 2-?) to start our first MVP sprint.