ACM SGB Meeting Materials Agenda, March 27, 2009
Friday, March 27, 2009
8:30 am – 4:00 pm
|8:30 am – 9:00 am||Continental Breakfast|
|9:00 am – 9:15 am||1.0 Welcome
1.1 Welcome, Introductions (Wolf, Hanson)
1.2 Welcome, ACM President (Hall)
|9:15 am – 10:00 am||
2.0 Report from the ACM CEO (White)
|10:00 am – 10:30 am||
3.0 History Committee Report (Hailpern)
|10:30 am – 10:45 am||
|10:45 am – 11:45 am|
|11:45 am – 12:15 pm||
5.0 SIG Development Task Force Report (Jacko)
|12:15 pm – 1:15 pm||Lunch|
|1:15 pm – 1:35 pm||
6.0 Declining SIG Membership Task Force Report (Hanson)
|1:35 pm – 2:05 pm||7.0 Publications Advisor Report (Davidson)|
|2:05 pm – 2:50 pm|
|2:50 pm – 3:10 pm||
|3:10 pm – 3:25 pm||
8.0 SGB EC Administrative Report (Wolf)
|3:25 pm – 4:00 pm||
9.0 Best Practices Session (All)
9.1 Open or Closed Nominations?
9.2 Level of Financial Reporting to Members
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.
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 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.