You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello - we are working to use Jira across multiple projects with several cross functional teams - several questions are coming up
1. What is the purpose of the releases - are they required, I think the answer is yes, but what is the nuance, ie could we use them as time box/sprints, 1 per month, or are they better to be used for specific epic projects with many smaller projects that have a fixed date, ie the evacuation of a data center?
2. When working with the various teams, does it matter if they are setup for scrum vs Kanban - and if so, can you expain those nuances further -
A release is used to group a collection of issues that is usually mapped to a specific version of the the product associated with the project you're working on.
It is not essential to use releases. For time boxing you should ideally configure a scrum team board for your project and use it to create sprints. These will then be included in your Portfolio plan when you include that project and team in your issue sources.
When using multiple teams in a plan the main nuance is that you can only use Kanban teams when estimating in time (hours or days) as you cannot use story point estimation in plans that feature Kanban teams.
I hope this helps,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.