Heh.
Design documents are only useful if those deciding the design are making it and are ready before the coding starts.
And then there is this confusion of which “Design Document” one is talking about. It could be a UI/UX document or it could be the software design document, which would comprise multiple flow-diagrams, helping anyone pick up a project for maintenance and extension.
This kinda depends. User stories document the typical goals and workflow of the users with the app, and thus should come from the target users or at least the client like a manager. The designer is not qualified to make the user stories since they don’t know the business domain, as it’s called. But they know how to organize the UI for any particular goals.
Heh.
Design documents are only useful if those deciding the design are making it and are ready before the coding starts.
And then there is this confusion of which “Design Document” one is talking about. It could be a UI/UX document or it could be the software design document, which would comprise multiple flow-diagrams, helping anyone pick up a project for maintenance and extension.
This kinda depends. User stories document the typical goals and workflow of the users with the app, and thus should come from the target users or at least the client like a manager. The designer is not qualified to make the user stories since they don’t know the business domain, as it’s called. But they know how to organize the UI for any particular goals.