3 ms·
And, plenty of surgeries are done in situations where speed matters more than the quality of the surgery (emergency tracheotomy, amputation, etc.)
by qq66 9y ago
And, plenty of surgeries are done in situations where speed matters more than the quality of the surgery (emergency tracheotomy, amputation, etc.)
- dvt 9y agoSpeed never matters more than the quality of the surgery. You're conflating constraints and criteria. Speed is sometimes a constraint, but never a criteria.
- brucephillips 9y agoConstraints are criteria.
- zbentley 9y agoNo, they're not. If you violate a constraint, delivery fails. If you pass it, delivery does not necessarily succeed. If you fail to meet a criterion, delivery might fail. If you successfully meet all criteria, this is the definition of successful delivery. Different places may assign different meanings to those terms in project-management speak, but those are the ones I've heard the most.
- brucephillips 9y agoYou're confusing an equality relationship and a subset relationship.
- dvt 9y agoNo they aren't. Constraints are necessary but not sufficient. Criteria are necessary and sufficient. In other words, necessity is a lower bound and sufficiency is an upper bound. Criteria is the upper bound, constraints are the lower bound. [1] https://www.sfu.ca/~swartz/conditions1.htm https://www.sfu.ca/~swartz/conditions1.htm
- brucephillips 9y agoYou're also confusing an equality and a subset relationship.
- stefco_ 9y agoBut speed is a self-imposed constraint on most projects rather than a physical law, meaning it might be violated. Furthermore, there might be a smooth relationship between speed of execution and value returned (even outside of cost of production). So when evaluating how successful a project was (software, surgery, or otherwise), you often do want to use speed as a criterion, even if you initially thought of it as a sort of constraint for the sake of simplifying planning.