Roles and Responsibilities
No-code Creator
The no-code creator sits within the business unit and has a strong understanding of the business domain. Importantly, they also possess strong user empathy. They sit within the no-code project team and have been trained in using the no-code tools. They are responsible for the system configuration and quality activities using no-code capabilities.
Responsible for:
Working with the no-code business architect and no-code stakeholder to contribute to requirements and designs activities.
Participating directly within the no-code development team to build the app; responsible for owning specific work items (micro use cases) in the backlog and implementing the use of the no-code tools.
Defining and executing quality assurance (QA) activities to validate end-to-end user scenarios.
Producing user documentation, training, or enablement related to the no-code application.
Working with the no-code business architect to develop feedback mechanisms and collect user and system feedback.
Delivery models:
Applies to all delivery models.
There will be one or more no-code creators on the team based on the size and scope of the no-code application. For larger applications, there may even be multiple team(s) of no-code creators who are working on the application in parallel.
Involvement throughout NCM Stages:
Stage 1 - Business Use Case: Involved with business stakeholders and architects define the business requirements.
Stage 2 - Options Analysis: More limited involvement, but may provide input on the feasibility of no-code solutions and platform capabilities.
Stage 3 - Design and Prototyping: Heavily involved; creates prototypes, translating business requirements into a working model.
Stage 4 - Project Assignment: Assigned responsibilities for developing the MVP once design and scope are finalized.
Stage 5 - Prototype to MVP: Heavily involved in the development of the MVP, transforming the prototype into a functional product.
Stage 6- Feedback Loop: Gathers user feedback on the MVP and iterates the application to improve functionality.
Stage 7 - Governance Checks: Works with governance teams to ensure the application meets compliance and security standards.
Stage 8 - First Release: Works with the rest of no-code team to deploy the MVP to production. Heavily involved in user enablement and docs.
Stage 9 - Feedback Collection: Continues collecting feedback post-release to identify bugs, enhancements, or new features.
Stage 10 - Incremental Improvements: Continues collecting feedback post-release to identify bugs, enhancements, or new features.
Stage 11 - Everyday Delivery: Ensures smooth, ongoing application updates and resolves operational issues as they arise.
Stage 12 - Application Audit: Participates in audits, ensuring compliance, performance, and potential for component reuse.
No-code Architect
The no-code architect (often called business architect) is a business role often filled by a more senior expert. The architect is responsible for setting the most suitable design approach. The architect decides on the right option to deliver the project and the combination of reusable components that will be needed. They also make sure the solution aligns with the business value. They are usually directly involved in the no-code project and own more challenging design or development tasks.
Responsible for:
Working with the no-code stakeholder on defining requirements and designs and ensuring alignment of the options and business needs.
Providing subject matter and process domain expertise that shapes design activities.
Participating directly within the no-code development team to build the app; may take on more challenging components.
Coordinating with IT and Operations to plan, schedule, and conduct Governance reviews.
Coordinating with Operations once the app is approved and ready to deploy to production.
In fusion team delivery scenarios, coordinates with IT software developers to build out custom software components of the no-code application.
In fusion team delivery scenarios, coordinates with IT to build or validate integrations to various backend systems and APIs
Delivery models:
Applies for the CoE and fusion team models. Might be engaged in the DIY model.
The no-code business architect typically sits within the business function itself. However, the CoE may also have a number of architects who can provide subject matter expertise in more specialized areas. They may also help the CoE drive overall standards and best practices, such as fostering, harvesting, sharing, and reuse of components across teams.
Involvement throughout NCM Stages:
Stage 1 - Business Use Case: Collaborates with the no-code stakeholder to define high-level business requirements and success criteria.
Stage 2 - Options Analysis: Assists in evaluating various solution options to ensure the chosen one aligns with business needs.
Stage 3 - Design and Prototyping: Shapes design activities by providing business process expertise and overseeing alignment with goals.
Stage 4 - Project Assignment: Coordinates with teams and ensures alignment of project roles, responsibilities, and business objectives.
Stage 5 - Prototype to MVP: Ensures the MVP design meets business needs and may help build complex components of the application.
Stage 6- Feedback Loop: Reviews feedback to ensure ongoing alignment with business objectives and adjusts the application as needed.
Stage 7 - Governance Checks: Coordinates governance reviews, ensuring the application meets compliance and business governance standards.
Stage 8 - First Release: Works with operations to prepare the application for deployment, ensuring it meets business expectations.
Stage 9 - Feedback Collection: Oversees the collection of feedback to ensure it aligns with the strategic goals of the business.
Stage 10 - Incremental Improvements: Ensures that incremental improvements continue to align with the overall business strategy.
Stage 11 - Everyday Delivery: Provides oversight to ensure the application's day-to-day performance aligns with evolving business needs.
Stage 12 - Application Audit: Conducts periodic audits to ensure continued alignment with business goals and identify opportunities for optimization.
No-code Stakeholder
The no-code stakeholder is a business function role — often a senior functional leader — who acts as an executive sponsor on behalf of the business unit. Typically, they are chartered with articulating the no-code app business vision and requirements and working with the no-code project team to review and approve business use cases, prototypes, MVPs, changes, etc. The no-code stakeholder typically will have a good understanding of the business process and have sufficient authority to make decisions related to functionality. Finally, while the stakeholder does not need to be deeply technical, they should understand the technology and its ability to impact the business.
Responsible for:
Defining and approving the business vision and requirements.
Providing overall direction and feedback that shapes design activities.
Provides feedback directly back to the no-code development team on demos.
Works with no-code team to set priorities for the backlog of micro use cases.
Final approver who indicates the app is ready to deploy to production.
Works with the business function, CoE, and IT teams to procure and assign resources to the no-code project team.
Delivery models:
Applies to all delivery models.
In the CoE or fusion team scenarios, the multidisciplinary teams should still have a dotted-line reporting to the no-code stakeholder who is ultimately responsible for the project direction and success.
Involvement throughout NCM Stages:
Stage 1 - Business Use Case: Defines and approves the business vision, objectives, and key requirements for the project.
Stage 2 - Options Analysis: Oversees the evaluation of potential solutions, ensuring alignment with business needs.
Stage 3 - Design and Prototyping: Provides feedback and direction on designs and ensures alignment with business goals.
Stage 4 - Project Assignment: Approves the final project scope and ensures proper resourcing and team alignment.
Stage 5 - Prototype to MVP: Approves the MVP, ensuring it meets core business objectives and is ready for further development.
Stage 6- Feedback Loop: Provides continuous feedback on the MVP, guiding refinements and adjustments.
Stage 7 - Governance Checks: Ensures the MVP passes necessary governance, compliance, and business alignment checks.
Stage 8 - First Release: Gives final approval for the application's release to production, confirming it meets business expectations.
Stage 9 - Feedback Collection: Reviews post-release feedback to ensure the application continues to meet business needs.
Stage 10 - Incremental Improvements: Prioritizes and approves incremental updates based on ongoing feedback and business goals.
Stage 11 - Everyday Delivery: Oversees the continuous delivery process to ensure the application remains aligned with business objectives.
Stage 12 - Application Audit: Reviews audit findings and ensures the application remains compliant, performant, and valuable to the business.