View My Drafts
In the same boat here. We have a few big or main digital transformations happening within our org and have access to azure devops. I have been playing around with using that to manage these projects and wondering if that would be over kill. Also the other place was going to be github. I think the trick is finding the right level of documentation if using these tools for what I am calling advanced "citizen development". But since we have the tools and our CTO is used to seeing reports out of devops I am leaning that way. But would love to see best practice for this as well as source control and managing "new feature releases".
I think of the Crisis Communication application that Microsoft put out and wonder how they managed it. https://github.com/microsoft/powerapps-tools/tree/master/Apps/CrisisCommunication
I create a "Documentation" screen that can't be navigated to and use that to document processes that are not obvious or happen over multiple screens. I also keep versioning info there, as well as what features I want to add in the future.
Standardization seems to be a must. We are creating a "bible" of conventions in a OneNote document so we can use the same naming conventions, etc. We also have a set up standard code we have started to insert in all the OnStart sections so that common variables have the same names in all apps.I'm also trying to create a help screen for the apps that users can go to in case something isn't obvious.In-line comments are also essential.
Microsoft also just released this for the platform. being able to use DevOps for application lifecycle management. 04 Aug 2020
Announcing general availability of Microsoft Power Platform Build Tools