Learn how to find and use the right governance tools.
- [Instructor] Okay let's talk about finding the right tool. So, as I mentioned earlier, people have a tendency to go directly to this step really kind of as a success factor in terms of making their cloud governance project work, but we have to work from the requirements to picking the best toolset for our governance solution. Again, watch letting technology distract you. I think people with the shiny objects have a tendency to start being drawn toward different technology and different technology patterns, and I recommend that you kind of leave technology out of the mix until you've gone through your requirements process, as we mentioned earlier in the presentation.
So, finding the right tools, basically is after you understand the requirements, not before, and that gets into testing because we have the tools to test, and that gets into cloud governance operations because we're operating with the tools that we picked. So, this is an absolute imperative that we understand what the requirements are and actually pick the technology that's going to work for us, and by the way, it may not be the most common technology, and it may not be the most popular technology, but ultimately it's going to be the cloud governance systems, whether that's resource or services, or a mix of the two, or cost governance and things like that, that really need to be understood in terms of how we're going to deploy this and make this work over a long period of time.
And by the way, you may make a mistake and there's no reason why you can't back up to understand your requirements better, or reselect the toolset, and then keep on going. You should forgive yourself with a few of those because ultimately this is new technology, and we're getting into some new spaces that people do not have a lot of experience in, and we're going to make mistakes. So the tips I have for you is narrow focus to three or four tools quickly. So this is not about boiling the ocean, and looking at 20 different tools and doing 20 different proof of concepts, and all those sorts of things.
You need to look at the features and functions, and look at your requirements and get quickly down to the top three, the top four, most case five, in terms of looking at the toolsets you're going to leverage. Ensure that the tool provider is a solid player. We have a lot of startups out there with some very valuable tools, and there's no reason you should not leverage those, but if the vendor is not a good actor, they're not doing well as a business, and they're likely to be acquired, and they're likely to go through some changes, that could end up tossing your tool out of the mix.
Then, that's something you need to avoid, and you need to make sure that they're going to have a solid platform for a business to support you going forward. Check on the available training, such as the tool SMEs. If I'm going to have someone who's going to be a drop dead expert in RightScale or ServiceMesh, or one of the other cloud management platform tools, they're going to need to go to training. So does your tool provider provide them with training? Does it provide them with the capabilities they need to be successful with the toolset? Make sure that you have a microplan for deployment, so in other words there's a plan, which is the larger project we just showed you, but you also need to have a subplan or basically a back of the napkin deployment plan for how these things are going to be deployed.
What resources do you need? How do the resources need to be setup? For instance in the demo you just saw, I had to configure my Microsoft resources before I was able to actually show you the tool, because it has to have something to manage. So, how many of those resources do you need in place? How are you going to leverage them? And this creates a bit of complexity because you're dealing with the complexity of the tool that we don't know a lot about yet, and also dealing with the complexity of the cloud, which we may know less about. Don't be afraid to stop, back up and retry. I forgive you for failure and hopefully your bosses will as well, because we're, again, blazing a trail here, and when we do that, we're going to end up making mistakes, and those mistakes are going to cost money, so budget money for mistakes that exist in the project, so you're able to not necessarily keep going forward with a dumb idea and a dumb tool that's not going to fit the bill.
It's easier for you to stop, hit the reset button, and try again.
- Cloud governance basics
- Cloud resource governance
- How cloud security and governance are linked
- Defining governance policies
- Cloud management platform basics
- Reviewing service governance tools
- Cloud governance costs
- Understanding your requirements
- Finding the right tools
- Testing cloud governance
- How operations deals with governance