I work in a cyber security company. We have backend and frontend developers in our teams, and I feel like the way the that the product managers work with us is just wrong:
New features are presented and handed over to us as Jira tickets that contain basically contain mostly if not only Figma screens and a very frontend-oriented description of, for example: “The account id field should be a text field greyed out until blabla The scan button should be disabled for 60 minutes after user clicks them”
We never receive diagrams even though we ask for them. The requirements are often invalid as the product managers never take into account how the system actually works and/or interacts with other components
I also have a big problem with the fact that in a very complex system, a backend who writes the business logic has to extract it from Figma screens rather than a diagram or set of business rules.
A bugger problem I see is that the discussions between the devs and product managers are very language primitive due to that and we don’t use a ubiquitous language at all and therefore lose context, information and ideas.
I tried talking to the PMs but was rejected, mainly because they feel like figma is the end all be all for them and feel like they are not supposed to be the domain experts and act as outbound product managers and avoid all inbound activities. We never asked them to get into technical detail, but the only thing they focus on is communicating with customers and add new features they ask us to add, without knowing how the system works (“just add it, we don’t discuss implementations”)
Am I asking for too much?
submitted by /u/subzero11223344
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/jT39NMc