Join David Linthicum for an in-depth discussion in this video Build a business case, part of Cloud Architecture: Design Decisions.
- [Instructor] So let's understand the Business Case and let's learn how to define the business case in this section of the course. So, you exist for the business so keep in mind that this is not about playing with advanced technology and playing with cloud technology this is about cloud architecture that needs a solid business case as a foundation for what it's looking to build and how you're looking to build it. So, you're primary goal is to meet the requirements of the business case so ultimately our business case is not necessarily going to be a plan but it's going to be the objective of the architecture to achieve the requirements that are set out in the business case.
How much money are we going to return to the business over time, how long is it going to take, how much of an investment needs to be made for a certain payback or return on our investment that's going to occur as part of the business and as part of our movement into cloud. So let's look at this. So, in the business case there are different things you need to understand. There are hard cost savings and soft cost savings, first and foremost. Hard cost savings are the things that are easy to define, the operational savings that cloud computing can bring us. Since we're not buying hardware and software, hard cost savings are going to be easy to find because we're going to pay the fee to the cloud provider not necessarily the fee to the hardware and software vendor.
So there should be a savings that posted based on the hard cost that we're saving based on the use of cloud computing. Soft cost savings are a bit more savings are a bit more difficult to define and they're around the notion of agility, time to market, other benefits that are difficult to quantify or basically put data around. Therefore they're tougher for organizations to suss to out as to what the impacts going to be but the reality is that the majority of costs savings and ROI within cloud computing is going to be around soft cost savings.
So in other words, their ability to be more agile, our ability to compress time to market is going to obviously go directly to the bottom line and then the business needs. So, what are the operational needs of the business, what business process needs, what does the business need to do to become better than what it is today. So, in defining a cost model we need to define inefficiencies in other words, what's costing us in terms of what we can do better, what are the opportunity costs that are lost in terms of the way we're doing the 'as is' things today that we could do 'to be' with cloud computing.
You need to define the core cost metrics, how we're going to measure existing costs. Need to define the 'as is' state. Need to define the 'to be'. And then move on to define the ROI models, based on that information.
This course is targeted at IT professionals who have a basic understanding of the cloud and are ready to move on to creating a cloud architecture. David Linthicum begins with the business case and requirement patterns, and then moves onto mapping requirements to individual architecture concepts. There are multiple aspects to consider: storage, processing, governance, management and monitoring, security, performance, and more. David also includes discussion of advanced topics such as serverless architectures and containers. Watch and learn how to make sense of today's requirements, and plan your cloud-based architecture to scale with what your company needs to succeed tomorrow.
- Advanced architecture
- Building a business case
- Defining storage, processing, database, and other requirements
- Mapping requirements
- Performance and security