Calgarypuck Forums - The Unofficial Calgary Flames Fan Community - View Single Post

photon · 05-19-2020, 05:10 PM

I've never been on a team where we adhered strictly to any specific methodology.

Process for the sake of process is doomed to fail IMO.

Every team I've been on has tried to pick aspects of Scrum (or agile or whatever) that served the needs of the team and ignored the rest.

I think part of that comes from the rest of the organization lacking a commitment to being agile. I.e. management just wanting to hear that feature X will be delivered by date Y despite not having the information available to actually know that, which results in a pesudo-waterfall-from-experience guess about if something is doable by date X.

But I've been on teams where a sprint just didn't make much sense, and we just worked from a Kanban instead. Standups seemed to be pretty common regardless. I think too many teams ignore retrospectives so don't improve over time and get stuck.

One team that was probably the most adhering to it I was on it seemed more time was spent on the methodology than was spent on actual work; it felt like I had maybe 2 or 3 days in a 2 week sprint to actually do any work.

I get that structure is needed, but process should serve me, not the other way around. Find what helps.

Except retrospectives, always do those

05-19-2020, 05:10 PM	#2
photon The new goggles also do nothing. Join Date: Oct 2001 Location: Calgary Exp:	I've never been on a team where we adhered strictly to any specific methodology. Process for the sake of process is doomed to fail IMO. Every team I've been on has tried to pick aspects of Scrum (or agile or whatever) that served the needs of the team and ignored the rest. I think part of that comes from the rest of the organization lacking a commitment to being agile. I.e. management just wanting to hear that feature X will be delivered by date Y despite not having the information available to actually know that, which results in a pesudo-waterfall-from-experience guess about if something is doable by date X. But I've been on teams where a sprint just didn't make much sense, and we just worked from a Kanban instead. Standups seemed to be pretty common regardless. I think too many teams ignore retrospectives so don't improve over time and get stuck. One team that was probably the most adhering to it I was on it seemed more time was spent on the methodology than was spent on actual work; it felt like I had maybe 2 or 3 days in a 2 week sprint to actually do any work. I get that structure is needed, but process should serve me, not the other way around. Find what helps. Except retrospectives, always do those __________________ Uncertainty is an uncomfortable position. But certainty is an absurd one.