 Hi, I'm Scott Nasella. I'm here for three reasons really. One, I think the Windows DevOps use case in enterprises vastly underrepresented. Two, I'm asking my engineers to do some scary stuff. So I need to be able to role model doing scary stuff too, hence being on the stage. And then three, really giving back to the community, I think is a hallmark. About us were Microsoft server, 3000 plus servers, lots of VMware, all on-premises. So, enter Gene Kim. I was an accidental attendee at one of his talks, the three ways bringing DevOps to the enterprise. And I walked away feeling very burdened, like what am I going to do about this? And he could almost have said that, okay, so enter Jeffrey Snover. So I've used Jeffrey Snover as our engineer whisperer at Columbia, sending some tough love to the engineers. So then we can have a conversation with the engineers. Hey, your job is not really preparing you for the future. So how do we have a collaborative conversation about creating that win-win scenario where we can concurrently benefit the business, becoming less fragile and benefit the engineer in terms of helping their career progression, start going too fast. Okay, so you're going to get a lot of reservations and a lot of pushback from the Windows crowd. And you can see some of the examples here. One of my favorites is, hey, they have a SSH, RDP tip jar, that's crazy. So out of that conversation, you should be able to find some early adopters that want to go on this journey with you. After you find the early adopters, then you ask them what they need to be successful. They could be someone that's frustrated, etc. So we use the minimum viable process to good effect. So instead of trying to build that super complicated burger on the right, build the simple thing, build it well, and then you can add the complexity a little bit later. Taking the top five predictors of IT performance, we said, you know what? We're going to focus on version control. I challenge the team to go from zero to 250 artifacts under version control in 2015. So what you're looking at on the right side, in case you don't know, is PowerShell. So we have a way to measure how we're doing in terms of our artifact count. So this is, I ran this a couple of days ago. So we hit like 500 in the first year and we're like 700 now. Okay, so now we're going to talk about Kanban. So we want to have a way to visualize the work, minimize WIP, and actually know what we're working on. So on the right hand side is TFS Kanban. And we created PowerShell script to be able to put it on there easily. So we have metrics to reinforce the flow. So we take the Kanban board and we can actually schedule our reports to further visualize the work. And then we have a PowerShell script to kind of see what we've done. So we've got version control. We've got scripting Kanban. Now we're actually ready to do the DevOps that we've heard so much about. And you're going to probably have some bumps in the road. Stay with it. Okay, so we started small. We started simple. What you're looking at is a PowerShell script that enables us to provision from script servers onto our VMware environment. So we're talking about the data center, et cetera. We made it a little bit harder. We added domain joining, et cetera. And as you're going to see on the next one, we figured out how to bootstrap Chef. So we have a full-end versioned artifact in our production control system. That way it describes everything that is important about that server. What we're working on now is actually brown-filling all of our existing servers. So we're going to actually exploit the data off of our vSphere environment to build those files, check them in, et cetera. So now we're working on building curious people. So we have stacks of books. I replenish them pretty frequently. You can see Lean Enterprise, Phoenix Project, Beyond the Blame, et cetera. We've had a couple of book clubs that have been super awesome and they've been facilitated by the members of the team. This is a recent podcast series. Three engineers did something scary. They got up and they talked about three podcasts that they picked. So in summary, it's all about minimum viable process for us, including the Deming Cycle, finding a win-win, both for your enterprise and for your engineers, and then making it easy for your new adopters to join.