You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: reference/business_outcomes.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ The business should expect more reporting in this phase. Reporting should cover
75
75
76
76
At this point, you may start to migrate your other applications and have a better understanding of what you want to achieve and where you will see value during each level of maturity.
77
77
78
-
## Level 5: Optimize
78
+
## Level 5: Adapt
79
79
80
80
This phase of optimization will see lots of changes with people, process, policy and technology. For the business, you should have achieved your business goals and have the measurable results to show your leadership teams, CEO, CFO or the board.
Copy file name to clipboardExpand all lines: reference/prologue.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,7 @@ Your competency is growing and you are defining processes for scale.
108
108
***Level 4: Improve**
109
109
You are improving security, policy and governance across your environment.
110
110
111
-
***Level 5: Optimize**
111
+
***Level 5: Adapt**
112
112
You are revisiting decisions made earlier and monitoring applications and infrastructure for optimization.
113
113
114
114
In each of the following sections, we will highlight core concepts and discuss what this means in each stage of your maturity across people, process, policy and technology.
Copy file name to clipboardExpand all lines: website/content/en/level-1/index.md
+22-29Lines changed: 22 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,24 @@ description: >
4
4
You have a baseline cloud native implementation in place and are in pre-production.
5
5
---
6
6
7
-
## <iclass="fas fa-users"></i> People
7
+
## <iclass="fas fa-building"></i> Business Outcomes
8
+
9
+
### Business Outcomes
10
+
11
+
*“For many business leaders, the migration and continuing adoption of cloud native technology are not as clear-cut as migrating workloads as-is from on-premises to hybrid/public clouds. They are unlikely to sign off on major technological shifts, which inevitably create process and cultural change, without understanding the tangible benefits to them.”*[CTO Summit](https://www.cncf.io/reports/cto-summit-na-2022/)
12
+
13
+
Prior to arriving at level one of the model, your business should have agreed the goals for the move. These business goals need to inform adoption of cloud native technologies. Goals will center around managing risk, meeting compliance, customer satisfaction and trust and cost effectiveness. While the technologist might translate this into avoiding vendor lock-in, capacity and availability planning, disaster recovery, response times, etc, ensure that whenever discussing decisions to root the conversation in the business goal.
14
+
15
+
In level one, the organization must prioritize its top business goals/issues. This is an important step as prioritization/ranking of business goals will help technologies factor in tradeoffs. Compliance and disaster recovery will no doubt be important, but for some organizations, that might not be the main driver. Business scenario planning is essential. For example, in the case where a company has decided to use public cloud, if customer satisfaction is the priority goal and needs faster website response times, then the technology team will select cloud regions close to the customer. If cost reduction is a primary goal however, then a more cost-effective cloud region might be selected. Another example might be that it is cheaper to host data in the US, but due to EU data privacy laws, that isn’t an option. This is a very high level example, but should showcase how the prioritization of all business goals must inform decision making.
16
+
17
+
At this level, the organization is experimenting with cloud native. This should also translate into business expectations. Technologies should be given the freedom to try different experiments to achieve goals. Experiments should be documented, OKRs (Objectives and Key Results) or KPIs (Key Performance Indicators) created and provided to the business during this phase. The business should expect to see the outcomes of these experiments before continuing to embark on its cloud native journey. This helps to build confidence between the technology and business teams and is absolutely a vital step particularly as cloud native changes the way an organization operates.
18
+
19
+
### Cost
20
+
21
+
In level one, the finance, technology and business teams need to be aligned. Technology needs to understand resourcing and the finance team needs to understand change fees. The organization must make allowances for running both the legacy systems and new cloud environments. In level one, costs will not go down, however as it is just the build/experimentation phase, the costs should not be exorbitant.
22
+
23
+
24
+
## <iclass="fas fa-users"></i> People
8
25
9
26
### People Overview
10
27
@@ -24,21 +41,21 @@ The people implementing cloud native will need to focus on security. Default sec
24
41
25
42
### Developer Agility
26
43
27
-
Your organization is committed to decentralization and will employ “teams of teams”. This is an essential requirement of your people. Across the different levels of maturity, people will be implementing tools for automated testing, metrics and feedback.
44
+
Your organization is committed to decentralization and will employ “teams of teams”. This is an essential requirement of your people. Across the different levels of maturity, people will be implementing tools for automated testing, metrics and feedback.
28
45
29
46
Developers may have learned about Agile Manifesto and adopted Scrum Framework without necessarily including Operations. Developers may attempt to resolve external dependencies themselves, slowing down feedback, with incomplete features per sprint.
30
47
31
48
### Upskilling Developers
32
49
33
-
The maturity of your people will include upskilling the development team.
50
+
The maturity of your people will include upskilling the development team.
34
51
35
52
Your application team will be trained in 12 factor applications, microservice and cloud native patterns. You will also require developers who are quite comfortable with cloud native concepts and tooling such as kubectl in order to bootstrap your development team.
36
53
37
54
### CNCF Certifications
38
55
39
56
Cloud Native Computing Foundation (CNCF) serves as the vendor-neutral home for many of the fastest-growing open source projects, including Kubernetes, Prometheus, and Envoy.
40
57
41
-
In order for you to build a sustainable ecosystems for cloud native infrastructure is it important to have your team invest in the CNCF Certifications. It is unlikely you’ll achieve certifications in level 1.
58
+
In order for you to build a sustainable ecosystem for cloud native infrastructure is it important to have your team invest in the CNCF Certifications. It is unlikely you’ll achieve certifications in level 1.
42
59
43
60
## <iclass="fas fa-cogs"></i> Process
44
61
@@ -62,7 +79,7 @@ You have no change control process in place. Instead changes are performed based
62
79
Incorporating security tooling and practices into your cloud native environment, whether through a practice or a process, as early as possible is crucial to keeping your cloud native environment secure. We often use the term ‘shift left’ to refer to bringing a practice, whether relating to testing or security, into a process as early as possible. Security is covered in all sections of the Cloud Native Maturity Model and each section with People, Process, Policy and Technology can be combined to support the security team as they seek to mature the organization’s cloud native security.
63
80
64
81
Take action: your security journey starts here. Consider security in all aspects of implementation and make it a first class citizen.
65
-
82
+
66
83
### Audit and Logs
67
84
68
85
Your process will include logging and auditing. This can be based on internal requirements or support your compliance mandates.
@@ -122,27 +139,3 @@ Start building your secured CI-CD pipeline if you don’t have one already and d
122
139
123
140
When just starting out, much of your testing will be conducted manually on your business application that you’ve identified as your initial production candidate. With Kubernetes you’ll be focussing on your general network connectivity, and ensuring you’re able to deploy your applications. You will have smoke tests, and UAT testing.
124
141
125
-
## <iclass="fas fa-building"></i> Business Outcomes
126
-
127
-
Level 1 of the Cloud Native Maturity Model is where your team has a baseline implementation in place and you are in pre-production. Here you will have completed a successful POC. Based on the POC, you should have initial findings on how cloud native will help improve your app. In a dev environment, you could, for example, have seen that:
128
-
- An app is using less resources (cost savings / more efficient use)
129
-
- A new feature shipped faster (faster time to market and thus increased revenue)
130
-
- There was no downtime (improved reliability for customers)
131
-
- Improved business continuity thanks to resilient cloud architectures
132
-
133
-
These are just examples, they are not a guarantee based on your environment as results may vary.
134
-
135
-
In this phase, you will determine how you’ll measure (your initial KPIs) the success of your cloud native journey; and just as important, how you will demonstrate it to stakeholders. This is a major outcome of Level 1 as the entire success of the journey should be mapped to this measurement. Remember it won't be immediate on day 1. Some quantitative and qualitative example KPIs may include:
136
-
- Reduced spend on app infrastructure by 25% by optimizing for cost
137
-
- Dev cost lowered by 10%
138
-
- Reduced team focus on app infrastructure by 15% by automating as much as possible
139
-
- Increased security for the application by automating CVE identification in containers
140
-
- Improve compliance as you can restrict and track access to the application; demonstrate compliance with SOC 2
141
-
- Accelerated development life cycles as you implement CI/CD pipelines shipping 10% more features per quarter
142
-
- Migrate plan - this will vary depending on your organization, but you should have a migration plan in place. Whether that’s to migrate one application first, or several, you should have this established.
143
-
- Improved customer experience measured by increased performance scores
144
-
- Elimination of information silos: departments no longer isolated; unique, integrated ecosystem in place.
145
-
- Alignment of business and IT goals: everyone is involved and aware, so that resources are better addressed to meet those goals efficiently.
146
-
- Increased internal communication: cross-pollination offers new perspectives with shared knowledge.
147
-
148
-
In this phase, it’s important that the business outcomes are examined and explained to business stakeholders. It should be a discussion with engineering leadership, the application owner (finance, marketing, etc), the CEO, and even the board. Without these discussions and alignment, maturing to the next phases will come with little appreciation and possibly even skepticism.
Copy file name to clipboardExpand all lines: website/content/en/level-2/index.md
+23-11Lines changed: 23 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,29 @@ title: Level 2 - Operate
3
3
description: The cloud native foundation is established and you are moving to production.
4
4
---
5
5
6
-
## <iclass="fas fa-users"></i> People
6
+
## <iclass="fas fa-building"></i> Business Outcomes
7
+
8
+
At level two, you’ve experimented and made the decision to continue on the cloud native journey. Here you want to identify the projects that will uniquely benefit from cloud native. The business and technology needs to align on the project/service/application that makes the most sense to move. The decision could be focused on “where are we hurting the most” either internally or externally. While it may be easy to look at external “product or service” spend time considering internal requirements first.
9
+
10
+
Part of the decision making process should be based on seeing a return on investment (ROI). You should be moving an application that can serve as your speed boat.
11
+
12
+
> *Speed boat: transform to the cloud steadily and incrementally using speed boats to accelerate adoption and achieve extreme agility.*
13
+
14
+
Moving business essential applications (i.e. production workloads) will come with trade offs so selection is key. If you choose application A for example, you may need to worry about cloud costs. If you choose application B, you’ll need to worry about compliance audits. Ensure that the decision of what applications to move first considers key non-functional requirements such as capacity, backup, DR, performance (availability) as well as any governance topics such as compliance (and audits, including relevant logging), and risks such as that to reputation through downtime or security compromise.
15
+
16
+
Whatever application is selected will force the technology team to set standards and innovate for new ways of working. The technology team will design and establish new patterns based on the business goals. The project(s) that are moved first will help establish new policy, technology, process and people changes. Be aware that the first application may require prerequisites to be implemented to fulfill specific obligations. For example, you may need to extend your current concept for identity and access management to cater for public cloud use cases. Be prepared for a cascade of activities to deliver the minimally acceptable prerequisites to get your first applications into production.
17
+
18
+
*“Organizations must develop meaningful processes for sharing information and results between technology and business units, which might mean seeking out new talent with technical expertise and passion for sharing information.”*[CTO Summit](https://www.cncf.io/reports/cto-summit-na-2022/)
19
+
20
+
Measurement is key as we move through business outcomes. Each KPI and OKR must map to the overall business goal. It must be documented in a language that the business can understand.
21
+
22
+
Before moving to level three - scale - you must demonstrate business value. Lots of organizations get stuck at level two because they cannot demonstrate how the technology has helped achieve the goal. Going through this goal mapping exercise as early as possible is vital to your cloud native journey.
23
+
24
+
### Cost
25
+
26
+
When selecting what you are moving first, you must consider how you will deal with changes in cost. You will no longer be buying server and network hardware and software directly, but instead effectively leasing or paying as you go for capacity. While this brings with it flexibility, it will also require some work with cloud providers to get discounts. Ensure your technology team is in lock-step with finance to plan accordingly. The business should continuously ask for ways of optimizing infrastructure to save money and/or for evidence as to why more or less capacity is needed. Cost control really does become everyone’s responsibility as real money exits the organization on a regular basis.
27
+
28
+
## <iclass="fas fa-users"></i> People
7
29
8
30
### People Overview
9
31
@@ -110,13 +132,3 @@ Ensure that your development and operations groups are following good practice w
110
132
### Testing and Issue Detection
111
133
112
134
Now that you are in production, you’ll be experimenting with tooling to help with security, policy management, workload misconfigurations, resource requests, limits and observability, in your staging or development environment.
113
-
114
-
## <iclass="fas fa-building"></i> Business Outcomes
115
-
116
-
Cloud native is now established and your technologists are moving to production. While the technical outcome of Level 2 is a fully functional application or group of applications migrated to cloud native tools and practices, the business outcomes are the ability to evaluate the benefits of the migrations. This is also the level that most customers/corporations get to and plateau. This is when a cloud native maturity model shows its true value.
117
-
118
-
With your established KPIs from Level 1, you will measure success and communicate this to stakeholders.
119
-
120
-
In the operation phase, you will be focused on moving to production. You’ll have established standards around technology, your people will be operating it and implementing policy and process. Your business outcome will be around production migration. The business leadership of your organization will want to understand what applications are being moved and why. Be able to clearly communicate the plans to your business leaders. Repeatable patterns will also emerge as teams operate in Level 2. These will be applied to your business outcomes so that benefits you see in one migrated application can be applied to another without as much as a heavy lift. These patterns will help streamline operations across your dev, sec and ops teams.
121
-
122
-
Your KPIs can also include your return on investment ROI, but know that in Level 2, your ROI will be lower than when you reach Level 5. This is because you are investing a lot in acquiring tools, establishing the right team and skill set, whereas in Level 5 you are optimizing.
0 commit comments