Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Technical debt - The elephant in the room
Upcoming SlideShare
Loading in …5
×

Technical debt - The elephant in the room

Code and design debt, test debt, and documentation debt are some of the prominent contributors of the technical debt metaphor in a software product. Increasing technical debt in a software system not only impacts the productivity of the team but also compromises the external product quality. However, identifying and resolving issues pertaining to technical debt often take back seat since development teams and their management prefers to develop a few new features in the software rather than refactor it to repay technical debt. The talk emphasizes on the pragmatism to technical debt management. It brings out the best practices associated with processes as well as practices and discusses pragmatic strategies to manage issues related to technical debt.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

    Be the first to comment

    Login to see the comments

  • omarf

    Jan. 20, 2016
  • powerirs

    Jan. 21, 2016
  • nakafi

    Jan. 24, 2016
  • gougoubaba

    May. 12, 2016

Code and design debt, test debt, and documentation debt are some of the prominent contributors of the technical debt metaphor in a software product. Increasing technical debt in a software system not only impacts the productivity of the team but also compromises the external product quality. However, identifying and resolving issues pertaining to technical debt often take back seat since development teams and their management prefers to develop a few new features in the software rather than refactor it to repay technical debt. The talk emphasizes on the pragmatism to technical debt management. It brings out the best practices associated with processes as well as practices and discusses pragmatic strategies to manage issues related to technical debt.

Views

Total views

1,645

On Slideshare

0

From embeds

0

Number of embeds

775

Actions

Downloads

15

Shares

0

Comments

0

Likes

4

×