3 ms·
We follow the canonical agile, or we think we do. Backlog grooming->Sprint planning->Standups->Retros->Backlog grooming. What else is missing in this process? S
by propernun 1y ago
We follow the canonical agile, or we think we do. Backlog grooming->Sprint planning->Standups->Retros->Backlog grooming. What else is missing in this process? Seems like this problem of engineers not updating their tasks is very unique to my team maybe? Could this be solved by process, or incentives, or tools?
- solardev 1y agoCanonical and capital-A Agile never, ever works in my (admittedly limited) experience. Part of the original Agile philosophy was "people over process", but when you get overly dogmatic about it and hire consultants etc. and try to enforce every little ceremony, those thoughtful guidelines then become corrupted into a useless bureaucracy that prioritizes process above all else, even when the process is no longer working or serving the team. Forget the official methodology, talk to your team and tell them you realize the process isn't working and ask them what would be a good way to give the stakeholders the updates they need without imposing undue work on the ICs. Sometimes a simple and well-tolerated kanban that people update as needed is more effective than rigid daily rituals hated by everyone.