> For the complete documentation index, see [llms.txt](https://innowayit-1.gitbook.io/framework/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://innowayit-1.gitbook.io/framework/use-cases/cloud-strategy.md).

# Cloud Strategy

> A cloud strategy "is a concise point of view on the role of cloud within the organization." Cloud is an online database or storage application where information is stored. It can help with long-distance communication and editing within the same documents. It is an essential component in an organisation's functioning as it allows for storing important information. 

> A cloud strategy can improve workflow. Since it hosts many components like infrastructure, workload and data in an online space, it allows easy access for all employees. 

| Sponsor                   | Scope           | Stakeholders                                                        |
| ------------------------- | --------------- | ------------------------------------------------------------------- |
| Head of IT/Head of IT Ops | Enterprise-wide | <p>IT managers<br>Information security<br>Business stakeholders</p> |

#### Sponsors' Concerns

1. How can cloud make our organisation more agile?
2. How can we reduce operation expenses?
3. how can we simplify IT?
4. What different models of cloud are relevant to us?
5. Cloud centre of execellence
6. How secure is cloud security?
7. Cloud exit strategy&#x20;

### FORMULATION

<details>

<summary>PLAN</summary>

Discuss with the right people i.e. team leader why a Cloud Strategy is needed for the organisation to flourish. Organise their thoughts, ideas and opinions into a comprehensive document to be used later.

</details>

<details>

<summary>ENGAGE</summary>

Engage with stakeholders and higher-ups and capture their recommendations and concerns. What are their opinions regarding implementing a cloud strategy? Is it beneficial to the organisation? How will it help with the functioning or effectiveness of the busine

</details>

<details>

<summary>DIAGNOSE</summary>

Isolate which concerns and recommendations take precedence and analyse how they will impact the development of the cloud strategy. For example, the cost to produce a cloud strategy, who will be involved, etc.

</details>

<details>

<summary>DECIDE</summary>

Decide which concerns and recommendations are the most important (highest impact on organisation. Create a table or list of pros and cons with other key information (what is a cloud strategy? Research regarding the use of cloud, etc.) Make a decision.

</details>

<details>

<summary>GUIDE</summary>

After a decision is made, a guiding policy is created to aid in the development of a cloud strategy

</details>

<details>

<summary>DEFINE OKR</summary>

</details>

### EXECUTION

<details>

<summary>ACT</summary>

</details>

<details>

<summary>REPORT</summary>

</details>

<details>

<summary>RETROSPECT</summary>

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://innowayit-1.gitbook.io/framework/use-cases/cloud-strategy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.