Talk:Team Practices Group/Proposal for formation

I think this is a great proposal! There are two small suggestions that I would like to make:

1) What do you think should the role of the ACO be regarding thought leadership around tools?

2) Maybe it's worth mentioning and explaining some other agile methodologies like Kanban which is more suited for DevOps work.

Looking very much forward to see this come to realization! Drdee (talk) 00:09, 1 March 2014 (UTC)

Need
Do we really need a dedicated team for this?

The way I see it, different teams have needed different amounts of advice-giving - from my perspective I've taken up maybe 30 minutes of User:awjrichards's time, if that. And now that we've had advice from him on the subject, we're good. We're self-sufficient with respect to agile and scrum and others. And I imagine most teams will have that experience - the problem has been that loads of teams are just starting up now. Once they're settled, and there are teams busy working on things, probably the need for training will dwindle. I imagine it already is.

Even if there are more teams formed, maybe they won't want to be trained. Maybe they'll pick things up on their own. Maybe they'll come up with their own system.

And even if none of that happens, I cannot see this taking three people. That seems just...totally unnecessary. I see you have them acting as scrummasters as well, but people within the team will almost certainly do a better job of knowing what's happening around them, and even if not, the amount of work surrounding scrummastering should either not be that great or should be reduced by fixing the crappy software we use instead of throwing resources at the problem.

That's all. --MarkTraceur (talk) 00:25, 4 March 2014 (UTC)