-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
What are the best techniques for teamwork (in an Android development team)?
- Thread starter Muva
- Start date
D
Deleted User
Guest
I assume you already have a source code repository.
And I would also recommend using a continuous build system, such as Bamboo. That way, whenever someone does a code commit, a build is started, and you know fairly soon if there are any code breakages.
Also put a priority on testing. Develop a suite of regression tests, which ideally can be run by the continuous build system.
You also need a good bug tracking system, which can link to your source code repository.
Fortunately Atlassian have figured all this out, and provide a comprehensive suite of development tools.
https://www.atlassian.com/
In terms of team management, I would just do the exact opposite of what was done at my previous company
Initiate some kind of development process. Planning and task break down is key. Have regular meet ups so that team members have visibility of what everyone's doing. Have regular bug reviews, and make sure the important ones get worked on. Do not let them pile up, or before long, you'll have a mountain of bugs.
Make it clear what the goals are. Set clear target dates, and monitor progress.
Keep in touch with your individual team members. Don't let people drift, with no purpose, or task. Be aware of what they're doing. Share out the work equally, don't let one person have the majority of the work. Individual engineers are useless at sharing what they're doing, because that reduces their importance. It's the team manager's responsibility to ensure work is equitably shared in the team.
This idea of a 'self managing team' to me doesn't work. You need an overseeing project manager, or team manager to do that job.
And I would also recommend using a continuous build system, such as Bamboo. That way, whenever someone does a code commit, a build is started, and you know fairly soon if there are any code breakages.
Also put a priority on testing. Develop a suite of regression tests, which ideally can be run by the continuous build system.
You also need a good bug tracking system, which can link to your source code repository.
Fortunately Atlassian have figured all this out, and provide a comprehensive suite of development tools.
https://www.atlassian.com/
In terms of team management, I would just do the exact opposite of what was done at my previous company
Initiate some kind of development process. Planning and task break down is key. Have regular meet ups so that team members have visibility of what everyone's doing. Have regular bug reviews, and make sure the important ones get worked on. Do not let them pile up, or before long, you'll have a mountain of bugs.Make it clear what the goals are. Set clear target dates, and monitor progress.
Keep in touch with your individual team members. Don't let people drift, with no purpose, or task. Be aware of what they're doing. Share out the work equally, don't let one person have the majority of the work. Individual engineers are useless at sharing what they're doing, because that reduces their importance. It's the team manager's responsibility to ensure work is equitably shared in the team.
This idea of a 'self managing team' to me doesn't work. You need an overseeing project manager, or team manager to do that job.
I assume you already have a source code repository.
And I would also recommend using a continuous build system, such as Bamboo. That way, whenever someone does a code commit, a build is started, and you know fairly soon if there are any code breakages.
Also put a priority on testing. Develop a suite of regression tests, which ideally can be run by the continuous build system.
You also need a good bug tracking system, which can link to your source code repository.
Fortunately Atlassian have figured all this out, and provide a comprehensive suite of development tools.
https://www.atlassian.com/
In terms of team management, I would just do the exact opposite of what was done at my previous company
Make it clear what the goals are. Set clear target dates, and monitor progress.
Keep in touch with your individual team members. Don't let people drift, with no purpose, or task. Be aware of what they're doing. Share out the work equally, don't let one person have the majority of the work. Individual engineers are useless at sharing what they're doing, because that reduces their importance. It's the team manager's responsibility to ensure work is equitably shared in the team.
This idea of a 'self managing team' to me doesn't work. You need an overseeing project manager, or team manager to do that job.
Thank you for this important information. I will be checking on the product.