Are there documented alternatives to user stories within Agile that UX can use to handle 'bigger picture' thinking?
For example, there may be a web page that has 3 distinct 'chunks' of development. The developers need these broken into individual stories so they can go off and start building all the back end connections to make them work.
However, these 3 'chunks' have to be designed as one holistic page from a UX and UI standpoint.
We're struggling how to accommodate that in the context of JIRA--where we're expected to break down stories into daily-trackable tasks.
Adding UX tasks under each user story is one way to handle it, but that's essentially duplicating tasks.
For example "create wireframes" would be a task for each story. But there's only one wireframe: the wireframe for the page.
So we're trying to find a way to pull out the UX task as a separately trackable element that doesn't overlap/interfere with the stories dev is using.
One thought would be a 'ux story' (for lack of a better term) that might read as:
As [developer on our team], I need [to know what the UI will be] so I can [build the solution].
To me, that sounds rather silly, and is more of a hack than anything, but this would allow us to then build tasks for UX to handle and easily track within one story.
Has anyone found a better way to handle this (short of moving UX out of the sprints in the first place...)?
The 'design spike' has been one suggestion, though everything I read says those should be used sparingly. And we need a solution for each sprint so that UX can work on tasks that dev can then implement the next sprint.