3 ms·
The thing that doesn't work for me in Agile: being treated like a baby and spoon fed little bits of work with little room for responsibility, initiative, creati
by pacala 14y ago
The thing that doesn't work for me in Agile: being treated like a baby and spoon fed little bits of work with little room for responsibility, initiative, creativity and a personal touch. Agile is great if you are a mediocre manager and you want to run a place full of replaceable cogs, but not so great if you want a place that pushes the boundaries and consistently goes the extra mile
- mindcrime 14y agoThe thing that doesn't work for me in Agile: being treated like a baby and spoon fed little bits of work with little room for responsibility, initiative, creativity and a personal touch. Agile doesn't prevent any of those things. Actually, "agile" doesn't "do" anything, since "agile" is just an adjective that describes a set of values that a number of development methodologies have in common.
- njharman 14y agoYou describe the opposite of Agile. Agile is all about ownership, responsibility, self-direction. It, (at least scrum) gives way more control to "producers" (devs, designers, etc) than "managers". But, of course (almost) no one does scrum cause sales/customers want up front signed contract listing exactly what will be done and exactly when.
- jschuur 14y agoTo a certain extent, agile tries to narrow the scope of a sprint, in order to ship more rapidly. For people that have a grander vision of what they want to build this may seem narrowing to constantly be reminded of the MVP. If the product you're creating is a commercial thing, or just something that will thrive based on its adoption in the marketplace, feature creep can be damaging, and it's helpful to have someone keep you focused on making that next shippable version. That's inevitably going to piss some people off who are bubbling with ideas and want to implement them all. As a product manager with an active imagination, I've been in that situation, and I'm slowly recovering :)
- pacala 14y agoAgile A play in 3 sprints Characters A: rockstar developer B: developer C: intern ===== Sprint 1 ====== A: To a certain extent B: agile tries to narrow A: the scope of a sprint A: in order to ship more rapidly B: For people that have a grander vision B: of what they want to build ===== Curtains, ship iteration 1 ===== ===== Sprint 2 ====== A: this may seem narrowing A: To be constantly reminded of the MVP. A: If the product you're creating is a commercial thing B: or just something that will thrive A: based on its adoption in the marketplace B: feature creep can be damaging ===== Curtains, ship iteration 2 ===== ===== Sprint 3 ====== A: and it's helpful to have someone to keep you focused A: on making that next shippable version B: That's inevitably going to piss some people off C: who are bubbling with ideas A: and want to implement them all. C: As a produce manager with an active imagination A: I've been in that situation B: and I'm slowly recovering Chorus: :) ===== Curtains, ship iteration 3, move on to the next project =====
- Goronmon 14y agoThe thing that doesn't work for me in Agile: being treated like a baby and spoon fed little bits of work with little room for responsibility, initiative, creativity and a personal touch. For the "agile" teams I've worked on, the developers have had the most input as to the breakdown of tasks compared to anyone else. So, no one was "spoon-feeding" me work. I would see what the goal of a feature would be and the team would discuss the best way to break that feature up so that work could be done.