Open to anyone with a .gov or .mil email address.
To join, email firstname.lastname@example.org with
Subscribe to DevOps in the subject.
Open to the public.
To join, email email@example.com with
Subscribe Public DevOps in the subject.
The DevOps Community of Practice (CoP) provides information technology and development staff and leadership throughout government the opportunity to share lessons learned, successes, benefits, and know how related to DevOps.
Government agencies are investing in cloud capabilities and are seeking to work more iteratively, improving their ability to support the public through their digital services. The DevOps CoP will allow agencies to share their innovations and successes, reducing the “cost of learning and innovating” across government.
DevOps is the practice of operations and development staff participating together in the entire service lifecycle operate rapidly changing resilient systems at scale.
- August Special Event: The Continuous DevOps Dilemma with Andrew Clay Shafer
- June Meeting: Air Force COOL and 18F, Partnership and Flight Operations Software Agile Lessons Learned
- May Meeting: DevOps Lessons Learned from the Air Force’s Early Cloud Journey
- April Meeting: The Hero’s Journey for Re-Skilling Talent (And Other Digital Adventures)
- March Meeting: Why I Love My Agile Team!
- February Meeting: Moving From Agile Towards DevOps With a Small Team
- January Meeting: Panel Discussion on How Agencies Are Spreading Best Practices
We have two listservs available, one for Federal Employees, and one for all individuals:
- To join our federal government employee only Listserv, send an email from your official government email to: firstname.lastname@example.org
- To join our public Listserv, perfect for federal employees, contractors, vendors, and academia to participate in the conversation, send an email to: email@example.com
What We Do
The DevOps CoP will meet on the fourth Tuesday of each month for 30 minutes. In each meeting, a presenter will have the opportunity to share experiences for 15 minutes, followed by a 15 minute Q&A session.
We work towards the following:
- This CoP allows technical staff and leadership from across government to share their experiences and lessons learned implementing DevOps and agile practices, as well as their efforts to migrate data and services to the cloud.
- We aim to help reduce the learning curve associated with individual agencies, bureaus, and offices adopting cloud capabilities and DevOps practices. The DevOps CoP will allow agencies to learn from one another, sharing technical know-how. We also promote the adoption of DevOps, knowing that DevOps techniques and technologies can not only save time and reduce costs, but also be a vehicle for innovation.
- As the U.S. government procures cloud capabilities, there is an opportunity to reduce cost, improve performance, and improve the speed to which data and digital services are provided to the public. An opportunity also exists to improve the speed at which software can be delivered to users.
Who We Are
Community Co-Manager Brian Fox is currently a strategist with 18F. Prior to working as a member of the 18F Strategy team, he led systems development at USGS’s National Geospatial Technical Operations Center (NGTOC) where he oversaw development activity in support of The National Map. Brian has also supported the National Geospatial-Intelligence Agency in a variety of roles, including joint military assignments in the United States and overseas.
Community Co-Manager Peter Burkholder is a consulting engineer with 18F, where he’s also supported cloud.gov. Before 18F, Peter worked with Chef Software’s enterprise customers to guide them on adoption of DevOps practices and infras tructure-as-code, and has held operations roles with health technology companies, National Institutes of Health (NIH), National Center for Atmospheric Research (NCAR), and AARP. He’s also an organizer of the DevOpsDC MeetUp and the annual DevOpsDaysDC conference.
When participating in this CoP, follow Digital.gov Etiquette Guidelines. Respect your peers, use plain language, be patient, practice constructive criticism, and stay organized. By participating in this CoP conversation, you agree to abide by the TTS Code of Conduct.
Have feedback or questions? Send us an email »