[rvdginste]

I don’t understand your comment: if you develop software as a team, it seems important to communicate and to know what the others in your team are working on?

Also, I really don’t see it as ‘social’ meeting, to me it’s a focused technical meeting about the work that is going on.

[Desafinado]

Yes to communicating with each other and knowing what you're working on, no to doing it every morning. Once a week, every two weeks, or once a month is fine. Any integral communication that can't be handled by the recurring meeting, can be handled ad-hoc as you go.

But people who have only done capital A agile and scrum are so buried in the philosophy that they don't understand that there are far better ways to do things.

[rerdavies]

I'm not sure how that's supposed works if most team members are burning through 14 tasks or 10 tasks or 5 tasks in a two week period. If your tasks are two week chunks, then you're doing something else completely different.

Over a 40 year career I've done all kinds of methodologies. If you understand that there are far better ways to do things, I'm all ears.

The big advantage to agile/scrum methodologies in my opinion: dramatically improved predictability. Total elimination of drama. Efficient management of expectations outside of the development group. Never having to do a death march ever again.

[rvdginste]

Ok, I agree, if there is enough (ad-hoc) communication within the team, you don’t need those meetings every day.