I’m a junior just a few months into my first software dev job after graduating. We are three sprints into our new project and they management decided to use Scrum as it’s “a fresh approach.” To “keep things agile”, the scrum master is using a random number generator to choose tasks to do during sprint planning. It is apparently called “planning gambling.”
We use React and Django, so front end and backend tasks a separate. The “planning gambling” has resulted in all sorts of frontend parts without backend and all sorts of backend stuff that doesn’t do anything.
They also embraced wholeheartedly the agile philosophy of not spending time documenting anything, so developers are making all the decisions beyond the one sentence of functionality they give us in the tasks. Fine if the devs were building the complete component (as we have reviews/demos), but problematic when they components need to talk in some random task assigned later and the components are not fully built.
The project is moving slow as a lot of time is spent guessing at the actual needs of the component, upper management complains about the lack of progress on specific pieces (and blames our tech lead, not the scrum master, who says it is waterfall management to choose one component over another), and we spend a ton of time redoing work because the product owner and scrum master do all of a sentence of thinking before they send devs off to code and hope they guessed the goal of the component correctly.
Is this what software development is like normally? As I don’t think this career is for me anymore...