Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@Torbuntu I don't think it's agile problem. As @D--M said, it's bad management and/or client. I've worked on a few agile projects and it was actually a very good experience. If there are any stoppers your scrum master should sort it out with the client and push him to make a decision. And working agile shouldn't mean that you don't have any information. There should still be project analysis and stuff. And the client shouldn't be allowed to change core stuff.
Agile is stupid.
You’re trying to build an application based on data that doesn’t exist yet, and that changes weekly; surely it makes more sense for the API to be built and in place before someone tries to create a front end?
The client decides they want an extra feature 1/2 way through which changes the way it should work yet again.
What you end up with is some rigid and poorly structured architecture, that might work - but how you have no time to refactor it to make it good, an account manager that doesn’t understand what the problem is, and a team of developers wondering wtf you were thinking when you wrote this pos
rant