Our IT organization has several low-code / no-code tools available to use when trying to solution requests received from our business partners including ServiceNow, Microsoft Power Apps, Microsoft Power Automate, Tools such as Microsoft Teams & SharePoint which can be enhanced using Power Automate, DSI etc. We are looking to develop decision criteria / decision matrices to help objectively determine "what to build where" as it relates to the different platforms. Has anyone developed such criteria or have any insights to share on this matter?
Network Administrator in Education, 5,001 - 10,000 employees
It is always important to keep a clear prejudice of the enterprise software feature requirements for at least 2 quarters and make sure that low code tools can satisfy enterprise custom requirements.SLA on Integrations has to be evaluated.Content you might like
Sr. Sourcing Manager in IT Services, 5,001 - 10,000 employees
For selecting an impartial ERP pre-implementation consultant, firms like Accenture, Deloitte, KPMG, and Slalom all have professional services that have expertise in this area.Be clear upfront that they will not be ...read more
🤖 Artificial Intelligence and Machine Learning41%
🚗 Electric and Autonomous Vehicles21%
💬 5G and Ultra-Fast Internet14%
🌐 Virtual Reality (VR) and Augmented Reality (AR)10%
🏠 Smart Home Technology2%
🌱 Sustainable Tech (e.g., Solar Energy, Green Tech)5%
🌐 Internet of Things (IoT) Devices2%
🌐 Blockchain and Cryptocurrency0%
🛰️ Space Exploration and Commercial Space Travel2%
🧬 Biotechnology and Genetic Engineering3%
58 PARTICIPANTS
Read More Comments
Grandstream27%
3CX39%
Sangoma21%
Avaya14%
148 PARTICIPANTS
Impact and Support: Which group supports which platform and how is that group related to the user group and are they the same. Do you have SLAs. Does the platform have the support mechanisms for the SLAs required. What is the end user support expectation from the platform and from the support/developers of the solution. Does the platform allow for the support.
Scalability: Does the system scale properly at all levels including any integrations that are made. You may not have all the controls over how a low-code system scales or if you have much control at all. If a solution turns out to be wildly successful, you may quickly outgrow the underlying system.
Integration: Does the system have the integrations necessary to where the operations can be automated and not require extra manual intervention or complexities.
Security: Any solution must work well with your Identity and Access Management area. Do the supporting groups know how to automate the user lifecycle, account, and permissions provisioning processing.
Data/Sensitivity: Does the platform allow for handling of the classification of the data or the process. Some data is more sensitive, and some processes require extra controls. Also, data handling, backup/recovery, and data protection.
Development: Do you have the expertise to develop these solutions with the platform because most non-trivial use cases require heavy uses of scripting or other more developer-oriented knowledge. Is this knowledge outside the normal body of knowledge that your company has. Does the platform support multi-environment testing, rollout, rollback needed.
Regulatory: Does the platform allow you to remain compliant with your regulations and customer expectations. You could have tenancy or jurisdiction issues which you must understand.
Cost: What does the usage cost on each platform and is there a development or component cost.