Skill-Profil

Technical Debt Management

Identification, prioritization, tracking, and strategies for paying down technical debt

Architecture & System Design Architecture Governance

Rollen

wo dieser Skill vorkommt

Stufen

strukturierter Entwicklungspfad

Pflichtanforderungen

die anderen 4 optional

Domäne

Architecture & System Design

skills.group

Architecture Governance

Zuletzt aktualisiert

17.3.2026

Verwendung

Wählen Sie Ihr aktuelles Level und vergleichen Sie die Erwartungen.

Was wird auf jedem Level erwartet

Die Tabelle zeigt, wie die Tiefe von Junior bis Principal wächst.

Rolle	Pflicht	Beschreibung
1C Developer		Understands basic architectural concepts of Technical Debt Management. Follows team architectural decisions. Understands main patterns.
Technical Product Manager	Pflicht	Understands the technical debt concept and its impact on product delivery speed. Knows the difference between deliberate and accidental debt. Can document tech debt items with business impact.

Rolle	Pflicht	Beschreibung
1C Developer		Applies technical debt management when designing 1C:Enterprise components. Understands trade-offs between quick fixes and proper refactoring of legacy configurations. Participates in discussions on platform upgrade planning and deprecated API migration strategies.
Engineering Manager		Applies technical debt management when planning sprint capacity. Understands trade-offs between feature delivery and debt reduction. Participates in budgeting discussions, tracks team velocity impact of accumulated debt, and communicates priorities to stakeholders.
Technical Lead		Applies technical debt management when designing components. Understands trade-offs between delivery speed and code quality. Participates in architectural discussions, tracks debt via SonarQube metrics, and enforces code quality gates during code reviews.
Technical Product Manager	Pflicht	Independently evaluates and prioritizes technical debt. Calculates cost of delay for tech debt items. Balances tech debt payoff with feature delivery in sprint planning. Maintains tech debt register with business justification.

Rolle	Pflicht	Beschreibung
1C Developer	Pflicht	Designs 1C:Enterprise architecture with technical debt management in mind. Makes architectural decisions on legacy configuration refactoring and documents them via ADR. Evaluates platform upgrade paths and plans deprecated API migration to reduce accumulated debt.
Engineering Manager	Pflicht	Designs team processes with technical debt management as a core practice. Makes decisions on sprint allocation for debt reduction and documents trade-offs via ADR. Evaluates velocity impact of tech debt and builds stakeholder communication plans for remediation efforts.
Solutions Architect	Pflicht	Designs system architecture with technical debt management as a guiding principle. Makes architectural decisions on modernization roadmaps and documents them via ADR. Evaluates architectural debt across systems and applies strangler fig patterns for incremental migration.
Technical Lead	Pflicht	Designs system architecture with technical debt management at the forefront. Makes architectural decisions on refactoring prioritization and documents them via ADR. Evaluates code-level debt using SonarQube metrics and enforces quality gates to prevent new debt accumulation.
Technical Product Manager	Pflicht	Defines tech debt management strategy for the product. Implements tech debt budget: 20% capacity allocation. Designs metrics for tracking debt growth and payoff. Makes architecture decisions considering debt accumulation.

Rolle	Pflicht	Beschreibung
1C Developer	Pflicht	Defines architectural strategy for 1C:Enterprise products with technical debt focus. Establishes guidelines for legacy configuration refactoring and platform upgrades. Conducts architecture reviews ensuring deprecated API migration aligns with platform evolution.
Engineering Manager	Pflicht	Defines product architectural strategy with Technical Debt Management. Shapes architecture guidelines. Conducts architecture reviews.
Solutions Architect	Pflicht	Defines product architectural strategy with technical debt management focus. Establishes guidelines for architectural debt assessment and modernization roadmaps. Conducts architecture reviews ensuring strangler fig patterns and migration strategies reduce systemic debt.
Technical Lead	Pflicht	Defines the product's architectural strategy with Technical Debt Management. Establishes architecture guidelines. Conducts architecture reviews.
Technical Product Manager	Pflicht	Defines tech debt management framework for the division. Introduces systematic debt assessment and prioritization. Shapes business case for large-scale refactoring initiatives. Trains TPMs on tech debt advocacy.

Rolle	Pflicht	Beschreibung
1C Developer	Pflicht	Defines organizational architectural strategy for 1C:Enterprise ecosystems. Designs reference architectures for legacy configuration modernization and upgrade governance. Establishes architecture governance for systematic deprecated API migration and debt elimination.
Engineering Manager	Pflicht	Defines organizational strategy for technical debt management across teams. Designs reference frameworks for debt budgeting, sprint allocation policies, and velocity impact measurement. Establishes governance for stakeholder communication and debt reduction accountability.
Solutions Architect	Pflicht	Defines the organization's architectural strategy for managing technical debt at scale. Designs reference architectures with modernization roadmaps and strangler fig patterns. Establishes architecture governance for systematic debt assessment and cross-portfolio remediation.
Technical Lead	Pflicht	Defines the organization's architectural strategy for technical debt elimination. Designs reference architectures with built-in refactoring prioritization and SonarQube quality gates. Establishes architecture governance for code-level debt tracking and continuous quality improvement.
Technical Product Manager	Pflicht	Shapes enterprise tech debt management strategy. Defines organizational investment in debt reduction. Coordinates large-scale modernization programs. Builds executive-level reporting for technology health.

Junior 2 Anforderungen

1C Developer

Understands basic architectural concepts of Technical Debt Management. Follows team architectural decisions. Understands main patterns.
Technical Product Manager
Pflicht

Understands the technical debt concept and its impact on product delivery speed. Knows the difference between deliberate and accidental debt. Can document tech debt items with business impact.

Middle 4 Anforderungen

1C Developer

Applies technical debt management when designing 1C:Enterprise components. Understands trade-offs between quick fixes and proper refactoring of legacy configurations. Participates in discussions on platform upgrade planning and deprecated API migration strategies.
Engineering Manager

Applies technical debt management when planning sprint capacity. Understands trade-offs between feature delivery and debt reduction. Participates in budgeting discussions, tracks team velocity impact of accumulated debt, and communicates priorities to stakeholders.
Technical Lead

Applies technical debt management when designing components. Understands trade-offs between delivery speed and code quality. Participates in architectural discussions, tracks debt via SonarQube metrics, and enforces code quality gates during code reviews.

Senior 5 Anforderungen

1C Developer
Pflicht

Designs 1C:Enterprise architecture with technical debt management in mind. Makes architectural decisions on legacy configuration refactoring and documents them via ADR. Evaluates platform upgrade paths and plans deprecated API migration to reduce accumulated debt.
Engineering Manager
Pflicht

Designs team processes with technical debt management as a core practice. Makes decisions on sprint allocation for debt reduction and documents trade-offs via ADR. Evaluates velocity impact of tech debt and builds stakeholder communication plans for remediation efforts.
Solutions Architect
Pflicht

Designs system architecture with technical debt management as a guiding principle. Makes architectural decisions on modernization roadmaps and documents them via ADR. Evaluates architectural debt across systems and applies strangler fig patterns for incremental migration.

Lead / Staff 5 Anforderungen

1C Developer
Pflicht

Defines architectural strategy for 1C:Enterprise products with technical debt focus. Establishes guidelines for legacy configuration refactoring and platform upgrades. Conducts architecture reviews ensuring deprecated API migration aligns with platform evolution.
Engineering Manager
Pflicht

Defines product architectural strategy with Technical Debt Management. Shapes architecture guidelines. Conducts architecture reviews.
Solutions Architect
Pflicht

Defines product architectural strategy with technical debt management focus. Establishes guidelines for architectural debt assessment and modernization roadmaps. Conducts architecture reviews ensuring strangler fig patterns and migration strategies reduce systemic debt.

Principal 5 Anforderungen

1C Developer
Pflicht

Defines organizational architectural strategy for 1C:Enterprise ecosystems. Designs reference architectures for legacy configuration modernization and upgrade governance. Establishes architecture governance for systematic deprecated API migration and debt elimination.
Engineering Manager
Pflicht

Defines organizational strategy for technical debt management across teams. Designs reference frameworks for debt budgeting, sprint allocation policies, and velocity impact measurement. Establishes governance for stakeholder communication and debt reduction accountability.
Solutions Architect
Pflicht

Defines the organization's architectural strategy for managing technical debt at scale. Designs reference architectures with modernization roadmaps and strangler fig patterns. Establishes architecture governance for systematic debt assessment and cross-portfolio remediation.

Community

👁 Beobachten ✏️ Aenderung vorschlagen

Kommentare werden geladen...