Timeline for Prioritise continuous process improvement with customer work?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 3, 2020 at 7:09 | vote | accept | kqr | ||
| Nov 2, 2020 at 15:38 | answer | added | kqr | timeline score: 0 | |
| Nov 1, 2020 at 23:44 | answer | added | Thomas Owens♦ | timeline score: 2 | |
| Nov 1, 2020 at 11:20 | comment | added | Bogdan | wouldn't it be nice if we could do continuous delivery of this legacy product? That's a bigger project and takes a lot of experimentation, and is not just something one gets out of the way as part of regular fixes of smaller annoyances Actually, it is. If this is important, if it is needed, then you scope it, prioritize it, schedule it, budget it, etc. The real question is: is needed, important and adds value? Or is it just "for fancy", or because it looks cool? If it's the second, then that's a waste and you shouldn't do it at all. If it's the first, you find a way to make it happen. | |
| Nov 1, 2020 at 11:12 | history | edited | kqr | CC BY-SA 4.0 |
added 325 characters in body
|
| Nov 1, 2020 at 11:11 | review | Close votes | |||
| Nov 6, 2020 at 3:03 | |||||
| Nov 1, 2020 at 10:51 | history | edited | kqr | CC BY-SA 4.0 |
added 325 characters in body
|
| Nov 1, 2020 at 9:47 | answer | added | Bogdan | timeline score: 2 | |
| Nov 1, 2020 at 8:28 | comment | added | jonrsharpe | You don't prioritise it because it is continuous. It's not "let's spend this sprint coming up with process improvements instead of software", it's regular retrospectives and "let's try [change] today and see if it helps" at standup. | |
| Nov 1, 2020 at 5:51 | history | asked | kqr | CC BY-SA 4.0 |