Update TechnicalDebtMonitoring.md #305
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
Scawie
reviewed
Jun 4, 2025
| - Testing – Unknown or unrecorded test scenarios, lack of test coverage | ||
| - Maintenance – Out-of-support products, usually leading to security vulnerabilities | ||
| - Process - inefficient or wasteful process steps, this could be related to practice or tooling | ||
| - Security - Known and exploitable vulnerabilities |
Scawie
reviewed
Jun 4, 2025
| - A **Technical debt** work item type **MUST** be created in target project. Using queries and dashboads it is then possible to monitor Technical Debt. | ||
|
|
||
|  | ||
|
|
Scawie
reviewed
Jun 4, 2025
| - A **Technical debt** work item type **MUST** be created in target project. Using queries and dashboads it is then possible to monitor Technical Debt. | ||
|
|
||
|  | ||
|
|
There was a problem hiding this comment.
Enclose bare links in angle brackets (ln 107-109)
Scawie
reviewed
Jun 4, 2025
| - A **Technical debt** work item type **MUST** be created in target project. Using queries and dashboads it is then possible to monitor Technical Debt. | ||
|
|
||
|  | ||
|
|
Scawie
reviewed
Jun 4, 2025
| ## Points of Contact | ||
|
|
||
| * Policy Owner - Principal Support Developer | ||
| - Policy Owner - Principal Support Developer |
Scawie
reviewed
Jun 4, 2025
| - Instability | ||
| - Security Concerns | ||
| - Add a new section called Status | ||
| - Add field for Scheduled Release |
Scawie
reviewed
Jun 4, 2025
| * Security Concerns | ||
| * Add a new section called Status | ||
| * Add field for Scheduled Release | ||
| - A **Technical debt** work item type **MUST** be created in target project. |
There was a problem hiding this comment.
ln 6-7 indent should be 2 spaces
Scawie
reviewed
Jun 4, 2025
| * Security Concerns | ||
| * Add a new section called Status | ||
| * Add field for Scheduled Release | ||
| - A **Technical debt** work item type **MUST** be created in target project. |
There was a problem hiding this comment.
found and destroyed
elerivaliant
reviewed
Jun 4, 2025
software-engineering-policies/TechnicalDebt/TechnicalDebtPolicy.md
Outdated
Show resolved
Hide resolved
| ### Strategy | ||
|
|
||
| * A **Technical debt** work item type **MUST** be created in target project. Using queries and dashboads it is then possible to monitor Technical Debt. | ||
| - A **Technical debt** work item type **MUST** be created in target project. Using queries and dashboads it is then possible to monitor Technical Debt. |
There was a problem hiding this comment.
Suggested change
| - A **Technical debt** work item type **MUST** be created in target project. Using queries and dashboads it is then possible to monitor Technical Debt. | |
| - A **Technical debt** work item type **MUST** be created in target project. Using queries and dashboards it is then possible to monitor Technical Debt. |
There was a problem hiding this comment.
went out of date, but is fixed
Comment on lines
16
to
42
| - Add new Details section with the following fields (use existing field, do not create a new field): | ||
| - Primary Product or Service | ||
| - there may be several interconnecting products but which is the main one, if needed, create a separate TD item for each product if they would be addressed separately. | ||
| - Technical priority | ||
| - TD1 - High business/technical value, high risk debt that needs to be paid off ASAP (a Security tag should automatically be considered for a TD1 prioritisation). | ||
| - TD2 - High business/technical value (cost reduction, blocker removing, maintainability improvement), lower risk, a change that should be worked on when time/opportunity permits and is not something that can be accepted or supported long term. | ||
| - TD3 - Tech debt that has been accepted as a risk but through paying off would add value through improving usability, maintainability, reliability or performance. | ||
| - TD4 - Accepted risk from the business, safe to leave until service reaches end of life. Worth tracking in case developers are working in the area and can complete as quick wins. | ||
| - Technical debt type | ||
| - Architectural – Tightly coupled systems (lots of criss-crossed dependencies), - restrictive to extension or automation | ||
| - Code – Low quality code or ineffective patterns | ||
| - Knowledge – lack of documentation or inaccessible documentation | ||
| - Automation – Lack of automated tasks forcing manual intervention (Testing, deployments, - backup/restore) | ||
| - Testing – Unknown or unrecorded test scenarios, lack of test coverage | ||
| - Maintenance – Out-of-support products, usually leading to security vulnerabilities | ||
| - Process - inefficient or wasteful process steps, this could be related to practice or - tooling | ||
| - Security - Known and exploitable vulnerabilities | ||
| - Technical debt impact | ||
| - Increased time to deliver | ||
| - Unplanned work | ||
| - Inaccurate planning | ||
| - Disengaged Development teams | ||
| - Longer times to recover | ||
| - Instability | ||
| - Security Concerns | ||
| - Add a new section called Status | ||
| - Add field for Scheduled Release |
There was a problem hiding this comment.
Whole section seems to have a lot of random spacing and a mix of different hyphenation with some random hyphens at the end of sentences which makes reading it a bit tricky!
There was a problem hiding this comment.
Think I got them all.
…y.md Co-authored-by: Eleri Valiant <eleri.valiant@ukho.gov.uk>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.