Here I thought Scrum was ridiculous. Then along comes kanban.
I'm an enthusiastic student of methodologies, consider Deming and Drucker are patron saints, and look for "one way flow" and "eliminate waste" (muda) opportunities everywhere.
I've now been on 4 scrum teams. I've been thru "master scrum training" three times. I have no idea what they're talking about. As far as I can tell, the Scrum methodology means talking about what "scrum" means. (Another possibility is that "scrum" is easier to say than "we have no idea what we're doing".)
See, I'm a GANTT chart, critical path, front load as much as possible, and iterate madly kinda guy. Worked great all the times I was in charge.
My current team is doing kanban. We have post-it notes that we move around. I have no idea what they represent. Chunking work like this is unnatural. There's really no way to infer the whole (work in the large, get a birds eye view) from the kanban project management artifacts.
I don't see how scrum or kanban relate to QA and testing. I've asked. (I used to be a QA manager, not very good, but I understood the work.) There's just arm waving "magic goes here" between the incompatible acceptable testing ("when are you done?") and the artificial sprint deadlines.
We also duplicate the kanban items in a bug tracking system. Ignoring the failings of Jira for a moment, I fail to see how how any mediated process can be "agile".
I could go on and on.
I'm an enthusiastic student of methodologies, consider Deming and Drucker are patron saints, and look for "one way flow" and "eliminate waste" (muda) opportunities everywhere.
I've now been on 4 scrum teams. I've been thru "master scrum training" three times. I have no idea what they're talking about. As far as I can tell, the Scrum methodology means talking about what "scrum" means. (Another possibility is that "scrum" is easier to say than "we have no idea what we're doing".)
See, I'm a GANTT chart, critical path, front load as much as possible, and iterate madly kinda guy. Worked great all the times I was in charge.
My current team is doing kanban. We have post-it notes that we move around. I have no idea what they represent. Chunking work like this is unnatural. There's really no way to infer the whole (work in the large, get a birds eye view) from the kanban project management artifacts.
I don't see how scrum or kanban relate to QA and testing. I've asked. (I used to be a QA manager, not very good, but I understood the work.) There's just arm waving "magic goes here" between the incompatible acceptable testing ("when are you done?") and the artificial sprint deadlines.
We also duplicate the kanban items in a bug tracking system. Ignoring the failings of Jira for a moment, I fail to see how how any mediated process can be "agile".
I could go on and on.