ACM SGB Meeting Materials Agenda, March 8, 2010
Monday, September 20, 2010
8:30 am – 4:00 pm
| 8:30 am – 9:00 am | Continental Breakfast |
| 9:00 am – 9:15 am |
1.0 Welcome, Introductions (Wolf, Hanson)
|
| 9:15 am – 10:00 am |
2.0 Report from the ACM CEO (White)
|
| 10:00 am – 10:15 am |
3.0 Report from SGB Membership Task Force (Hanson) Slides
|
| 10:15 am – 10:45 am |
4.0 Program Reviews
|
| 10:45 am – 11:00 am |
Break
|
| 11:00 am – 11:30 am | |
| 11:30 am – 12:00 pm | 5.0 Publications Update (Davidson) |
| 12:00 pm – 12:20 pm |
6.0 Tech Pack (Terry)
|
| 12:20 pm – 1:20 pm | Lunch |
| 1:20 pm – 1:35 pm |
7.0 History Committee Report (Hailpern)
|
| 1:35 pm – 2:05 pm |
Program Reviews Continued
|
| 2:05 pm – 2:20 pm |
8.0 SGB Administrative Report (Wolf)
8.1 Update on ACM EC and Council Activities
8.2 Lifetime Membership
8.3 SGB Election Update (Konstan)
|
| 2:20 pm – 2:35 pm |
Break
|
| 2:35 pm – 3:05 pm |
Program Reviews Continued
|
| 3:05 pm – 4:00 pm |
9.0 SIG Proposal Report (Fisher)
9.1 Social Computing - Review Completed
9.2 Health Informatics - Under Review
9.3 Game - Under Review
9.4 Bioinformatics - Under Review
|
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.
