On 12/22/2015 10:40 AM, Andrew Halberstadt wrote:
I'd prefer to see quality be a perpetually ongoing effort over a
periodic burst. I'd like to see management rotate people into "quality
mode" by explicitly setting goals and deliverables around addressing it.
I agree that it is necessary to have management and goals/deliverables
backing this. Otherwise, in my experience, very little gets done. It
doesn't need to be an entire org, but if each team rotated one or two
people at a time through this on a regular basis, it would make a
significant difference.
The problem in the past has been this notion of "greatest impact".
Things like refactorings and fixing tests always get deprioritized
because it's really hard to estimate how beneficial they are to the
overall mission. It was much easier to say shiny new feature X aligns
nicely with our top-line goals.
Bingo! If we as an organization want to be serious about quality and
"strengthening our core" as a top-line item, we must be willing to
prioritize some of this stuff and make sure that people feel that they
are having an impact by working on it. Otherwise it always becomes
"somebody else's problem."
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
