Brainstormer Inputs

Development Logistics: 

• Do we want to create the HTML in GitHub?  Yes, public can read, contributor access only 
  • Use GitClone for backup of repository
• We use Atlassian JIRA for Backlog and User Stories:  http://jira.web.technologynursery.org/projects/TWS/ 
• How-To for Atlassian JIRA and Confuence Integration:  https://www.atlassian.com/software/confluence/jira-integration
• We use Atlassian Confluence for Knowledge Management:  http://confluence.technologynursery.org/display/TWD/Brainstormer+Inputs

Identify TSSG Organizational Objectives: 

• RESPONSIVE website is a top priority
  • Website needs to work well on mobile, tablet/laptop and desktop screen devices
    • per IAB.com, 90% of people check mobile screen device first 
• Everyone is fond of the claim that We help you answer the question “What have you been doing lately?” – should find a way to include it – is in the Acton Networkers presentation & was in the original mission statement (where’s that?)
  15-dec-2018: [lora] We decided against this in autumn, reason is to keep it professional and avoid sales gush.  The site is not selling, it is informative. Not just prospects read this, future employers will also.  There will be a link to testimonials added at the end of the project; only new testimonials to be captured by Jim Drewniak on Confluence. 
  
  • NOTE: we should comb our documentation for mission/vision statements already published
    
    • Added the Linkedin Group "about us" section to the Project Parameters page 
    • Added the TSSG-OnBoarding.pdf "Purpose, Mission and Guidelines" section  to the Project Parameters page 
      
      
• Use word clusters or word-cloud? esp. for the technologies
• Keep the membership local, no remotes (comment: enforced by requirement to attend one Wed. mtg)  (possible exception for known cases?)
• Job-hunting role is the original focus, but (a) include professional-interest of any sort (b) avoid the term “transition”
  • embrace the term "learn"?
  • NOTE: “transition” is used in the LinkedIn "about us" section, Lora emailed TSSG MGT to find out who can edit that info 3/20
• Volunteer nature of organization
• don’t publish individuals’ contact info (names ok) – note this may not really hide much from the interested snooper w/ access to LinkedIn etc.

Implementation details, perhaps to address at once in v.0 while we work on real thing:

• Lora & Andy principle: attraction, not sales pitch / marketing
• Technologically attractive/up-to-date 
• Determine web layout style - via pages or on the same page vertically?
• “cleanliness” is part of attractiveness – we looked at models that distinguished sections of a page by unobtrusive changes in background color & nothing else
  
  • Example of attractive and vertical = Confluence website https://www.atlassian.com/software/confluence or others... list___ 
  • Example of attractive and horizontal (meaning multiple pages) = 
  • Less is more, lead with just enough to pique interest - too much is a turn-off at the start, people move on from new things quickly
• TSSG.TECH is a non-secure HTTP site, and we do NOT need it to move into being a secure site.
  • this issue came up because someone could not connect to the web site - the note in the address bar was a red lock and "this is not a secure site" - he had an app loaded that blocked any sites that were not secure
• add mouse-hover aids, at the least alt strings (use them to differentiate the links that look similar?)

• we DO NOT want to mention LinkedIn until the admin of that is resolved

Issues about current TSSG.TECH site: 

• New: down the line we need the customer to decide whether to scatter logos (&c) across the "Technologies" pages

     (and BTW some other decisions about those pp)

• Fix the scattering of panels on page 2
• resolve the confusing 2 rows of similar-looking graphics with different links – in parallel, decide which link to a page vs. a [labeled] section on a page
  •  I'd rather start this project design from scratch - no need to resolve or fix anything... (Lora 3/19)

 List of Potential Customers “(as defined in current website)”:

• CUSTOMERS, anyone interested in any aspect of the software development life cycle
• CUSTOMERS, software developers
• CUSTOMERS, web designers
• CUSTOMERS, project managers
• CUSTOMERS, support persons
• CUSTOMERS, quality people
• CUSTOMERS, agile people
• CUSTOMERS, scrum masters
• CUSTOMERS, product owners
• CUSTOMERS, those interested in learning about these and other roles

Purposes for Viewing Site / Joining TSSG:

• PURPOSE TO VIEW TSSG.TECH SITE, between jobs - see if TSSG is doing something I want to do
• PURPOSE TO VIEW TSSG.TECH SITE, software engineer - learn new programming skills
  • Website can show what the TSSG groups are working on
• PURPOSE TO VIEW TSSG.TECH SITE, between jobs - break up my job search with hands-on development
  • This is a purpose of the TSSG group itself, not the TSSG.TECH website
• PURPOSE TO JOIN TSSG, between jobs - demonstrate that you are still active in roles
  • This is a purpose of the TSSG group itself, not the TSSG.TECH website
• PURPOSE TO JOIN TSSG, between jobs - speaking energetically about what you're working on NOW is more natural than something you worked on six months ago
  • This is a purpose of the TSSG group itself, not the TSSG.TECH website
• PURPOSE TO VIEW TSSG.TECH SITE, UX designer between contracts - showcase my skills to a prospective employer
  • This is a purpose of the TSSG group itself, not the TSSG.TECH website

• Stress Variety – including roles (try on hats you haven’t done in the workplace)
• Stress Outlet?

Reporting: 

• Create A Report in JIRA with a date feature so we can view what tickets are closed, in-process and pending - bring The Report back as a link in CONFLUENCE. 
  • The Confluence 'JIRA Report Page' would be at the same level as Meeting Notes.

Advertising: 

• Create an easel sign (40" high x 30" wide, laminated foam core board) for Acton and Hopkinton Networking for visibility at both groups; this is the size they use - they have offered to put it up for us weekly
  • Keep it simple: logo, name, bullet points, website, QR code 

NOTE: at least once a month, we should read the on-boarding documentation & compare w/ the site

review Andy (VOICE OF THE CUSTOMER) inputs (including what NOT to do) & maybe add