Hello and welcome to the technology podcast series by ThoughtWorks.

Joining us today, we have Sri Ram Narayan, principal consultant for ThoughtWorks Technologies.

Hello, Sri Ram. Welcome to the show.

Thank you, Gotham.

You mentioned that you'd be talking about anti-patterns of agile software development.

So what do you mean by anti-patterns?

That's just a jargon for saying it's a common mistake.

We are used to coming up with best practices for everything.

But it's sometimes also useful to identify common mistakes so that we can watch out for them in future.

Okay. Well, why not focus on the right way of doing things instead of looking at the

mistakes? It's just a different way of slicing the situation. Agile software development methods

aren't prescriptive by nature and that is a good thing. But that also means that there is a lot

of room for interpretation

and you often have the unfortunate side effect of misconceptions.

So I think it's useful to call out these misconceptions that I have experienced

and explain why it is so.

And hopefully through the course of explanation,

the right way of doing things become somewhat self-evident.

So can you quickly summarize the anti-patterns you're going to talk about today?

I'm going to talk about when Agile estimation becomes pointless, labeling people instead of

activities, cost ineffective pair programming, and how to do XYZ in Agile.

Let's talk about estimation.

...