Software Quality Management Diagnostic Dashboard
Is your Software Project on the Right Track?
Bugs are costly, delays are frustrating, and inefficiency can cripple your software’s potential. That’s why we’ve developed the SQM — a simple, powerful tool to assess the health of your project and ensure you’re set up for success.
With this template, you can:
Spot risks before they escalate into costly mistakes.
Identify Issues Early 
Save time and money by avoiding rework and missteps.
Optimize Resources 
Set your project up for smooth growth and avoid delays when it’s time to scale.
Boost Scalability 
How Does It Work?
01
Tick the Applicable Statements:
Select statements that relate to your project and mark “Yes” if the answer is positive.
02
Leverage Advanced Algorithms:
Our algorithms calculate your project score, summarizing your strengths and identifying potential weaknesses.
03
Visualize Your Progress:
Instantly receive an overview diagram that provides a snapshot of your project’s current state.
Fill in the template
| Engineering Practices | Applicable | Positive answer |
|---|---|---|
| 1. Is the code version repository being utilized, for example, GitHub or Bitbucket? | ||
| 2. Is there a Code Review process in place? | ||
| 3. Are coding standards defined and adhered to, such as using linters? | ||
| 4. Is a PR review a mandatory step before pushing features to the staging/production environment to ensure quality and avoid future issues? | ||
| 5. Are there different environments set up for development, testing, etc.? | ||
| 6. Is there an assigned Technical Lead who oversees technical aspects? | ||
| 7. Is a Gitflow or a similar workflow approach used? | ||
| 8. Does the .gitignore file exclude sensitive, temporary, and confidential information, including credentials and backups? | ||
| 9. Is information and task distribution within the team balanced to prevent the creation of knowledge silos? |
| UI/UX | Applicable | Positive answer |
|---|---|---|
| 1. Does the UI/UX Lead conduct regular reviews of quality? | ||
| 2. Are the results of quality reviews tracked and documented? | ||
| 3. Does the UI/UX design meet accessibility standards? | ||
| 4. Is the product accessible on phones, tablets, and desktop computers? | ||
| 5. Does the team use a UI kit? | ||
| 6. Does the team utilize components and styles? | ||
| 7. Do designers document their work? | ||
| 8. Is a clickable prototype available? | ||
| 9. Are designers involved in collaboration with front-end and back-end developers? | ||
| 10. Do you collect and review feedback on user actions to improve UX? |
| Database | Applicable | Positive answer |
|---|---|---|
| 1. Is the database design documented? | ||
| 2. Are the changes to the database schema version-controlled, incremental, and reversible? | ||
| 3. Is production data backup executed with a defined frequency? | ||
| 4. Is that true for your project that sensitive data is not stored or stored encrypted? | ||
| 5. Are schemas defined? | ||
| 6. Are table and column namings defined and consistent? | ||
| 7. Are constraints (foreign key, check, not null, length, enum, etc.) for data integrity? | ||
| 8. Are indexes being used for frequent queries? | ||
| 9. Is access allowed only with authentication? | ||
| 10. No manual data and structure changes, only code migrations approach? |
| Infrastructure | Applicable | Positive answer |
|---|---|---|
| 1. Is the Continuous Integration process present? | ||
| 2. Are unit tests integrated with the CI process? | ||
| 3. Is the Continuous Delivery process present? | ||
| 4. Is Infrastructure as Code approach in use? | ||
| 5. Are credentials to the Cloud managed through AWS IAM or similar? | ||
| 6. Is HTTPS being used everywhere? | ||
| 7. Do you monitor your infrastructure? | ||
| 8. Do you have notifications when a critical issue on production appears? | ||
| 9. Do the developers know the infrastructure architecture (not only the source code) to be able to understand and debug problems in the app faster? | ||
| 10. Is the local app setup described and simple? |
| Front End | Applicable | Positive answer |
|---|---|---|
| 1. Do you use the latest major language/framework version? | ||
| 2. Is the project performance being measured? | ||
| 3. Is the README.md file filled with the actual information? | ||
| 4. Are installation notes defined? | ||
| 5. Is the folder structure designed for a modular approach? | ||
| 6. Do you use code analysis tools? | ||
| 7. Are your code and assets minified on production? | ||
| 8. Do you optimize the images on production? | ||
| 9. Do you use caching? | ||
| 10. Do you use a Content Delivery Network (CDN)? |
| Back End | Applicable | Positive answer |
|---|---|---|
| 1. Do you use the latest major language/framework version? | ||
| 2 Is project performance being measured? | ||
| 3. Is the README.md file filled with actual information? | ||
| 4. Are installation notes defined? | ||
| 5. Is the folder structure designed for a modular approach? | ||
| 6. Do you use code analysis tools? | ||
| 7. Do you validate all user inputs? | ||
| 8. Do you handle errors in the best possible way? | ||
| 9. Do you follow the separation of concerns? | ||
| 10. Is permission/role access well-defined and implemented? |
| Quality Assurance | Applicable | Positive answer |
|---|---|---|
| 1. Quality Assurance Engineer is involved in a project. | ||
| 2. Is QA involved in requirements/documentation review? | ||
| 3. Is a staging environment for testing present? | ||
| 4. Is a testing plan present? | ||
| 5. Are acceptance tests defined and implemented in your project? | ||
| 6. Are test cases present? | ||
| 7. Is regression testing being performed before each release? | ||
| 8. Do you use an automated QA approach? | ||
| 9. Is unit test coverage higher than or equal to 70%? | ||
| 10. Is the project as automated as possible (avoiding manual testing to improve the development process)? |
| Project Management | Applicable | Positive answer |
|---|---|---|
| 1. The project goals are clearly defined and communicated to all stakeholders. | ||
| 2. We always have clear requirements and an understanding of what should be implemented. | ||
| 3. Is a formal Project Manager assigned to the project? | ||
| 4. Following Scrum or Kanban methodology. | ||
| 5. Sprint planning meetings are held to plan upcoming work. | ||
| 6. Daily meetings are scheduled. | ||
| 7. PM ensures that all necessary testing and quality assurance steps have been taken before a release. | ||
| 8. Changes to the project scope or timeline are documented and approved by the customer before implementation. | ||
| 9. PM ensures that risk mitigation strategies are in place for high-priority risks. | ||
| 10. Regular project status reports are provided to the customer and all stakeholders. All their reports are saved and accessible. |
