how to deal with technical debt
This commit is contained in:
parent
f34e72c53e
commit
83e85d147a
23
_posts/blog/2020-11-08-how-to-deal-with-technical-debt.md
Normal file
23
_posts/blog/2020-11-08-how-to-deal-with-technical-debt.md
Normal file
@ -0,0 +1,23 @@
|
||||
---
|
||||
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.
|
@ -2,6 +2,7 @@ backend:
|
||||
name: github
|
||||
repo: michalvankodev/michalvankodev
|
||||
branch: master # Branch to update (optional; defaults to master)
|
||||
site_domain: michalvanko.dev
|
||||
|
||||
media_folder: 'static/images/uploads' # Media files will be stored in the repo under images/uploads
|
||||
public_folder: '/images/uploads' # The src attribute for uploaded media will begin with /images/uploads
|
||||
|
Loading…
Reference in New Issue
Block a user