|
comedyblissoption posted:Some of the things under the umbrella of Agile make sense and if you take the religious parts out they are good ideas without the Agile kool-aid. The problem is to implement those ideas you basically need buy-in from everybody in the business and sometimes the customer. Agile methodologies actually make a ton of sense if you get down to the core of what they're saying. Kanban, Six Sigma, Scrum, whatever are all about identifying where the company is loving up and fixing the problems. The issue is that most business people's actual job description is "blame failures on other people, take credit for successes" which goes completely against the core of these methodologies and they end up loving it all up.
|
#
¿
Sep 30, 2015 18:09
|
|
|
|
| # ¿ May 10, 2024 07:56 |
|
|
Ithaqua posted:I'm passingly familiar with SAFe. It seems insane to me but some of my colleagues are big fans. SAFe is actually pretty nice. That diagram's actually supposed to be an interactive piece where you click on something and it goes into more detail. This (http://www.scaledagileframework.com/budgets/) is what you get when you click on the pie chart. It talks about some of the pitfalls with project based budgeting and describes alternatives. It's not as specific as it looks like it might be, it's more about providing a complete architecture for the company rather than having the dev team on agile but everyone else around them is working differently. I don't work at a company that follows it but I've heard of companies doing well with it.
|
|
#
¿
Oct 1, 2015 05:56
|
|
|
That's not actually kanban. Kanban is about inventory management. If you had a supply of parts in a manufacturing plant, then there'd be a "parts" card in the manufacturing lane. When you run out, you move that card to supply (because it's out), supply moves a new bin (with a card) to manufacturing and sends the empty part bin (with the card) to the supplier lane. When the supplier gets the parts to storage then storage gets the card. The point is that you can have only two "parts" cards that stay in the system, reducing held inventory and still making it obvious when things are going slow. The software design concept just takes the board and does some unrelated stuff with it.
|
|
#
¿
Oct 2, 2015 04:04
|
|