Tag Info

New answers tagged

0

You can find some good pointers on organizing and developing personas in About Face 4. I am going to summarize it here along with inputs based on my personal experience. Developing and Organizing by Behavioral Patterns You can identifying behavioral variables and then relate them to the subjects. These, in turn, depend on factors like activities, ...


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 ...


5

I had very similar experiences to yours (and also been using JIRA for quite some time now). It goes: User stories are extremely limited It seems that every Agile team fails to understand or work with user stories. But for a good reason - a user story capture only a tiny fraction of the problem domain, here's just a couple of things user stories don't ...


8

First things first I don't think UX can succeed in this scenario. A sprint is too short to do both the design and execution of the same feature. You should be out in front of things with the Product Manager defining the work before it ever becomes an engineering request. If you take that approach seriously (which I've never been able to realize 100%), you ...


3

Focus first on the user story. As it stands there is no user value inherent in the first story as it is written. Try rewriting it from the User's perspective (and consider that User's don't want to fill out forms but form fills are necessary in order to get something that they want). Attach a simple ux workflow created by ux in collab with dev. The other 2 ...



Top 50 recent answers are included