3-4 releases a year sounds like there might be a solid QA cycle involved. e.g. I used to work on a webapp for flight planning: how much fuel should go in the p

3-4 releases a year sounds like there might be a solid QA cycle involved. e.g. I used to work on a webapp for flight planning: how much fuel should go in the plane's tanks, etc. It's not the sort of application that should be live-updated by the developers every 2 weeks. Maybe the mentor here has a clear view of the product lifecycles appropriate for this organization. I don't think we have enough information to decide who's right in any of the OP's situations.