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,556,693
Community Members
 
Community Events
184
Community Groups

how to organize my developers team?

i have 3 members ( Android - Iphone - Web Developer ), all of them work in the same project.

My Question : Better than to make each one of them with its own project or make them in the same  project in jira  ? 

1 comment

Aiden Marriott
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 08, 2021

Depends on what you are trying to achieve.... if it is one team working on delivering the same product (even with different platforms) - I would say 1 project and multiple components and/or releases.  

Thanks for your reply 

But team will work in parrellel in the same stories 

how can i assign the same stories to the three members in the same time ?

Aiden Marriott
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 08, 2021

Probably best practice would be to break the stories down further so that they are more specific and can be assigned to an individual.  If that is not what you want - I would suggest creating 3 sub-tasks per story to represent each individuals element.

in the first solution , stories are the same to all members, no need to break them, i think if i make that, i will dublicate the stories three times. 

The second solution: i think no accurate reports for the subtasks of all stories in sprints, and may be to make confusing between the actual subtasks of each story and the dividing way to organize the team ( Android - Web - iphone )

Comment

Log in or Sign up to comment