The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Using JIRA Portfolio for a non-Agile purpose

Emily Triyonis
Contributor
October 17, 2016

Does anyone who does not work in sprints or have 'releases' use JIRA Portfolio? Looking for pointers to get around the agile aspect of it for portfolio project management. Thanks!

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Walter Buggenhout
Community Champion
October 17, 2016

Hi Emily,

I want to avoid to go into a discussion of what might be 'Agile' or not, but focus on the more formal concept of releases and sprints. Something I have been doing on several occasions, is use a time based concept as releases. This may be useful in a consultancy or any other environment where you rather have time based milestones instead of numbered releases.

I still use the concept of FixVersions in JIRA, but use months or quarters to label them. Examples may be "2016 | October" or "2017Q4". It works perfectly fine for the same purpose as a release: planning for work you need to get done by a given moment in time.

I think you can see sprints apart from releases. They help you plan, focus and visualize work on a shorter timeline and can be very useful outside a development environment as well. And if you don't need them, you can choose to plan in Kanban mode in Portfolio as well.