1 to 1 of 1
Sort by

Blog Entry
Proselyte, or How I Learned to Manage SharePoint Debt

Sterling identifies five types of software debt: Technical Debt: a team or team members choose not to do well now and will impede future development if left undone Quality Debt: a diminishing ability to verify the functional and technical quality of software Configuration Management Debt: integration and release management become more risky, complex, and error-prone Design Debt: the cost of adding features is increasing toward the point where it is more than the cost of writing from scratch Platform Experience Debt: the availability of people to work on software changes is becoming limited or cost-prohibitive The scenario and accompanying formula is straightforward

Mimi Dionne's profile image