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
We are a small team (<10) but we have to manage very different projects/products that are not related.
So we could have repositories with identical names in different projects, but again they are specific to each project. And support of legacy products avoid to make too many change.
Developers could switch from one project to another.
I tried to manage using group but it's became quickly an horrible nightmare.
So I imagine managing a team by product or product range.
I see the main benefits;
I see also some drawbacks;
Please let me know your experiences about teams management and the solutions you define.
Any helpful comment will be very welcome!