The funny thing is that you can - and probably should - do a development style that gives you increments and quick feedback (I'm careful around the term "agile" these days since the consultants kidnapped and raped it); it's probably gonna be a style of work that's much heavier on initial specifications and testing, etcetera; but most of the principles would apply (I know - I worked in this style in heavily regulated industries which were heavily regulated because people would otherwise die).
The issue is that agile does not mean "deploy crap to production and let your customers be your QA staff". It means that you iterate, learn, and that way develop the code that your business/customers needs - including the level of quality required. Re-read the manifesto for agile software development. Nothing there about "ship fast and fail fast", that's only appropriate in some contexts.