Re:How necessary are the programming fundamentals?
by ChrisMarshallNY on Wednesday May 19, 2021 @07:41AM
(#27207212)
Quality, Cost, Deliverable.
The Japanese live by it. If you ever want to work with a Japanese company, it's a good idea to know it. I think Deming may have started it.
"Quality":
How do we measure the deliverable? Not just testing targets. Any form of quantification. Progress tracking goes here, as does a lot of things like CI.
"Cost":
What will the cost of the deliverable be? Not just money, but also schedule, the number of folks working on it, prototypes, BoM, progress meetings, buy-in from stakeholders, risk management, etc.
"Deliverable":
What will be delivered? Please describe expected deliverable, what will be delivered at milestones defined in (Q) and (C).
It's a very rigid process (good for hardware), but can be difficult to deal with in software. I've learned to do my own version of it. I've written about it.
BTW: I just demonstrated "jargon," but in a different way. I do not think less of you for not knowing it.
The Japanese live by it. If you ever want to work with a Japanese company, it's a good idea to know it. I think Deming may have started it.
"Quality":
How do we measure the deliverable? Not just testing targets. Any form of quantification. Progress tracking goes here, as does a lot of things like CI.
"Cost":
What will the cost of the deliverable be? Not just money, but also schedule, the number of folks working on it, prototypes, BoM, progress meetings, buy-in from stakeholders, risk management, etc.
"Deliverable":
What will be delivered? Please describe expected deliverable, what will be delivered at milestones defined in (Q) and (C).
It's a very rigid process (good for hardware), but can be difficult to deal with in software. I've learned to do my own version of it. I've written about it.
BTW: I just demonstrated "jargon," but in a different way. I do not think less of you for not knowing it.