How a large program would work in an agile and non agile way (i.e. waterfall) using JIRA?


I need to give a demo of JIRA server on a server hosted by our company.

The thing is that we would like to know in advance how a large program would work in an agile and non agile way (for instance using waterfall) using JIRA? Does JIRA support hybrid ways of working? How is best way to achieve this leveraging the Out-of-The-Box project configuration?

We are using JIRA v6.4.12 and JIRA Agile v6.7.11.

Look forward to your feedback.



1 answer

JIRA is configurable in such a way that it will support the purist Waterfall or Agile approaches, but in reality most organisations use a hybrid of Waterfall and Agile. 

JIRA as of V7 comes with a number of useful project templates that will provide you with out of the box configurations that match different methodologies. Do not be scared of changing these to meet your specific organisations particular requirements as that is part of the strength of JIRA.

You might to look at the site for a more indepth approach to how Agile in JIRA works. 

That's good but we are not planning to upgrade to V7 in the near future.

So we have to follow the best approach using the current version of the tool we have installed.

Many of the principles are unchanged and indeed V7 really just automates a lot of what can already be done in the earlier version. 

Our preference would be as little configuration as possible....maybe another option could be to have one project instance based on Scrum configuration and another instance based on a more traditional configuration (maybe by selecting the "Project Management" configuration?).

So, a project would have two project instances setup in the JIRA supporting Agile and the other one supporting Waterfall...That way, a project team would use one or another project instance, depending on the nature of the work to be performed without having to customize the tool...

Any other suggestions or experiences in hybrid project teams are very welcome.

I would try not to split the project in two as it will make reporting on a single client more complex. You can always base a Scrum (or Kanban) board off a filter rather than a whole project and that then means you retain the full project context but can work on whichever parts you need to in an Agile approach. The spilt could be on issuetype or even a customfield to determine which methodology is in place.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

239 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you