Hi,
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!
Thanks,
Philippe
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.