Common Pitfalls Citizen Developers Should Avoid When Developing Applications
Whether you work in a large, medium or small organization, applications can be built easily and swiftly using a citizen development approach. But there are some pitfalls to avoid as Citizen Developers go about bringing ideas to life.
1. Forgetting to take account of complexity and risk
To choose a suitable software development life cycle (SDLC), Citizen Developers conduct a suitability assessment. as part of the suitability assessment, a risk/technical grid must be completed. It must assess their projects against two variables:
- Risk categories that are investigated can include: security, operational IT, IT architecture, regulatory, reputational and financial risks.
- Technical complexity takes into account how difficult it is to build the application, integrate it with the wider IT landscape and create the user interfaces.
A common pitfall when assessing the risks associated with a citizen development project is not considering the probability and severity of each.
- High probability/low severity risks are easy to identify. If these risks materialize, they may cause minor issues.
- Low probability/high severity risks can be difficult to identify; however, if this type of risk materializes, it can have a devastating effect on the organization.
Assessing the probability and severity of each risk is important. This information is fed into the
Please log in or sign up below to read the rest of the article.