How do you manage technical debt that isn’t technical?
How do you explain to managers and MBAs how certain choices affect software in terms they can understand?
How do you keep track of shortcuts in features, functionality, and UX? And explain how they cost more to correct the longer they’re missing?
With a new twist on an old metaphor, that’s how.
Continue reading Introducing the Feature Debt Metaphor