dstoolkit-maiva
MAIVA - Microsoft AI Value Accelerator Playbook
Chapter 1 - MAIVA Framework
Chapter 2 - MAIVA Data Strategy
Chapter 3 - MAIVA Security
This repository hosts a playbook dedicated to helping company IT departments effectively scale their AI initiatives. The playbook aims to provide a structured guide on managing AI investment portfolios to maximize returns. It introduces a framework for industrializing AI within organizations.
Highlights:
- Introduction to the playbook’s purpose and structure.
- Overview of the MAIVA framework for industrializing AI.
- Scope definition for scaling AI initiatives within companies.
- The importance of a robust data management and governance capability.
- Creating an intelligence-driven culture, centrally governed data processes with federated aspects.
- Scalable technology solutions supporting self-service automation and data integration.
- Data strategy centered on business use cases, leveraging AI, and building organizational capacity with a focus on continuous learning and adaptation.
- Security framework and integration
- Security during each stage of the MAIVA framework
- Responsible AI
This playbook will be made available to through GitHub as a guide to any company endeavoring to manage the AI investment portfolio to optimize return on those investments. The playbook will be published in multiple chapters of increasing depth and detail. Each chapter will be published to a separate github repo, making its maintenance manageable. This first chapter sets the stage and scope for a framework to industrialize AI. Subsequent chapters will take on the technical depth of architecture (both AI platform and data platform), security, responsible AI, and so on.
Transparency
Turns out the voice of an author matters, even in a dry professional journal. We were reminded of this truth as we created this playbook. This playbook was constructed in part with AI.
The structure and scope were fully defined before engaging AI based on technical and market expertise and based on executing AI initiatives at many enterprises globally for years. The scope of the playbook was originally authored in a series of presentations. Most of the text itself was authored by a team of contributors before AI was engaged.
On a couple of sections in which writer’s block set in for longer than a few minutes and couldn’t be broken with pen to paper, AI was solicited for help as starter. In those cases, the prose provided by AI was acceptable for breaking the blockage and raising key components for consideration, but in all cases had to be re-written to capture the tone and intent of the author.
In some cases, AI was asked for suggestions to tighten or edit existing sections. The recommended edits were again not accepted without further change to tone.
Perhaps more important than the contributions of AI, we acknowledge that we have leveraged several Microsoft resources that are widely known and recognized as authoritative. For example, we have leveraged the construct and some assets of the Microsoft approach to Responsible AI to illustrate the importance of this policy and practice. Even MAIVA itself is a Microsoft approach to AI acceleration.
We have provided a list of resources and links at the end of the playbook that may be helpful.
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Trademarks
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party’s policies.