My Principles in Process Engineering
- There is no one size fits all process. It needs to be catered to your needs. Templates such as CMMi and IEEE may offer guidance. But it is important that you analyze your process requirements and come up with a process that is efficient, effective and sustainable.
- Continue to adjust and improve. It is a must to keep on improving. Processes; especially ones that are targeting to assure product quality must monitor its success, and adjust and improve where necessary.
- Identify tools that support and enrich the process
- JIRA
- Confluence
- Trello
- Bitbucket and Pipelines
- Jenkins
- Use industry best practices to guide you. There is no need to re-invent the wheel
- When introducing process changes, adhere to a gradual approach; rather than a big-bang. People typically don't welcome change when it's dropped on their head.
- Ensure that the Dev process provides clear visibility into progress for the management to take informed decisions
- Document the process in an easy to understand format, such as flow charts and associated literature.
QA focused success measurements
Here are some of my go-to metrics; or success measurements. I believe that a strategy, or a process should always be measurable to be successful.
- Requirement effectiveness
- Requirement bounce rate
- Non-compliance rate by project
- Test coverage by requirement
- Test coverage by release
- Test suite effectiveness
- Defects per test
- Defect bounce rate
- Residual defect density
- Resolved Vs Reported defects
- Deployed Vs Delivered features
