Seeking your contributions to what’s next for the Power Platform Adoption Framework

PowerPlatformAF.jpg

The Power Platform Adoption Framework is owned by the community, and we need your input to keep its best practices for adopting, managing, and governing the platform at scale current and useful to all.

Lee Baker, Lucy Bourne, Manuela Pichler, Keith Whatling, and I recently put together seven major themes that we plan to address in the framework over the next six(ish) months. We’d like to share them with the community and ask for your contributions. Each of the themes listed below direct links to their milestone page on GitHub, where you can contribute your ideas, thoughts, approaches, etc. by creating new “issues”. You can also join us in open discussion of all our open issues at this link.

As always, we will continue to keep the latest content for everyone to use in the Github wiki found here.

"Adoption" is a continual process

Power Platform Adoption isn't just a matter of initially bringing the platform to your organization. It's an ongoing, long-term process of modernizing workloads and building solutions to meet today's and future needs. Adoption lasts for as long as you've got the platform.

Adoption drivers; why are we doing this (or why not)?

Why should organizations be adopting Power Platform as the go-to app development platform of the future? How should they be thinking of building the platform now in order to scale tomorrow?

Technology choices across the three clouds

Power Platform is one of Microsoft's "three clouds" alongside Azure and O365. How should we be thinking of leveraging the benefits of integration amongst those clouds? Data is a prime consideration here as their are multiple approaches to data storage (e.g. CDS, SharePoint, Azure SQL).

Power Platform in an organization's tech ecosystem

What's the strategy for fitting Power Platform in alongside what already exists in an organization's tech ecosystem? In particular, how does the platform "play nice" with pre-existing data arrangements, when do we migrate vs. integrate, etc?

Power Platform + Dataflex integration with Teams

How do we adopt, manage, and govern Power Platform and Teams as an increasingly integrated solution set? They are becoming increasingly inseparable from one another.

Architecting repeatable and re-usable solutions

How should organizations architect with repeatability and re-usability in mind so that they gain efficiency in their development at the complex end whilst empowering citizen developers with re-usable components at the less complex end?

Microsoft partners in the Power Platform context

What role do Microsoft partners play in an organization's Power Platform journey? We need to explain the value so that customers are encouraged to benefit from what partners provide.

Thanks for continuing to support this effort 🌏🌍🌎

Previous
Previous

Reflecting on Microsoft Ignite 2020: Five big strategic takeaways for Business Applications

Next
Next

Four things to know and five things to do following the big Microsoft Dataflex + Teams announcement