r/agile

Been working with agile for few years now as data analyst and something always confused me. Everyone thinks agile means doing everything super quick but actually its opposite

The tough part is making yourself go slower when everything in you wants to rush. Like spending proper time on user stories instead of throwing them in sprint last minute. Or actually listening in daily standups when people mention problems instead of just going through motions. In retrospectives we used to just say "yeah that sucked, next sprint will be better" but now we dig deeper into root causes

Weird thing is whenever our team tried to speed everything up we got slower results. More bugs, people got frustrated, had to redo stuff constantly. But when we started taking time to do things right first time, suddenly we were delivering better quality faster

Think agile isn't really about velocity at all, its more about finding good flow that works for long term. Took couple failed projects for me to understand this but now it makes sense

Most of the time when we work agile, we like to count story points as "progress". To me this does not make sense.

First of all, complexity, to me, does not reflect actual work hours. Furthermore, more senior people will require less time for complex tasks but for less complex tasks, it might be the same amount of work.

I always perceive it as a mix up and was wondering how you track progress?

I asked my manager to explain our client onboarding process and got this “First we send the doc, then depending on what they choose we either go into setup or strategy, unless they need revisions, then we loop back, but only sometimes.”

????

So I tried to write it down step by step and realized there are decision points everywhere, some steps repeat, some things only happen if conditions are met

Basically impossible to explain in text without it sounding confusing.

Then I tried explaining it to a new hire and they were even more confused.

I feel like this is something that NEEDS to be visual (like arrows, branches, decisions), not paragraphs.

How do companies actually map processes like this in a way that makes sense, would really appreciate advice

We are seeking a skilled full-stack developer to join our team for ongoing web and mobile app development projects. The ideal candidate should have a strong background in both front-end and back-end technologies, as well as experience in creating responsive designs. You will work closely with our design team to deliver high-quality user experiences and efficient functionality across platforms. If you are passionate about coding and enjoy solving complex problems, we would love to hear from you