michalvankodev/michalvankodev-site
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #3 from michalvankodev/cms/blog/2020-11-08-how-to-deal-with-technical-debt

Browse Source 
Automatically generated. Merged on Netlify CMS.
This commit is contained in:
Michal Vanko 2020-12-18 16:08:40 +01:00 committed by GitHub
commit 1bc58e8a94
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
_posts/blog/2020-11-08-how-to-deal-with-technical-debt.md
View File

@ -2,22 +2,22 @@
layout: blog
title: How to deal with technical debt
published: true
date: 2020-11-08T15:57:18.797Z # TODO executable line for generating date
date: 2020-11-08T15:57:18.797Z
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.
Technical debt is a massive problem that 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.
- 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.
Assign a certain amount of story points for each sprint to those tasks which have been accumulated and prioritized.
> _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.
> _Action points_ are tasks agreed upon on **retrospectives**. These are the _points_ which the team has agreed on. They should be solved in the upcoming sprint to make the developer experience better for the whole team.