Timeline for How to structure a software development team
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 21, 2013 at 9:11 | comment | added | Paul Fleming | @DeerHunter. Spin off question raised here. | |
| May 20, 2013 at 14:48 | comment | added | Deer Hunter | @flem - looks like it (line management for team leads) is subject for yet another question. | |
| May 20, 2013 at 14:46 | comment | added | Ben | We generally try to avoid people reporting to someone on their team where I am. Keeps a distinction between line management and leadership and helps keep retrospectives more honest I think. | |
| May 20, 2013 at 14:31 | comment | added | Paul Fleming | @DeerHunter Is it a good idea for a team lead to be a line manager? I.e. is Scrum master a line manager? | |
| May 20, 2013 at 14:30 | comment | added | Deer Hunter | @flem - team leads should be saved from paperwork, but not from managing their teams. | |
| May 20, 2013 at 14:21 | comment | added | Paul Fleming | Capacity is currently not a problem, and we can scale up to support more projects. The main problem (I think) is that we don't have enough leadership to manage the higher capacity. Should we have a full time manager "head of development" for all line management/HR duties, allowing team leads to focus on the project(s)? | |
| May 20, 2013 at 13:00 | history | answered | Todd A. Jacobs♦ | CC BY-SA 3.0 |