Establishing a governance model
The whole purpose of governance is defining processes to simplify everything that is happening and that is necessary for the product. This starts at the initial required analysis stage and ends with maintenance efforts.
From a technical point of view, a governance model helps us identify what processes can be left unautomated and which ones need automation.
In general, there are multiple areas that can be covered with such a governance model, as follows:
- Business analysis (such as roadmaps, timelines, and monetarization)
- Requirement definitions (such as use cases, effort, and risks)
- Software architecture (such as performance and security)
- UX design (such as guidelines)
- Implementation (such as code quality and feature implementation)
- Testing (such as plans, coverage, and scores)
- Documentation (such as documents)
- Deployment (such as instructions)
- Maintenance (such as troubleshooting, bugs, and feature requests...
