|
|
|
|
|
|
by bcarroll22
2761 days ago
|
|
|
I gotcha. I guess the confusion from my end is that I’ve yet to have a software development job where I wasn’t developing a product. No one in the orgs I’ve been a part of refer to the “product” team as the “product development” team. It’s just the product team, and the development team. If that’s not been your experience then maybe you fall outside the target demographic of this article? I say that because it was super clear to me exactly what the author was talking about (in fact it even resonated with other members of my scrum team). Alternatively, I suppose my experience could be anecdotal and not what most development teams encounter daily and struggle with. |
|
|
If I go mentally back to when I was in a small startup, then I could kinda see how the article makes sense, because as a technical co-founder I also had (partial) freedom to imagine how the product should be, besides having to actually write code. But then all the "politics-related" aspects that the article mentions (the whole "us vs. them" thing) make less sense because in a small startup there isn't as much "politics" as in a larger corporate environment...
Maybe the article applies to a "later stage/larger startup" environment, which I have never experienced, and maybe that's why I find it confusing.
Edit: another thing that you said and makes a lot of sense, is that your dev work often involves creating a product, however in my experience (at least since I left the startup world and went into enterprise) most work has been about dealing with a lot of legacy stuff and developing new features here and there, very rarely having to develop a new product from scratch.