SIG Governing Board Meeting Agenda

April 2, 2019

Download the Agenda Here

April 1, 2019
7:00pm-9:00pm
  SIG Governing Board Dinner
Room: Athens/Berlin Room
April 2, 2019
8:30am-4:00pm
  SGB Meeting
Room: International Ballroom
8:30am-9:00am   Continental Breakfast
9:00am-9:15am 1.0 Welcome, Introductions (Jortner and Pancake)
9:15am-10:00am 2.0 ACM Publications Board (Davidson) Report Feedback
10:00am-10:30pm  3.0 Disability Inclusion Discussion – (Trewin) Report and Feedback
10:30am-10:45 am   Break
10:45am-12:00pm 4.0 Conference Practices
12:00pm-1:00pm   Lunch
1:00pm-1:45pm 5.0 SIG Practices
1:45pm-2:45pm 6.0 What Should We Be Doing Differently?
2:45pm-3:00pm   Break
3:00pm-3:30pm 7.0 Best Practices-Interaction Between SIG and Conference Committees
3:30pm-4:00pm 8.0 Wrap-up

 

Why I Belong to ACM

Hear from Bryan Cantrill, vice president of engineering at Joyent, Ben Fried chief information officer at Google, and Theo Schlossnagle, OmniTI founder on why they are members of ACM.

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” consistently 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 of RfP is by Anna Wiedemann, Nicole Forsgren, Manuel Wiesche, Heiko Gewald, and Helmut Krcmar. Titled “The DevOps Phenomenon,” this RfP gives an overview of stories from across the industry about software organizations overcoming the early hurdles of adopting DevOps practices, and coming out on the other side with tighter integration between their software and operations teams, faster delivery times for new software features, and achieving a higher level of stability.