3 ms·

I assume by 'traditional' industry you mean stuff like manufacturing, finance? If yes, then you should check out Six Sigma, Kanban etc. Those came from traditio

I assume by 'traditional' industry you mean stuff like manufacturing, finance? If yes, then you should check out Six Sigma, Kanban etc. Those came from traditional industry - manufacturing and applied to software engineering. Scrum and Agile evolved out of these methods. That said, you might think retrospectives work because of the method behind it. But in my opinion it works because of the intent and culture of the team. At a past employer we started Agile with bang. Our manager used a clock to ensure everyone spoke for 2 mins max. "Brevity is the Soul of Wit" he said. But once he left Agile meetings were in shambles. People rambled on about who they sent mail to, what meetings they had etc. because it showed "importance" of their work.

bb88 8y ago
> People rambled on about who they sent mail to, what meetings they had etc. because it showed "importance" of their work. Yeah, I ran into that more than once. Scrum turns into a daily performance evaluations which tends to encourage micromanagement. And this is something I don't get. Managers complain about getting too many emails that they have to read through, but yet they're fine with 5 minute status reports from every member on their 10 person team on a daily basis. Every company that I worked for that had retrospectives dropped them, as they were pretty much useless. Because once a team optimized internal processes, the thing they couldn't optimize was the external managemalaise that impeded their ability to get things out on time. And that never ever flowed upwards.