Deploy an application with a lot of dependencies using Chef or another configuration tool that requires you to author new scripts. Set up monitoring that alerts

Deploy an application with a lot of dependencies using Chef or another configuration tool that requires you to author new scripts. Set up monitoring that alerts you intelligently when someone hammers it. Deploy the Chaos Monkey and point it at what you authored; see if it stands up. If it doesn't, figure out why. Fix it. Wash, rinse, repeat. The reason that it's called "devops" instead of just "ops" is to create a separation between the type of ops where you don't EVER break anything and you move real slow and no one ever got fired for buying IBM, and the type of ops where everything's virtualized and software-defined, and things can, will, and should break without any penalty to the operation of the system as a whole.