Last updated on
Plutora Blog - Release Management

Monthly vs Quarterly Release Cycles

Reading time 3 minutes

A common question we get asked is how often should we set our regular release cycle, in other words what should be our release frequency in our overall release strategy. Monthly vs Quarterly Release Cycles?

Release cycle frequency is a highly contentious issue in larger organisations because of the even balance between the pros and cons of each. Generally to understand what is best suited to your portfolio or greater organisation some simple questions need to be asked.

1: How much high priority change is your business asking for and how comprehensive is the change?

2: How good is your delivery methodology at ‘delivering’ and is your Production Change Management process lean, robust & repeatable?

3: How complex in terms of integration and system knowledge is your IT landscape?

Once you have answers to these questions you will immediately see the what is most likely going to work. Explaining to business stakeholders that they can have a monthly or quarterly release is easy when you can show the level of change requested and the risk to the production systems if the release is unfinished or untested. Establishing monthly releases for a smaller system which doesn’t have a large change program associated to it might mean that agility monthly releases provides is a good release cycle strategy.

For completeness we have listed are a few pro’s and con’s of them:

Monthly Release cycles


  • Your IT Delivery team/s are a well-oiled machine. A lean robust process needs to be in place and a pertinent automated regression test suite needs to be place.
  • Usually reserved for organisations who have been practising Agile, Scrum or Kanban development methodologies and achieve target dates.
  • System/applications releases are not dependent on other
  • Level of system integration complexity in your IT portfolio is not high.


  • High risk of failed releases due to shorter time frame to remediate defects
  • Level of regression testing may not be as comprehensive
  • Burn of IT delivery resources in particularly Devs and Testers

Quarterly Release Cycles


  • IT and Business users have a longer time to perform testing activities such as performance testing and UAT.
  • Detailed Planning can forecast efficiently the roadmap and provide various IT Planning options to business leaders around resource availability for release delivery. i.e. Projects and Programs can be delivered using BAU resources


  • The business have to wait more than 3 months for change to be implemented. (over 3 months because of the lead up time to prioritise features for a release)
  • Slow
  • Perceived lack of agility by business stakeholders and end users.
  • More resources typically required in monthly releases due to the planning, execution and production deployment processes.