Learn how to understand your own requirements.
- [Instructor] So let's take a look at understanding our requirements and actually drilling down on what we defined as a project earlier. So this is the most important step, but it's often skipped. And the reason it's skipped is because this is not sexy stuff and we have to dig in to the dirty little details of what these systems are all about and deal with compliance issues, which means understanding legal issues and deal with security and deal with lots of things that are very detailed and very difficult to go through. But if you don't understand what you're doing, in looking at those various aspects of the systems, you're going to end up making mistakes in the requirements, which means that you're not going to come up with a valid in-state solution.
So please don't let this be technology driven. I'm often distracted by technology because my clients are looking at different technological solutions and they want the answer to be within a particular tool, and ultimately that's not where the answer is. Keep in mind that governance, in terms of a strategy, in terms of tactical deployments, is going to be a set of tools. You're going to have SEMP tools, cloud management platform, you're going to have a service governance tool. You're going to have any number of different cost governance tools that are there, budget governance tools that are there, compliance governance tools that are there.
And this is really going to be a complex solution that's built upon complex requirements. Keep that in mind. So understanding your requirements means just that. And so you can break them down into data. You can break them down into service resources. You can break them down into people. You can break them down into security identity access management, and basically coming up with a complete list. In a previous video, we talked about this actually lasting five weeks.
In some instances it may take you longer and I urge you to not necessarily skimp on this. If you're going to make the wrong decisions, you're going to make the wrong decisions understanding your own requirements and how they need to be built out. So the tips... Focus on what you're governing... resources, services, security, compliance. I can't stress that enough. This is what you need to understand in terms of the target solution based on the requirements. Write use cases as if you're doing application requirements.
So this is a net new application and we need to make sure we write the use cases so we understand how the application is going to be used... The actors, people who are interacting with the systems, and that will get you to the governance resources, the governance requirements, which will finally get you to the policies you need to write to protect the systems. And again, never start with the technology. I can't stress that enough. I understand the tools are very cool and we're always looking for answers in the technology, but sometimes the answers aren't there, and if we need to pick the right technology, and that's important to us, then getting the requirements right is an absolute must.
Then finally, get the right skill sets the first time, including governance subject matter experts. And so, if you need to use a consulting company, fine. If you need to hire people, fine. If you need to train people, that's also fine, but you're not going to be able to make the right decisions and make the right calls within your cloud governance project if you don't have the skills and the people understand what's going on.
- 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