Our theme this year is the DevOps feedback loop. As DevOps practioners, we need insights into our processes and how effectively our teams are operating (an indicator of how well our DevOps adoption strategy is working). We need insights into our system health (modern systems are dynamic: cloud, microservices, container-based architectures change state all the time, resulting in more complex failure scenarios). We need insights into the risks we are exposed to and finally, we need insights into user behaviour and experiences to drive our feature development.
in DevOps mode, feedback needs to be faster, it needs to be more accurate, and especially in a large organization it needs to connect not just with dev and ops, but with other stakeholders too – business owners, test and QA teams, security teams, and of course end users.
We’d love to hear how you and your organisation tackle these challenges, about failures and successes related to your systems or teams, new tools and methods you have tried or came up with that have produced great or not so great outcomes.
You are also welcome to submit proposals that you feel fall outside this theme.
DevOpsDays Singapore 2018 is committed to creating a diverse environment and is proud to invite people of all backgrounds and profiles to submit presentation proposals. All potential speakers will receive consideration without regard to race, colour, religion, gender, gender identity or expression, sexual orientation, national origin, genetics, ability or age.
We also encourage those who have not presented before and can offer support to anyone who would like to submit a proposal. Please email us firstname.lastname@example.org with any questions. Even better, just submit your proposal and let us know it’s your first presentation. We can offer support that includes review of your CFP content, speaking and presentation coaching/tips, travel, and accommodation assistance.
There are three ways to propose a topic at DevOpsDays Singapore:
- A 30-minute talk presented during the conference, usually in the mornings.
- An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).
- Open Space: If you’d like to lead a group discussion during the attendee-suggested Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you’d like to demo your product or service, you should sponsor the event and demo it at your table.
Proposal Review Considerations
Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:
- 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 prefer talks not already presented at another event, especially another one in the local area or one available in recorded form.
- No third-party submissions: 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. This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees.
- 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.
Please consider the following for your description
- Be specific. We aren’t mind readers (a description of about 20 lines is about right)
- Detail is good, but not as important as explaining why your proposal would be interesting
- Multiple proposals are welcome. Just respect the other rules