Data Tech Debt
From the book I Am Datapedia!, published here free by the author.
Part of I Am Datapedia!
Questions 1–10 of 10
1. What does the term 'technical debt' refer to in software development?
2. Technical debt is compared to which everyday concept?
3. Which type of general technical debt describes rushed or inadequate system architecture that makes adding new features difficult?
4. In the data world, which kind of technical debt is illustrated by rushing to type in students' grades and ending up with inaccurate information, like wrong scores on a report card?
5. Information gathered from several friends for a school project does not fit together because their different formats were never reconciled, like a puzzle with mismatched pieces. Which data technical debt does this describe?
6. The treehouse analogy, where a poor initial plan makes it hard to add a slide or secret door later, illustrates which data technical debt?
7. Which consequence is associated with data governance debt, illustrated by a school with unclear rules?
8. The treasure map analogy, where important clues and rules were never written down, illustrates which data technical debt?
9. Which of the following is NOT listed as a way of addressing technical debt in the data world?
10. Which factors are given as causes of technical debt arising?