Re:Audiblegate
by duped on Thursday February 17, 2022 @10:41AM
(#30374249)
I'm not talking about any specific PM strategies though. For the software to be written, it must be specified. Whether that's in a ticket or design doc is irrelevant.
As you point out, the agile manifesto eschews documentation for working software. This is not about having documentation, it's about defining "working" for the software. The ticket could not be written or handled without consultation with legal or BA teams on how the formulae are defined, similarly to how if you're implementing any kind of system where the formulae are critically important for correctness you need to consult back and forth with the expert stakeholders to double check.
I don't know any other way to do this that isn't negligent, not just by the developer, but by the reviewer, the stake holders, and ultimately the PM that signs off on accepting the task as "done" when it hasn't been checked for correctness.
As you point out, the agile manifesto eschews documentation for working software. This is not about having documentation, it's about defining "working" for the software. The ticket could not be written or handled without consultation with legal or BA teams on how the formulae are defined, similarly to how if you're implementing any kind of system where the formulae are critically important for correctness you need to consult back and forth with the expert stakeholders to double check.
I don't know any other way to do this that isn't negligent, not just by the developer, but by the reviewer, the stake holders, and ultimately the PM that signs off on accepting the task as "done" when it hasn't been checked for correctness.