March 21, 2016 SIG Governing Board Meeting Agenda

SIG Governing Board
Friday, March 21, 2016
International West and Center Ballroom
8:30 am – 4:00 pm

8:30 am – 9:00 am Continental Breakfast
9:00 am – 9:05 am 1.0 Welcome, Introductions (Matthews)
9:05 am – 9:30 am
2.0 Welcome, ACM President (Hanson)
2.1 Turing Celebration Young Academy
9:30 am – 10:00 am
3.0 Report from ACM CEO (Schnabel)
3.1 State of ACM
3.2 Global Strategy Plan
0:00 am – 10:30 am 4.0 Round Table Leaders to provide input on their Global Programs (SGB Chairs)
10:30 am – 10:45 am 5.0 Update on actions from last SGB meeting (Cappo)
10:45 am – 11:00 am Break
11:00 am – 12:00 pm 6.0 Discussion Groups with reporting and open discussion in last 20 minutes Emerging Areas within your SIG – what are they, what are you doing, what would you like to be doing?
12:00 pm – 12:30 pm 7.0 SIG Contributions to CACM Research Highlights (Morrisett)
12:30 pm – 1:30 pm 8.0 Publications (Davidson)
1:30 pm – 2:30 pm Lunch
2:30 pm – 3:00 pm
9.0 SGB EC Report
9.1 Report from EIG Task Force (McCauly)
9.2 Replication Task Force (Harper)
3:00 pm – 4:00 pm 10.0 Discussion Groups with reporting and open discussion in last 20 minutes Collaboration Project – groups will be asked to discuss and present a potential program or conference to collaborate on

The DevOps Phenomenon

ACM Queue’s “Research for Practice” serves up expert-curated guides to the best of computing research, and relates these breakthroughs to the challenges that software engineers face every day. This installment, “The DevOps Phenomenon” by Anna Wiedemann, Nicole Forsgren, Manuel Wiesche, Heiko Gewald and Helmut Krcmar, gives an overview of stories from across the industry about software organizations overcoming early hurdles of adopting DevOps practices, and coming out on the other side with tighter integration between software and operations teams, faster delivery times for new software features, and achieving higher levels of stability.

ACM Case Studies

Written by leading domain experts for software engineers, ACM Case Studies provide an in-depth look at how software teams overcome specific challenges by implementing new technologies, adopting new practices, or a combination of both. Often through first-hand accounts, these pieces explore what the challenges were, the tools and techniques that were used to combat them, and the solution that was achieved.