Off Topic: Sources of Technical Depth
Software projects which are in the maintenance phase of their life cycle have to deal with Technical Depth soon or late. Sometimes this can be completely ignored by the development team and project managers. Early warning of a non managed technical depth is causing a full stop in the new feature development. In worst case it can cause a reboot in the software project which means efforts to maintain project stability is bigger than redevelopment of the product. Classically technical depth is something hidden in the source code of the software. Therefore naturally it is something invisible for the product managers without any software development skills. In this case it is software development teams responsibility to make it visible for other steak holders. This type of depth is grouped in the left side of the source diagram. Internal Sources of Technical Depth Classical technical depth sources can be enumerated as follows: Legacy Code Any piece of code written in t...