Gergely OroszFeb 26, 2023

A mistake less experienced software engineers make when it comes to estimations:

They break out maintainability/quality. Eg “building the feature is 2 weeks, adding automated tests another 3 days”.

What follows by less technical stakeholders is a push to remove the latter.

Non-functional requirements like correctness, quality, maintainability, performance etc should be baked into estimates, and not made part of bargaining. That bargaining is how sw can become less maintainable over time.

Show threadJRFeb 26, 2023

@gergelyorosz Quality is part of scope. Who has the authority to change scope? Product management, not devs.

Theoretically a "definition of done" explicitly invoked in the estimation phase deals with this. That said, my experience with a "hard" DoD has been mixed.

Show threadBarrett
@rodley @gergelyorosz concur with the statement that quality is part of scope, as a PO . As a dev, though, I see a ton of POs that don’t understand enough about the dev process to make informed decisions about quality.
Feb 26, 2023 at 7:36pmMastodon for iOS
Show threadJRFeb 26, 2023
@ba66e77 @gergelyorosz
That's why people resort to a "hard" DoD. We only ship stories of a known quality. You want to reduce scope, use feature-scope, not quality-scope.