44 ms·
Good luck achieving your sprint deliverable when all you have is some ideas! That's one of my main misgivings about a hard-line agile approach. It is good for
by astrodust 14y ago
Good luck achieving your sprint deliverable when all you have is some ideas!
That's one of my main misgivings about a hard-line agile approach. It is good for shops focused on engineering simple problems or doing routine technical work. It breaks down completely in more research-driven domains.
The hard problems are the ones where you bang your head against the wall with no tangible progress, simply exploring the problem domain until you can get some traction, find a way to solve it, but often your first few attempts lead to a sub-optimal solution you'd hate to commit to.
Agile says go with it, fix it later. This is why we get stuck with crappy standards we'd all want to go back in time to fix.
Some things require a more artistic approach where you grind away at the thing until it's actually solid.
If Haskell is pure mathematics then there's no way you can shoehorn that into an agile box.
- binspace 14y agoActually, agile methodologies are good for situations where the problem itself (and even customer base) is in flux and not fully known (ie consumer facing web startups). Agile methodologies help lay a roadmap to facilitate communication and prioritization to/from developer, project management, and the customer(s). The solution may or may not be difficult, but finding the right problem to solve is paramount. The quality of the solution is often a product of the quality of the people working on the problem. Oh, and don't run out of money :-)
- astrodust 14y agoMy experience is there's a tendency to ship the first viable thing that comes out and deal with the rest on an as-needed basis. This is fine for stuff that can survive being a bit ramshackle at first if you can refactor it later, but some things are highly resistant to later refactoring.
- binspace 14y agoShipping quickly is often a strategy used to discover the problem space. Some things should be done as quickly as possible and some things should not. The developers/tech management are responsible for forseeing such cases. Hopefully the initial developers are good ones. If not, I'm sorry and I hope they pay you well. I've been there :-|
- Drbble 14y agoCheck out Gall's Law, which I just learned about on HN. Big solutions come from iteration, not ejaculation.