Absolutely. This is why I tell people the resistance to being an agile team (and not just another team that uses agile processes like scrum but doesn’t change direction) usually comes from people not wanting to be humble enough to admit there are other sources of good ideas than themselves.
I do wonder if non-techies could be scared of being "more involved" in development, or they might not care, because just implementing dev-specific processes improved raw code efficiency and they get what they want out of it - therefore, why change it?
On project level, would you still need some sort of set mission statements that don't change?
Or is it better to not enforce any and go "with the flow" so to speak?
I mean, it's kind of unlikely that you start with building CMS system and end up with open world PS4 game, so it might waste of time to even worry about it.
On other hand I could see how it could end up exactly like you described in your story, where it seems company lost the concentration and went crazy with including features.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Absolutely. This is why I tell people the resistance to being an agile team (and not just another team that uses agile processes like scrum but doesn’t change direction) usually comes from people not wanting to be humble enough to admit there are other sources of good ideas than themselves.
I do wonder if non-techies could be scared of being "more involved" in development, or they might not care, because just implementing dev-specific processes improved raw code efficiency and they get what they want out of it - therefore, why change it?
On project level, would you still need some sort of set mission statements that don't change?
Or is it better to not enforce any and go "with the flow" so to speak?
I mean, it's kind of unlikely that you start with building CMS system and end up with open world PS4 game, so it might waste of time to even worry about it.
On other hand I could see how it could end up exactly like you described in your story, where it seems company lost the concentration and went crazy with including features.