Difference between revisions of "Fusion Teams"
Line 9: | Line 9: | ||
== Fusion Teams and Power Platform == | == Fusion Teams and Power Platform == | ||
− | Often Pro Developer tasks are described as creating APIs, generating [[Custom Connectors]] for everyone to use in their [[Power Apps]] ([[Canvas | + | Often Pro Developer tasks are described as creating APIs, generating [[Custom Connectors]] for everyone to use in their [[Power Apps]] ([[Canvas App]]) and [[Power Automate]] [[cloud flows]] as well as building custom components using the [[Power Apps Component Framework]]. What is not mentioned is developing plugins, custom workflows and client side scripts (JavaScript/TypeScript). Still those parts are common in projects. Power Automate cloud flows are recommended instead of classic workflows nowadays though and in the future we will have the possibility to use the low-code language [[Power Fx]] when we need to extend our solution with a [[plugin]] as well as in our [[model-driven apps]] (for what parts in the model-driven apps - the future will tell). |
== Microsoft Resources == | == Microsoft Resources == |
Revision as of 14:29, 9 December 2021
A Fusion Team is a team within an organization where Citizen Developers (people who are business experts within different areas that the organization operates in) and Pro Developers work together.
Fusion Teams described in the Gartner Glossary, Definition of Fusion Team.
A fusion team is a multidisciplinary team that blends technology or analytics and business domain expertise and shares accountability for business and technology outcomes
Gartner
Fusion Teams and Power Platform
Often Pro Developer tasks are described as creating APIs, generating Custom Connectors for everyone to use in their Power Apps (Canvas App) and Power Automate cloud flows as well as building custom components using the Power Apps Component Framework. What is not mentioned is developing plugins, custom workflows and client side scripts (JavaScript/TypeScript). Still those parts are common in projects. Power Automate cloud flows are recommended instead of classic workflows nowadays though and in the future we will have the possibility to use the low-code language Power Fx when we need to extend our solution with a plugin as well as in our model-driven apps (for what parts in the model-driven apps - the future will tell).
Microsoft Resources
- Transform your business applications with fusion development MS Learn Learning path.
- Fusion Development approach to building apps using Power Apps Whitepaper about Fusion Teams
Community Resources
- Power Platform Developers – what does the future hold? by Alex Shlega 2021-04-15
- Future of developers in Power Platform by Natraj Yegnaraman 2021-04-08
- Democratizing code by Jukka Niiranen 2021-04-06