Outstanding Chapter Recruitment Submissions
Thank you to our panel of judges!
We hope that this set up will allow for a smooth and efficient judging process. Following each list of submissions is the rubric for judging that specific category. If you have any questions or concerns throughout this process, please do not hesitate to contact Sunita Jaswal, local_activities@hq.acm.org.
Listed below is a brief description of what we expect, followed by each chapters' submission.
Outstanding Chapter Recruitment - 16 Chapter Submissions
Chapters should apply to the Outstanding Chapter Recruitment category if they have done an excellent job of recruiting student ACM members. They should tell us about their recruiting program. The following questions should be addressed:
- How do they let students at their school know about their Chapter?
- How do they get them interested in joining?
- What factors are most critical to the chapters success?
- How many members does their chapter have?
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.
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.
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.
