I want to know best practices to manage water fall project in JIRA Agile. In our scenario some of the projects are being managed using waterfall methodology where development team concludes their development cycle and testing team start testing cycle. Once dev cycle concludes, Dev moves on to the next Dev iteration whereas Testing team is testing the dev cycle1. I would like to know your valuable guideline to manage this in a best possible way.
Are there specific elements of JIRA Agile that you want to use? In my opinion a lot of companies use JIRA Agile (or simply "do scrum") and still end up doing a lot of things the waterfall way, so I think it is good that you recognize that you are doing things waterfall. But then the question rises: why do you want to use JIRA Agile?
I agree with Geert here, although I'd phrase it slightly differently - Instead of looking at Jira Agile and asking for "best practices for Agile although we're not Agile", it would be better to look at your process first. It's not a case of using Agile because you can, I think you need to think about what you need from your users, and what you can do to help them, and if Agile has some functions that you *might* find useful, use them. I can't really give you much in the way of "best practices" because I simply don't know your processes. From what you have said, I'd use versions to represent cycles, build a workflow that has both Dev and Test phases in it (and I note you say "iteration", which implies you're already moving away from waterfall anyway), and then maybe use a Kanban board for a quick overview and prioritisation.
@Geert Graat For some of the projects we are using scrum approach and for some not. Nature of the project varies from one to another like purely waterfall, iterative or you may call them hybrid. All I want to ask that for waterfall should i create any other type of project while creating a new project so that dev and test teams can use them accordingly like dev teams are always in n+1 cycle and test team cycle is n . dev to move on to the next iteration whereas test team will test the dev n-1 iteration. this is the idea. In Agile I can not run parallel sprint since this feature is in the development lab (correct me if i am wrong). @Nic Brough All I want is to create a project that allows me to define two cycles at one given time in which dev will always be one step ahead to the test team. also is it it possible that something like this can be done in Kanban that dev moves to next iteration, do not close it and proceed to the next cycle whereas test team stick to the old cycle and keep testing ?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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