Dear Client, Here’s Why That Change Took So Long

Post by watwut » Thu, May 09, 2019, 9:05 PM UTC

irq11 wrote: post #239

watwut wrote: post #220

Earlier quoted context omitted.

Are you saying there is trust between you and developers? Cause you surely don't trust them and the way you describe their communication sounds like they don't trust you. Also, if they give you non-padded estimate, that is the one they will occasionally miss, will typical manager of your company force them to work weekends and evenings or otherwise punish them? Or will typical be ok with it and accept it as risk fact…

Rather than second-guessing a total stranger on the internet - concerning a situation about which you know nothing - you would do well to question why you insist on assuming that everyone is as bad as the worst manager you’ve had. To answer your question: no. I don’t do any of that. Also, this situation has nothing to do with aggressive schedules.

Post by bfdm » Sat, May 11, 2019, 5:27 AM UTC

megablast wrote: post #165

maccard wrote: post #107

Earlier quoted context omitted.

On the contrary, there are plenty of devs who won't take on any work until it's been designed, scoped, run through management, prioritised and scheduled, when the actual fix is a one line change that would have taken less effort than the meeting where it was prioritised. There's a happy middle ground between the two, and assuming developers who will deliver quick fixes are all hacks who don't care is counterproductiv…

Ha, hilarious. I have had changed that were done as soon as they were mentioned, but still required several more meetings to ensure everyone was aware of the upcoming change, had signed of on it (even though it was a severe bug), and discussed it ad-infinitum. Including how to do it, even though I already did it at the start of the meeting. Approximately 100x the time it took to do the work.

Post by majkinetor » Sat, May 11, 2019, 6:26 AM UTC

bfdm wrote: post #284

majkinetor wrote: post #152

Earlier quoted context omitted.

Definition of Done (DoD) does not exist. It is whatever stakeholder needs it to be. Stakeholder might be delusional or not, its your thing to educate or if impossible, avoid working in toxic conditions that future will bring. Everything is a feature: - Automatic tests, a feature. You can buy it if you want or you can accept accidental bugs any time even for stuff that worked before, or even complete meltdown. You don…

I'm not sure how any of that relates to you suggesting "DoD does not exist" above. What do you mean? The DOD is not a singular ruleset, but something defined by the project team, and which can evolve as the needs or the project request. It may or may not involve some or all of the components you've mentioned.