|
|
|
|
|
by mastazi
2764 days ago
|
|
the problem (as I said in my other comment) is that "development" is incredibly vague, software development or product development are hugely different fields, almost always those roles won't be covered by the same person, unless we're talking about a very small startup. In the article the author makes several statements that apply e.g. to SW dev but not product dev or vice-versa. I find the article confusing for this reason. |
|
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.