Remix clone Hacker News

Agile is like communism. Lots of people like to hang external ideas to it. Some valid, some not.

Points, t-shirt sizes, figmas, etc... these are _tools_ and _processes_. Why the hell are you complaining about it when it says very clearly that you should focus on people and interactions?

▲

bluGill 8 hours ago | parent | next [-]

Because I have real problems. People and interactions as a focus shows me where those problems are, and now I need solutions to solve them. Those tools and processes that agile often uses are the type of things I need to make my people and interactions work. (or at least that is their promise) I should not be developing my own tools when someone else already has some that works.

▲

ryandvm 8 hours ago | parent | prev [-]

Oh, well if Agile is just a vibe then count me in.

▲

skeeter2020 8 hours ago | parent [-]

it's more than a vibe, the challenge is it's "Here's a bunch of things that can help; pick and use what works but don't be dogmatic about it". This is impossible to scale, as by definition it's anti-scale, which is why companies run into massive problems and pervert agile into whatever they have now.

▲

alganet 8 hours ago | parent [-]

If that's the problem, then it's easy.

Do not think about the tools. Think about small improvements that can move the team in a more productive and sustainable (agile) way.

Simple things. Like putting a timer on long meetings until people get used to not extending it. Or putting a limit on the work pipeline between the developer and the tester to avoid overwhelming testing sessions.

In my opinion, you are not supposed to start from scratch. The chaos often comes from this "let's blank slate everything and adopt all agile things we can find". Once again, the same mistake of focusing on tools instead of interactions between people.

C'mon, it's not that hard. Doesn't need to have strict rules.

▲

bluGill 8 hours ago | parent [-]

> Think about small improvements that can move the team

Which team? My team of 5 people or the entire project of several hundred? Focusing on the small teams finds a lot of local maximums that are very bad for the entire project. Many of the small changes small teams want to make are not possible because they would impact some of those several hundred other developers. Often small pain for us is much better than the pain our change would force on those others.

	▲	alganet 7 hours ago \| parent [-]
		By team I mean "the people you interact with [the most]". Those who impact your routine and are impacted by you most directly. As I mentioned before, there is no one size fits all recipe. And there are no multiple recipes of different sizes. There are infinite variables a group of people can express. There is no point in making recipes, agile is about ideals.