5 ms·
I feel for the above commenter. I cannot relate to their experiences as fulsomely. Within my past several roles I have always had a really good experience with
by TheNewsIsHere 3y ago
I feel for the above commenter. I cannot relate to their experiences as fulsomely.
Within my past several roles I have always had a really good experience with engineering, requirements gathering, and how those disciplines are executed by stakeholders, including management.
It’s fair enough to say that having worked at a cryptography company where the CEO was a mathematician is probably fairly rare, but I don’t think that this being an exception is an indictment on the various methods used to go from ideation to implementation.
Edit to say: user stories in particular are as good or as bad as those involved in creating them are skilled and understanding of what is being requested, what is needed, etc. In my prior company we had an entire design team who took care of the UI/UX, and decoupled that (largely) from logic, implementation, platforms etc.
- deleted 3y ago[deleted]
- xcv123 3y ago> I feel for the above commenter. I cannot relate to their experiences as fulsomely. Not as bad as it sounds, when the requirements are provided at a high level. In a User Story the implementation details and software architecture are left to the developer.