New answers tagged

0

UX is something you have to test actively from day one, and keep on testing while the product develops. Beware! It's super easy to forget about UX testing while you are pushing the developers hard and everybody is working like hell in your team. UX testing has to be part of your Definition of Done! Meaning that no "story" should be considered as Done, if ...


0

Initially I was finding it difficult to match my standard ux design process to Kanban, but after a little while it started to work. It took a lot of changing and rethinking stuff though. This was a bit of inspiration for me: http://kanbantool.com/blog/kanban-for-ux-design


0

When ever you add an item and then when you are going to edit an item, we should have prompt message for save are cancel the added item. same message should be displayed once we have edited the sub item too. there should be final save button to the whole process then user can understand its the final call for the form. this is my view.


0

I think what you have a the moment is an asset that is somewhere between a design guide and a development framework. What you need depends on how your team's process in transferring design concepts to a built product works, and where the hand-over point is between the designer and the developer. Be careful also not to be too detailed in your wireframes ...



Top 50 recent answers are included