Timeline for How to represent technical debt in agile development using azure devops?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2023 at 12:48 | comment | added | Alex Constantin | Definitely has to do with what devs are rewarded for. I find the average attention span of the present-day dev to also play a factor. In certain cases it can digress to be just a copy/paste race in a team -- find that perfect niche YT video/blog that shows exactly what to copy/paste for your problem before your colleagues do, just do it (don't reason as to the merits, approach, risks) & if it works, cool -- pat oon the back for you, on to the next one. | |
| Nov 18, 2022 at 14:13 | comment | added | Ryathal | not just devs. Several times I've seen entire processes built around the assumption everything is code that goes to prod, and developers are essentially graded only on shipping code. Developers apparently never write implementation plans, documentation, prototype, research libraries to use, or prepare a knowledge transfers. | |
| Nov 18, 2022 at 7:06 | comment | added | Phill W. | +1 for "There are more things that deliver value than deploying newly implemented features." Too many Devs I meet are focussed on [coding] the new stuff and [try to] ignore anything and everything else! | |
| Nov 17, 2022 at 20:52 | history | edited | Ryathal | CC BY-SA 4.0 |
added 3 characters in body
|
| Nov 16, 2022 at 16:49 | history | answered | Ryathal | CC BY-SA 4.0 |