3 ms·
At every single company I've worked at an Agile-like approach was used. This meant that the daily catch-up is called a Scrum, and that instead of working in a W
by EnderMB 12y ago
At every single company I've worked at an Agile-like approach was used. This meant that the daily catch-up is called a Scrum, and that instead of working in a Waterfall approach we've created sprints of however long was needed to fit a bunch of tasks in. Also, instead of writing large spec documents that are signed off and given to a developer to implement we create a smaller spreadsheet of deliverables, and later changes are introduced into later sprints.
Naturally, things tend to fall apart when the spec isn't accurate, or when an estimate is off. In a client-facing business like an agency these approaches often fall apart when the client isn't getting something when they want it.
I've interviewed at a number of large agencies and it all seems to be the same. Everyone does Agile...kinda. They have the general feeling down, but they all skip some parts to make it usable for their clients.
This brings me to ask, does anyone REALLY do it properly in an agency setting? If you do it properly in a client-facing industry will it fall apart, or are people just too lazy to fully embrace Agile? I'm yet to hear of anyone doing it well, but I would love to hear from someone that knows how to do it well in a team of 15-20 people containing developers and Project Managers.