4 ms·
"Way of work should be defined at a team level by its people, not by the company." - This is basically the origin of scrum. Essentially every problem ascribed
by _ea1k 3y ago
"Way of work should be defined at a team level by its people, not by the company." - This is basically the origin of scrum.
Essentially every problem ascribed to scrum is its departure from this origin story.
Scrum is about making each team work better, but somehow it turned into the same weird top-down imposed structure that it was supposed to replace. 2 week sprints are mandatory for all teams? They all have to start and stop on the same day? And you can use any story point system you want as long as they neatly summarize into these t-shirt sizes?
There is little resemblance between the agile manifesto and what people are pretending to do today.
- 0xdeadbeefbabe 3y agoMakes you wonder if the writers followed the manifesto writers manifesto or if they also strayed from the origin.
- unethical_ban 3y agoHa! At my old employer they used "Scaled Agile Framework" (SAFe). About a dozen teams of developers and operations people got together once a QUARTER to determine what big epics/objectives to complete, and then develop stories and estimates (points) for those stories and roughly which sprint they would fall into within the "iteration", as the quarter was called. Every team on the same sprint schedule. Fibbonaci story rankings across the org. Product owner and scrum master would be shared between several teams, IIRC. And of course, middle management observing the aggregate amount of work estimated vs. completed every "iteration".
- _ea1k 3y agoDon't forget to tag and label every story appropriately, use the corporate standard for sprint names, and file those tps reports on time. That would be great.
- belval 3y agoI feel like that's unfair. It's normal in a company to answer to someone and its normal for that someone to want some way to answer the question "are we on track for X" when asked by their superior (whoever that may be). The larger the company the more that statement becomes true because the number of interconnect for N employees is O(N^2). That does not excuse making the whole thing stupid and painful, but accountability is not an unreasonable request.
- _ea1k 3y agoOf course! The problem is that this "accountability" is the grease on the slippery slope towards doom. If I need every epic, story, task and subtask to be labelled in the correct way for your organization, then I no longer have an autonomous team that is able to self organize to maximize its own efficiency. If I don't have that, I no longer have agile. There are better ways than turning agile into a caricature of its former self.
- The_Colonel 3y agoThe quarter is called "increment". "Iteration" corresponds to sprint from Scrum. > About a dozen teams of developers and operations people got together The S is for "Scaled" for a reason. Yes, large & complex projects need planning on several levels and the timeframes are longer. Nothing surprising.
- _ea1k 3y agoWe all know that. There are even some good things in SaFe. Where it loses value is that it imposes those organization level planning ideas at too many levels and ultimately impedes the most effective teams.