No amount of dogma should interfere with a deployment within the scope of an MVP. Once it's out of MVP then anything not addressed best practice-wise is tech de

No amount of dogma should interfere with a deployment within the scope of an MVP. Once it's out of MVP then anything not addressed best practice-wise is tech debt. If your organization had adopted 12FA as a set of best practices then those should be met, but they should never interfere with a deployment. 12FA is not a single box that is to be checked. It can and in most cases probably should be implemented over time as the product matures, taking each point, point by point (and maybe even breaking those up) and adding that into the product. If you've done good engineering up front (abstractions and interfaces where it makes sense, not hard coding everything) this should not be an issue. inb4 YAGNI: this is just as abused as 12FA. EDIT: the biggest thing 12FA is missing are concrete examples that junior engineers can reference.