Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,799
Community Members
 
Community Events
176
Community Groups

Best practise question: how do you associate teams in large projects?

Edited

Example: I have so set up a plan für several year, 12 main epics wigh a total of 280 stories underneath. Not all the programmers are totally interchangeable so not everybody can pick any task from any epic.

Would you create multiple teams and associate them to the epics (issue source)? In case one team finishes ealrlier with the tasks in this epic, would they be assigned to any other issue (inside the plan but outside the original issue source) by the autoscheduler or would they have some free time?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events