I am a Product Owner for six months now, comming from the industry(electronic equipment) where my new company (200 employees) is creating software for. To make the switch to this new job I've studied programming and software engeenering for several years. The company creates complex new software. My team members are very divers in age and experience.
We create functional designs as a team and I let them review my use cases. Till that point it goes great, they give me great feedback.
But the design process stops there. They take use case 1, program it functional and then refactor it. Then they take use case 2, come to the notion they have to change 1. So they change one, introduce a bug, finish use case 2, fix the bug. Then they take use case 3, come to the notion they have to change use case 2, which leads to changes in use case 1, and so on. In this 6 months they created one sequence diagram because I asked them to. So no technical design, no class diagrams, no sequence, communication or state diagrams. After about a week in the sprint they start to ask me questions that tell me that they are zoomed in so far that they have lost sight of the bigger picture and have forgotten things.
Before I go and discuss this with my teamleader. Can this be a 'normal' programming style in your opinion? When I program something for my self, I devour a "ton of paper" before writing one line of code, but I consider myself an amateur. Is it just a matter of personal taste, or does every self respecting programmer first has to form an overview of what he will be coding and create some form of technical design for new functionality, no matter the circumstances.
Thanks for your time. I don't mean this in a bad way, I just wan't to make things better if I presume they can be.
Searching for an edit button
