Devopsdays Boise

Boise, Idaho May 03, 2022

https://devopsdays.org/events/2022-boise/welcome/

CFP closed at  March 16, 2022 15:07 UTC
  (Local)

The DevOps movement has as many definitions as it has practitioners. We believe the core value proposition of DevOps is maximizing the efficiency of software development and operations, reducing the time and overhead of getting usable code from a developer’s desk to a customer’s product. Each enterprise has unique challenges in optimizing this delivery pipeline, from requirements management, to coordination of multiple developers, to function and performance testing, to creating environments and automating deployments.

CFP Description

1) A 20-minute talk presented to the entire conference audience, usually in the mornings. 2) An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes talks with slides auto-advancing every 15 seconds (20 slides total).

General Guidelines:

The themes for the conference are “The Practical Application of DevOps, Reliability, and Security”. Please consider this in your proposals.

  • Be concise, but include as much detail as is necessary to convey your idea.
  • Please provide at least three concrete takeaways that the audience will get from your talk
  • Multiple entries are welcome.
  • Submissions must be made by one of the proposed presenters; we do not accept proposals submitted on behalf of others
  • Attempt to not give details to who you are, we prefer to judge based on content.
  • All presentations must conform to the code of conduct.

Proposals must be submitted via our CFP site. If you have questions about our CFP process, please email: proposals-boise-2020@devopsdays.org

Ideas:

This is what we would like to know. Do you have an answer?

  • DevOps movement has been around for a few years now: Has it really helped your organization? Are there numbers for this?
  • Did the culture of DevOps spread to other parts of your company? If not, why?
  • Is DevOps the magic silver bullet which solved all your problems? What are the problems it didn’t solve (although you thought it would)?
  • Was there one tool or methodology in particular that was key to your organization’s DevOps transformation? Tell us about the role it played and how it moved the needle.
  • Were there unexpected problems during your cultural change into DevOps?
  • Did the required skill-set of people change after starting to do things DevOps-Style?
  • Did people leave because you “went DevOps”? Was this good or bad or both?
  • Have there been technical changes after the culture in your team changed?
  • Did the change affect the business/sales/marketing side?
  • And of course: Has DevOps affected you personally? How do you feel about the change it brought to your work?
  • How have you built reliability into your systems
  • Why is focusing on reliability important

If you’d like some more specific topic examples…

How about release management.

  • Integrating security into the DevOps conversation
  • How to handle budgets for DevOps initiatives
  • DevOps/Reliability/Security and Working Remotely
  • Having DevOps make #monitoringsucks less
  • Metrics and why they are important and how to collect them
  • Why is monitoring important

Our main criteria to make it to the top selection are:

  • Broad appeal: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool.
  • New local presenters: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request.
  • Under-represented voices: We want to hear all voices, including those that may speak less frequently at similar events. Whether you’re in a field not typically thought of as a technology field, you’re in a large, traditional organization, or you’re the only person at your organization with your background, we are interested in your unique experience.
  • Original content: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn’t likely to have already seen.
  • No third-party submissions: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you’ve already shown that as a speaker you’re distant from the process.
  • No vendor pitches: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product. If you’d like to demo your product or service, you should sponsor the event and demo it at your table.
  • Open Space Fodder: Will this talk help generate discussion during the Open Spaces?

Even more tips:

  • We like stories over theory. Examples of what your organization has done are fantastic.
  • You don’t need to write out the entire talk in your abstract, but please provide sufficient detail for the selection committee to get a feel for what your talk will include. Show, don’t tell.
  • However, we will consider talks of this nature if they provide something special.

Attendees (2)