25 ms·
Those sound exactly like the things any team would do on a new project, regardless of calling it Agile, Scrum, Kanban, or whatever. I just don't see any differ
by khazhoux 3y ago
Those sound exactly like the things any team would do on a new project, regardless of calling it Agile, Scrum, Kanban, or whatever.
I just don't see any difference between this and just having the philosophy: "Do first things first; do the next most important things next; don't bite off giant chunks but instead break them up."
- crazygringo 3y agoBecause lots of teams don't break things up. They do give giant chunks to each person, not check in, and then magically expect them all to integrate on the end and on time. This is precisely the common/naive practice that Agile/Scrum/Kanban/etc. is specifically reacting to.
- SkyPuncher 3y agoYep. This is exactly my experience. You don't need to get crazy about things, but having the defined time periods forces people to actually think about how they're going to deliver things.
- Cthulhu_ 3y agoIt's that a lot of people don't have (didn't have?) this philosophy. My previous employer worked in telecom; it wasn't uncommon to have one major feature be under development by one or two guys for eight months at a time. It was specialist work, sure, and the guys knew what they were doing (20-40 years in the business) but then integrating and releasing it was a big job.