How do you move a Citizen Developer project into a professional IT-managed environment?
My team built a "temporary" project management tool that has now become critical for the entire department. It’s starting to lag because we have too many users, and it needs a real database back-end. How do we "hand off" a Citizen Developer app to the professional Pro-Code developers without them having to rewrite the whole thing from scratch? What is the proper transition protocol for scaling an LCNC app?
2024-05-20 in Software Development by Mark Thompson
| 11037 Views
All answers to this question.
This is a "Good Problem" to have—it means your app provides real value! The transition usually happens in the "Back-end." Most LCNC apps start with Excel or SharePoint as a database, but they can't handle high concurrency. A professional developer will likely migrate your data to SQL Server or Dataverse. Because your app is built on a standard platform (like Power Apps), they don't have to rewrite the UI; they just "re-point" the data connectors. To make this easy for them, ensure your logic is labeled clearly. This "Fusion Team" approach—where Citizen Developers build the front-end and Pro-Code devs manage the back-end—is the most efficient way to scale.
Answered 2024-06-15 by Kimberly Adams
When you approach IT for the hand-off, are you bringing a "Technical Debt" report that outlines the current limitations and the specific areas where the app is failing under load?
Answered 2024-06-25 by Christopher Evans
-
Christopher, I’m working on that report right now. I’ve logged the specific instances where the app "timed out" and the tables where we are hitting row limits. I want to show IT that I've taken it as far as I can with my current skills. By giving them a clear list of "bottlenecks," it makes it a lot easier for their senior architects to step in and optimize the performance without having to guess where the issues are. It turns it into a collaborative "upgrade" rather than me just dumping a broken tool on their lap.
Commented 2024-07-05 by Mark Thompson
Think of it as a "Prototype." You've proven the business logic works, which saves the developers weeks of requirements gathering. They will appreciate that you’ve done the heavy lifting.
Answered 2024-07-12 by Linda Garcia
-
Exactly, Linda. A working prototype is the best functional specification a developer could ever ask for. It removes all the ambiguity from the project.
Commented 2024-07-20 by Kimberly Adams
Write a Comment
Your email address will not be published. Required fields are marked (*)

