3 ms·
>>For example, I'm afraid that in many environments, Agile ends up meaning "directionless or micro-directioned iterative development" Directionless. Absolutely
by enraged_camel 12y ago
>>For example, I'm afraid that in many environments, Agile ends up meaning "directionless or micro-directioned iterative development"
Directionless. Absolutely.
Before he retired, my uncle was the VP of Technology for a very well-known financial firm. He managed a large department of developers and IT folks across multiple countries.
We were talking about Agile vs. Waterfall once, and he said something that stuck with me: Agile works if and only if your developers have significant amounts of industry expertise. Because only then can they look at a set of vague requirements, make sense of them and translate them into solid product features using their experience and knowledge in that specific problem domain.
Whereas if you look at the software industry today, most developers specialize along languages and frameworks, rather than industry lines and problem domains. Resumes almost never say, "X years of experience in [industry]" because most companies say they want to hire developers with "X years of [insert language/framework here] experience."
So then they end up hiring developers who are really, really good at Rails/Angular/Java/C# or whatever, but have never solved problems in the company's industry because their last job was something totally unrelated. They know how to use the tools and they may be able to iterate quickly, but if they implemented the feature correctly in the first place they wouldn't need to iterate in the first place and the product would ship on time and be on budget.
- pinaceae 12y agothat's exactly why product managers exist. i run precisely such a team, because there are no devs out there that know enough about our vertical - and the time learning and keeping up to date would be prohibitive.
- kylequest 12y agoPMs can help only with one part (the "problem"), but, unless they are also good architects and designers, the end result and the process end up being pretty painful. The devs still need to learn about the domain and they need to understand it enough to build a good solution. Having to learn a new domain on your own can be tough. Having external SMEs (subject matter experts) reducing the ramp up time and answering detailed questions is a big help. It's pretty common for PMs not to be SMEs though...
- pinaceae 12y agoabsolutely agreed and yes, we go deep on designs. and yes, it is uncommon, makes hiring quite challenging.
- danieltillett 12y agoThis is so true. I am mediocre developer at best, but because of my domain knowledge I can solve problems that developers 100 times better than me can't. Sure my code might be rough around the edges and some of my designs lacking in elegance, but they work. Working code is a million times better than elegant code that doesn't. Edit. I have often thought that a good way to pair program would be to pair up a strong domain knowledge / weak dev with a weak domain / strong dev. I have had the opportunity to do this on occasion and the pace at which you churn out great working code is phenomenal.