Tag Info

New answers tagged

2

The answer is a spike story I heard people say there is no room for UX Design in Agile. But there is if you make the most out of it. You can do a spike story before pulling up the actual userstories from the backlog. A spike is a story or task aimed at answering a question or gathering information, rather than at producing shippable product. Sometimes a ...


0

There are a lot of best practices out there. For my work the use case 2.0 model from Ivar Jacobsen works good. In general think about established process management models like use cases, think about agile stuff like user stories/epics/..., think about combining them for your business. Use Case 2.0 Whitepaper


6

Great question. I'll try and break it down into a couple of components of how to provide the holistic view and task management (and reference Jira documentation when I can). From what you have described, a user story to handle the 'bigger picture' thinking is called an Epic. An epic is essentially a large user story that can be broken down into a number of ...


0

Great answers above, but this may also help if you are truly agile: Design as a Kanban Stage Instead of making a card for UX/UI design vs. coding, we treat design as a stage in our Kanban boards: Open --> Ready for Design --> Ready for Coding --> In Progress --> Ready for UI Review --> Ready for Code Review --> etc. Note the "Ready for UI Review", which ...



Top 50 recent answers are included