24 lines
1.0 KiB
Markdown
24 lines
1.0 KiB
Markdown
|
---
|
||
|
|
layout: blog
|
||
|
|
title: How to deal with technical debt
|
||
|
|
published: true
|
||
|
|
date: 2020-11-08T15:57:18.797Z # TODO executable line for generating date
|
||
|
|
tags:
|
||
|
|
- Development
|
||
|
|
notes: Dont forget the todos
|
||
|
|
---
|
||
|
|
|
||
|
|
Technical debt is a massive problem which costs a lot of time for everyone working on the team.
|
||
|
|
It should be part of the development cycle to eliminate it.
|
||
|
|
**Manage a secured time** in a development process to increase development experience.
|
||
|
|
|
||
|
|
By planning **regular tasks** like:
|
||
|
|
|
||
|
|
- Upgrading dependencies, gathering information about migrations and creating tasks for those which require attention.
|
||
|
|
- Solving _action points_ discussed on retrospective.
|
||
|
|
- Finding and creating tasks for dealing with technical debt.
|
||
|
|
|
||
|
|
Assign a certian amount of story points for each sprint to those tasks which have been accumulated and proritized.
|
||
|
|
|
||
|
|
> _Action points_ are tasks agreed upon on **retrospectives**. These are the _points_ which team has agreed on. They should be solved in the upcoming sprint to make developer experience better for whole team.
|