Tag: citdev

In a pervious article we talked about evolving Citizen Developers from City Dwellers to Townsmen … so they can become first class citizen. We discussed the left-shift of responsibilities from pro-developers to Citizen Developers and explained that Low-Code / No-Code (L-C/N-C) platforms cannot exonerate an organization of all the responsibilities shifted to these Citizen Developers:

It is the tooling support of the L-C/N-C platforms
that evolve Citizen Developers from City Dwellers to Townsmen.

It is the organization’s (city) strategy and tactical focus
that turns them into first class citizens.

Next we introduced 3 prerequisites for success the so-called D^3 or Data, Devices and Delivery.

After some more research it became clear that still some dimensions were missing to cover all the angels of people – processes – technology.

Firstly, we want to extend Data with Digitalization. Data is a necessary but not a sufficient condition. Data as a collection of information is nothing without a clear view where it fits within business processes. It is here where Digitalization comes in to add the process angle as sufficient condition.

Secondly, in order to have an acceptable ROI for a L-C/N-C platform investment, a high level of reusability is important. Reusability focusses on technical building blocks like components and connections but also on governance and policies. The idea that there are things that will be application-specific and handled by a Citizen Developer and other things will be generic and handled on an organizational level, introduces a dimension where we look at the distribution of reusable elements throughout the L-C/N-C platform.

The two additions mean that we have now D^5 model:
Data – Devices – Delivery – Digitalization – Distribution

Data: data encapsulation/exposure is a prerequisite

For a Citizen Developer to develop applications for his business,
he needs access to his business data

Data source isolation: data specific for his business
Data availability: data accessible through API’s
Data storage: data to be stored in relation to his application

Devices: suitable devices are a prerequisite

For a Citizen Developer to build applications,
he needs to be able to select a suitable device for the problem at hand
i.e. desktop, mobile, VR-AR, kiosk

Device availability: devices made available on short-term to all the users of his application
Device/License sharing: devices and licenses ad-hoc attributed and revoked to users
Device security policies: devices are managed to protect against exposure and loss of business data

Delivery (Deployment): platform governance and strategy is a prerequisite

For a Citizen Developer to manage the life cycle of his application,
he needs to be able to count on supporting process to be in place

Application Delivery TOM/SOM: application delivery processes clearly describe roles and responsibilities for Business and IT
Delivered Application Support Model: delivered application he can support directly or indirectly
Application DevSecOps policies: business risks and IT risks are controlled by DevSecOps tooling

Digitalization: process oriented automation is a prerequisite

For a Citizen Developer to contribute to the digitalization
he needs to be able to affect end-to-end processes he owns

Monetized Digitalization: processes direct and indirect costs and revenues are quantified (FinOps)
Dematerialized Digitalization: processes descriptions focus on activities (steps towards end-results) before information (content carried between activities)
Optimized Digitalization : end-to-end processes are defined as a set of interrelated activities (process optimization not isolated activity optimization)

Distribution: availability of reusable building blocks is a perquisite

For a Citizen Developer to efficiently assembly his application
he needs to combine distributed building blocks

Distributed Components: reusable front-end components (UI elements) as well as reusable back-end components (Systems/Solutions)
Distributed Connectivity: reusable means of integration between components (data exchange, network connectivity, import/export)
Distributed Responsibilities: reusable cross application responsibilities (generic governance) extending application specific responsibilities of his application (app specific governance)

Citizen Development City Dweller to Townsmen

Evolving Citizen Developers from City Dwellers to Townsmen … so they can become first class citizen

Citizen developers have triggered a new left-shift in the application development.

With the introduction of DevXOps, in its multitude of variations DevSecOps, DevBizOps, DevDataOps … we have seen a first shift toward putting more responsibilities with the developers of applications. The idea that, if we consider security, usability, manageability, operability, monitorability, business value and other *-abilities as quality attributes from the get-go of the development process and not wait till applications get into production, resulted in new application life cycle management (ALM) processes. ALM processes that focus on continuous testing, continuous integration, continuous deployment, continuous feedback, continuous monitoring and continuous operations (7 C’s op DevOps). New ALM processes that support this left-shift from operations to development and can even exonerate developers from these additional responsibilities.

Low-code platforms targeted initially developers with the promise of acceleration introducing the concept of Rapid Application Development (RAD). Using drag and drop features to create UI’s; visual wizards to add business logic for validation and other business rules into applications; and schema generation to expose data to applications all resulted in faster time-to-market of IT solutions.

After the introduction of low-code (L-C) platforms, a new group developers raised to the occasion. Tech savvy business users started to use the same L-C platforms to solve day-to-day problems that could not be picked up quickly by IT departments through traditional or rapid application development. The citizen developer was born. At the beginning this was done covert and resulted in shadow-it. When L-C platforms evolved towards no-code (N-C) capabilities, the need for governing this new group of developers became apparent. This resulted in a second left-shift, now from pro-developers to citizen developers. Also here, responsibilities shifted and this time across the IT – Business chasm.

What are these responsibilities that landed in the laps of the Citizen Developers?

Typically we see first the same responsibilities be shifted, that were apparent already in the first left-shift, from operation to pro-developers. These are mostly IT related risks:

ALM risks: keeping the application up to date through evolving the requirements, architecture and technology of the application to protect against functional obsoleteness and technical debt.
Security Risks: keeping the application secure and protect against incorrect access, usage and data exposure.
Costs Risks: baring the cost of the application and protect against inefficient and uncontrolled spending
Governance Risks: ensure the application is managed as part of a solution architecture landscape

Typically when Citizen Development matures, we see that also business related risk become visible. These should be part of the responsibility shift as well. These Business related risks are:

Strategic Risks: Citizen developer’s focus limited to ad-hoc problem solving i.e. operational problems, forgetting about tactical and strategic long-term solutions. Missed opportunities towards generalization and standardization of solutions leading to redundancy/duplication: excess costs and limited scaling.
Process Risks: Citizen developer’s focus on a part of a business process (one or more activities) resulting in sub-optimal solutions. Automating an inefficient process or part of a process results in an automated inefficiency. It requires an end-to-end process view and level of abstraction beyond the problem at hand to create efficient solutions.
Obsolesce Risks: Citizen developers applying a technology because they can, not because it is the right thing to do: “If you have a hammer everything looks like a nail“. Limited critical reflection on why and when to apply a technology. Lack of understanding of correct usage and limitation of a technology.
Regulatory Risks: Citizen developers’ focus solely on the business process forgetting about regulatory compliance e.g. data usage (GDPR, data privacy) and security (data leakage and data loss). Limited understanding of requirements beyond functional requirements omitting domain and non-functional requirements. Limited accountability toward end-to-end process and compliance of activities part of an end-to-end process.

Most of these risks are managed from within a modern L-C /N-C platform through tooling and monitoring. These are basically where the platforms turn shadow-it into business managed solutions. The business risks are often underexposed in these platforms and managed by means of on-boarding checklists, ideation repositories and usage monitoring.

The latter typically requires a strategy and governance added on top what these platforms can offer. The platform is a means to the end but cannot exonerate an organization of all the responsibilities that were shifted to the Citizen Developers.