4 ms·
Agile can only work if every part of the organization is agile. HR too slow? Can't be agile. Upper management obsessed with numbers and reports? Can't be agile
by johncoltrane 9y ago
Agile can only work if every part of the organization is agile.
HR too slow? Can't be agile. Upper management obsessed with numbers and reports? Can't be agile. Hard to recruit new people? Can't be agile. IT department incapable of creating accounts and prepping laptops in less than a week? Can't be agile. Ever-shifting requirements because we are "Agile", aren't we? Can't be agile. Client insists on a deadline? Can't be agile. Hard dependency on non-agile third parties? Can't be agile. Unstable teams? Can't be agile. Etc.
- amirmm 9y agoLet me make myself clear, I agree Agile is not useful for all environments. Just need some example of cases that it has not been useful and reasons for that. If I get you right, you mean any team that is too slow cannot be agile. I disagree, transparency in agile is useful to find the issues and retrospective meeting can be used to fix the issues. Thinking out of the box, I can say a business analyst can help with improving the process and making it more efficient. To bring the slowness problem to the surface, I would use a Kanban board to make everything transparent and figure out what the problem is, and hire a business analyst to review the process and find the bottlenecks. Also, I had experience of working in a agile (scrum) team while our client (whom sent the requirements) was following waterfall. Would you elaborate further? Cannot we wait for the other team to finish it work and then use Agile to develop what is required? Or if something is going to be delayed cannot we remove that from the current Sprint and move a ready item to the current Sprint while waiting for the other team? In addition to above, which other approaches did you use to develop software applications when Agile did not work? and which approach would you use if you were in our situation?
- johncoltrane 9y ago> If I get you right, you mean any team that is too slow cannot be agile. No, I meant that agility is what you get when you got rid of every impediment. Sadly, a small team working on building a product or delivering a set of features can be as agile as they want but they _will_ face impediments that they have no power over, no matter how much introspection they do. Sadly I have no solution for this.