Registration | Technical Debt for Policymakers

[pie_register_form id=”1″ title=”true” description=”true” ]

Reference posts

Posts you might want to refer to

A collection of definitions of terms as we use them in this blog, with links to longer discussions of each term. Along with each definition is a link to a post that discusses that term in more detail. Read more…

Welcome to Technical Debt for Policymakers

Welcome to Technical Debt for Policymakers. What you’ll find here are resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Read more…

References

Bibliography and citations used in some of my posts, many with links to the published papers or Web pages. Read more…

Recent Posts

Refactoring for policymakers

To refactor an asset is to apply a series of small, behavior-preserving changes to improve the structure of the asset. When effects are observable externally, they’re very specific, usually related to attributes such as quality and usability.

Outsourcing Technical Debt Retirement Projects

Because situational details are so important, there’s no formula for choosing to outsource technical debt retirement projects. But there are guidelines.

Automation-assisted technical debt retirement

When we retire technical debt from assets, service disruptions might be necessary. Automating some procedures can minimize those disruptions and avoid errors and rework.

Controlling incremental technical debt

Organizations are more likely to gain control of their legacy technical debt portfolio if they begin by controlling the transformation of incremental technical debt into legacy technical debt.

Retiring localizable technical debt

Technical debt that appears as discrete chunks—localizable technical debt—is more readily retired, because we can do it incrementally, piece by piece. It’s a particularly manageable challenge.

Share this: