Exploiting the potential of low code
Posted: Sun Jan 26, 2025 4:12 am
To do this, both parties must first get over their shadows (we just couldn't resist the pun):
1) On the one hand, central IT must accept that IT applications can also be created by specialist departments. However, certain rules must be strictly followed.
2) The specialist departments, on the other hand, must accept that central IT is responsible for (almost) all IT applications. Therefore, IT requires rules and processes that specialist departments must adhere to.
Which rules lead to success? The art here is to carefully weigh up the freedoms and restrictions in order to, on the one hand, make the most of the employees' spirit of progress and, on the other hand, to create a safe environment for such innovations. To do this, a Citizen Developer Framework must be introduced. A Center of Excellence (CoE) for low code should cayman islands consumer email list​ be established episodically in the company, which takes on the following tasks:
1) The definition of best practices, naming conventions and/or security guidelines, among others, is essential for low-code development.
2) It is essential to build up the know-how of how to deal with different applications. What can actually remain in the specialist departments (for example, small applications that do not map critical processes or proof of concepts [PoC])? What must be managed by a CoE (for example, medium-sized applications that do not have critical non-functional requirements)? And what must be handed over to central IT?
Monitoring the application flow from citizen developers to CoE and central IT is the job of a solution architect or the CTO. LCDPs make all applications visible at once! This transparency is the key to success in finally getting shadow IT under control. The range of use cases for low code is enormous, so the introduction of the citizen developer framework must be gradual and targeted.
1) On the one hand, central IT must accept that IT applications can also be created by specialist departments. However, certain rules must be strictly followed.
2) The specialist departments, on the other hand, must accept that central IT is responsible for (almost) all IT applications. Therefore, IT requires rules and processes that specialist departments must adhere to.
Which rules lead to success? The art here is to carefully weigh up the freedoms and restrictions in order to, on the one hand, make the most of the employees' spirit of progress and, on the other hand, to create a safe environment for such innovations. To do this, a Citizen Developer Framework must be introduced. A Center of Excellence (CoE) for low code should cayman islands consumer email list​ be established episodically in the company, which takes on the following tasks:
1) The definition of best practices, naming conventions and/or security guidelines, among others, is essential for low-code development.
2) It is essential to build up the know-how of how to deal with different applications. What can actually remain in the specialist departments (for example, small applications that do not map critical processes or proof of concepts [PoC])? What must be managed by a CoE (for example, medium-sized applications that do not have critical non-functional requirements)? And what must be handed over to central IT?
Monitoring the application flow from citizen developers to CoE and central IT is the job of a solution architect or the CTO. LCDPs make all applications visible at once! This transparency is the key to success in finally getting shadow IT under control. The range of use cases for low code is enormous, so the introduction of the citizen developer framework must be gradual and targeted.