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

Re:Dear Client, Here’s Why That Change Took So Long by hinkley on Tuesday May 07, 2019 @02:19PM (#19852041)

Yes, there is. Probably the best four projects I worked on, there was collusion to spread out the cost of necessary maintenance across all work items. Because nobody will agree to doing maintenance stories (this is how Scrum hijacks developer ethics). Never ask permission to do something that must be done.

Or to look at it another way, if no stories are maintenance stories, then all stories are maintenance stories.

[ Parent | on HN ]

Re:Dear Client, Here’s Why That Change Took So Long by novaleaf on Tuesday May 07, 2019 @03:29PM (#19852641)

I used to be all about jumping on the next fancy thing as soon as it was (pre)released. Having been burnt and learned my lesson, now I delay until it's blindingly obvious it needs to be done.

But yeah, if it needs t be done, do it.

[ Parent | on HN ]

Re:Dear Client, Here’s Why That Change Took So Long by Sharlin on Tuesday May 07, 2019 @05:24PM (#19853579)

Version x.y.0 of most software is "public beta" quality. x.y.1 is "release candidate". x.y.2 might be production-ready.

[ Parent | on HN ]