The hardest part of integrating Chef Infra into an organization isn't learning the technical aspect - it's helping others to understand "The Why", and to build a solid community of practitioners. Culinary students often learn the concept of "Mise en Place", or "Everything in its Place". From champions, to technical challenges - come learn from my organizations' lessons that enabled us to scale Chef out, and the epics and features that would have helped us grow faster and become more successful earlier in our journey.
As organizations look to bring new tools in to increase the quality of their infrastructure and speed software delivery, it's often engineers that identify what may be able to improve these processes. Generally what follows is a business case presented to leadership in order to secure funding, an initial purchase order, and then a discovery period for those engineers and their product or service owners on how to make the tool work well in their unique ecosystems. For many, it's tempting to start automating and delivering right away - to just get something out there to show value. Often there is low hanging fruit that can be pointed to as a success story - but it's the more complicated patterns that can slow adoption down. In order for real success to happen there must be a strong community and willingness to change the ways in which we work, as well as support from the bottom of the organization all the way to the business leaders that partner with IT. We can increase velocity and adoption of new tools and ideas by following the concept of "Mise en place", or "Everything in its Place" by laying a solid foundation for Chef, or any other new tool or concept in our organizations to remove friction and make new ideas become successful realities.
Come learn how we developed a community of practitioners, built support for Chef, and laid the groundwork for Chef to not only survive, but to excel in our organization. In this talk we'll share how to build a strong business case for Chef to garner support and build new champions. We'll also cover some epics and features that we think are critical to the success of Chef in an organization. Finally, we'll talk about some thoughts around removing friction from the development lifecycle for Chef Infra to make it easier to learn and use.
Infrastructure Engineer, CUNA Mutual Group