Key areas to address for a Low Code CoE:
- Portfolio of Products
- People/Skills/Experts
- Process/ALM
- Platform/Governance/Cleanup/Architecture/NFR's (scalability, SLAs)
- Promotion/delivery/training
Consider putting the project through a Business case validation, particularly for larger projects. The business case is how your business visualises and communicates a proposed project, which should continuously be refined. Points to cover:
- Business Case (Idea)
- Customer Segment >
- Value Proposition (what do they get) >
- Channels (API, website, AI Services, .. ) Customer Achievement (get and retain) >
- Revenue (how to make money)
- Key Resources (patches, maintenance) covers technology and data. What tech, people need to build and continue delivering. Data: where does it come from, quality, restrictions, relevancy.
- Partners (dependency e.g. AWS, Azure, Mendix, OutSystems, UiPath, Microsoft, and backup options)
- Cost breakdown
CoE needs to clearly understand its boundaries and responsibilities.
I am a big fan of Total Ownership, clear requirements and goals, using RACI, and stand-ups. For the rest, I try to be agile and malleable. Big projects require more oversight and planning, so I allow teams to change and focus on delivery.
