Summary

In this chapter, we discussed how to look beyond just pure technology consideration and make the adoption of Puppet a success. We reviewed how to choose a focus and scope to allow Puppet to be delivered in iterations of continuous improvement, using a regular delivery cadence and methods such as sprints with a small focus for the team to work together on. We talked about breaking down this focus into deliverables that can be collaboratively worked on and demoed on a regular cycle. We also covered allowing the Puppet team to build confidence and learn as decisions are made together and coding practice is established while showing meaningful returns and progress to management and stakeholders. We discussed how the use cases of Puppet should be outlined and ensure that the temptation to maximize the return from Puppet does not result in unsuited tasks trying to be shoehorned in, which can destabilize the reliability and performance of the Puppet infrastructure and give general...