What Is the Just-Right Agile Team Size?

[@DerekMahlitz]

I agree with small teams, I've seen success on them. It can go against company culture as smaller teams means more SM & PO, and other supportive structures.

[@MountainGoatSoftware]

If cost is at the forefront of the conversation I think that the data shows that smaller teams are more productive and have lower overhead costs even with the added cost of more SMs and POs in the company.

[@rajeswarikv9396]

Even though agile is a team work/colloborative effort, How can we calculate individual productivity in agile (scrum , Kanban)? Can the team members enter daily hours (this also may not be accurate as team colloborative efforts also will be included)..Don't want to take story points for measure here as it's relative and won't be accurate

[@MountainGoatSoftware]

I wouldn't suggest tracking individual productivity. I just don't see much of a benefit in that. I do, however, see benefit in empowering a team enough to self-organize and decide how much they will be able to reliably get done. Then use those estimates as data for future estimates farther out than a sprint or two.

[@rajeswarikv9396]

@@MountainGoatSoftware Is there a way to measure self organising ability ?

[@mikewcohn2]

@@rajeswarikv9396 No.

[@rajeswarikv9396]

@@MountainGoatSoftware What if a team does not have a sprint goal in one or two sprints? Like there are many defects,technical debts and each one picked each item and no common sprint goal? Still do they need to colloborate even for defect fixes and debts fixing?Is it still a shared effort? And wat to show in sprint review in this case?Kindly clarify

[@MountainGoatSoftware]

@@rajeswarikv9396 I have a set of videos about sprint goals, please start with this kzbin.info/www/bejne/emnSiKh4eNpnrZI