Hacker News new | past | comments | ask | show | jobs | submit login

Yeah, I'm in the middle of 3 projects right now using sprints as the base time unit.

One project is in Sprint #17 this week.

One is on Sprint #41 as of Wednesday.

One is on Sprint #56 as of this Friday. On top of that, the weekly meeting is set at 4:30pm on Fridays in my time zone. The sprint planning meetings typically go 2 hours.

Each project has a daily stand-up too, each lasting about 30-45 minutes. I get about 3 hours a week total to actually code.

Yes, this has effectivly killed the entire idea behind a sprint and agile in general, we all know, it's super obvious. But the company is now an 'agile' company as of ~2.5 years ago, so we can say so in the job apps. All the interviewing devs know to ask about how long the stand-up is, we tell them the truth, and the job apps stay open when they decline our offers (we also pay under market rates). Our copies of 'The Phoenix Project" remain in shrinkwrap.




This problem has nothing to do with Jira or agile, but with bad management.


No. Problem is with jira and agile.

Majority of managers will always be mediocre. But previously, managers without tool just let the developers do the job. Nowdays, mediocre managers have industry standard tool to make everyone life terrible and destroy the product by accumulating bad decisions founded on jira/agile metrics.

Also, jira and agile gives management ability to be extremely shorter oriented in their reasoning - that is major factor changing dynamic in the team.


Again. The problem is with management.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: