Please enable JavaScript.

Coggle requires JavaScript to display documents.

Technical debt and agile software development practices and processes: An…

- - - - non-strategic result of doing a poor job.
    - - occurs when an organisation makes a conscious decision to optimize for the present rather than for the future.
  - - - From visible
        
        new features, additional functionality,
        defects, and low external quality
      - To Invisible
        
        architectural debt structural debt, test debt, documentation debt, code complexity, low internal quality, coding style violations, and code smells
    - - issue type,
        from evolution to quality
        
        listed issues, new features, additional functionality, architectural debt, structural debt, and test debt are evolution issues, coding style violations, code smells, defects, and low external quality are quality issues, and documentation debt, code complexity, and low internal quality fall in between
- - - - RQ2
        (a) What are the perceived drivers of technical debt, and
        (b) which software development phases does technical debt affect?
      - RQ3
        (a) Are practices and processes of agile methods perceived to have an effect on technical debt or its management, and
        (b) which practices are deemed to have the most significant effect?
      - RQ1
        (a) Are there differences in various stakeholders’ perceptions of technical debt, and
        (b) do stakeholders’ backgrounds affect such perceptions?
  - - - Part 1 - general
        demographic information
        
        Individual
        
        Work
      - Part 2 - agile software
        development techniques
        
        agile practices and processes
      - Part 3 - technical debt
        
        technical debt knowledge
        
        recollections of a specific instance
        of technical debt and its effects.
- - - - the closeness of the ‘technical debt’ concept to the concept of ‘software legacy’ should be carefully examined to establish if practi- tioners fully distinguish between the two concepts.