...

• Get updates on progress of NCSA software development projects and relationships with our collaborators
• Allow all to have a sense of current state of NCSA software development activities
• Allow all to be exposed to technologies used on each project, foster uptake and education of new technologies
• Allow all to be exposed to issues being encountered on each project, allow others to avoid common problems
• Allow all to be exposed to NCSA software being developed on each project, encourage leveraging/adoption in other projects
  • minimizing redundancy and reinventing of the wheel
  • foster the ability for produced software to be sustained over time (independent of individual funding sources)
• Allow all to become and take advantage of subject matter experts within the group
• Allow projects, in particular smaller projects, to be amplified in terms of their deliverables (team experience, technology, leveraged development)

Past Meeting Styles

Approach 1 (2008-2012)

1 hour meeting each week, round robin presenter each week to provide updates and demonstrations of development work being done

...

• Long gaps between project updates, lots can take place in between updates

Approach 2 (2012-2014)

1 hour meeting each week, 10 minute update form everyone

...

• Not very in depth often times
• Can be difficult to follow along from projects where overlap isn't immediately apparent to some on the team

Approach 3 (2014-2016)

1/2 hour standup/kickoff each Monday, interact with members/leads of each project on progress/updates, no central structure

...

• Project leads who span multiple projects are a bottleneck for the Monday meetings, team members having to wait to give update

Approach 4 (2016 - present)

1/2 hour - hour standup each Monday, quick goals from everyone for the week

...

• Could still use more, from project leads perhaps, to guide conversation and highlight how things tie together

Approach 5 (Future)

...

Suggestions for Future Meeting Styles

Kenton

Monday meeting (weekly kickoff):

• Drop and replace with just the wiki updates or a plugin like Standup Jack for Slack

Friday meeting ("the" group meeting)

• Team touch base for the week
  
  • Rocks/Sucks but more directed by a moderator (e.g. Kenton or Shannon) who knows what's happening at a high level in the group and call out topics of interest for discussion (don't go through everyone, just topics of interest)
  • Encourage agenda items to be raised prior to meeting/at beginning of meeting
• Presentation from 1 project/team member (does not have to be every week, but should be fairly often)
• Move to Mondays instead?