ACM SGB Meeting Materials Agenda, October 16, 2014

SIG Governing Board

Thursday, October 16, 2014

8:30 am - 4:00 pm

Chicago, Hilton O'Hare

Meeting Room: International West & Center

Lunch: International East

8:30 am - 9:00 am
Continental Breakfast
9:00 am - 9:05 am
1.0 Welcome, Introductions (Madden, McCauley)
9:05 am - 9:15 am
Welcome from ACM President (Wolf)
9:15 am - 10:00 am
2.0 Report from ACM CEO report (White)
10:00 am - 10:30 am
3.0 Report on CRA CCC report (Mynatt)
10:30 am - 10:45 am
10:45 am - 12:00 pm
4.0 Publications
4.1 Report from Publications Advisor (Ioannidis - 35 min)
4.1.1 New Publication Suggestion (Harper - 10 min)
4.2 Report from Publications Board Chair (Konstan - 30 min)
12:00 pm - 1:00 pm
Lunch (Held in International East)
1:00 pm - 2:00 pm
5.0 Viability Reviews 
5.1 SIGARCH SlidesViabilityReach
5.2 SIGBED SlidesViabilityReach
5.3 SIGMETRICS SlidesViabilityReach
2:00 pm - 2:15 pm
6.0 Report from CSTA Report (Clayborn)
2:15 pm - 2:30 pm
2:30 pm - 3:00 pm
7.0 SGB EC Administrative Reports
7.1 SGB EC Update (Madden)
7.2 Taskforce on Policies towards retirees Report (Banzhaf)
3:00 pm - 4:00 pm
8.0 Best Practices Session: Practitioner Activities

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.

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.