The classic development phases are
- requirement elicitation
Currently we are having issues with UX joining the mix. My current job lets UX build wireframes as the very first step, and they are treated as SRS. This has led to a lot of incomplete designs, wrong technical assumptions and a lot of mistakes as well.
As wireframe driven process is not working for us, I would like to know exactly how UX fits in development and already existent disciplined approaches
Sorry I could not think of a proper way to google this
EDIT: Just a bit more context on this
The devs (me included) are familiar with Scrum. Our company got restructured a fair bit and as a result our projects do not start with Requirements anymore, but with Wireframes and fairly broad User Stories.
We used to treat Requirements (business rules) as being written in stone, with small changes here and there. But now that UX/UI comes first, the designers assume all is common sense and critical pieces of code design are left to the devs imagination.
Should I assume UX/UI products are also iterative? part of the actual design phase of coding, and not requirements? References to methodologies are greatly appreciated