Making UX Work with Agile Scrum Teams – Our September 18 Virtual Seminar

Where does UX design fit into sprints? How do companies let go of Waterfall methodology? If you’re struggling to confidently and clearly answer either of these questions, then it’s time to register for Aviva Rosenstein’s seminar. You’ll learn how to clarify roles and responsibilities, and more effectively track and estimate UX work. You’ll also hear case studies of companies that brought teams together to work more collaboratively, iteratively, and harmoniously in an Ag?ile process. Learn from teams who’ve “been there, done that” Increase the value of UX in your organization Get scrum teams involved in UX If your team could benefit from Aviva’s seminar, join us on September 18....

UIEtips: Dissecting Design – Part 2

In this week’s UIEtips, we offer part two of Ben Callahan’s article, Dissecting Design. In it, he explores which tools are the most helpful for different parts of the design process. Ben was one of our top speakers at this year’s UX Immersion Mobile Conference and we’re pleased to have him back for our next virtual seminar on June 5, Responsive Workflows: Because There’s No Such Thing as a Perfect Process. Here’s an excerpt from the article: I believe many people in our industry struggle with “design in the browser” simply because they aren’t fluent with the tools needed for working that way. I’ve heard many people say, “Happy accidents don’t happen in code like they do in PhotoShop.” I can testify that this is absolutely not true. Instead, I believe it’s about where you are the most fluent. As we evaluate the best tools for the monumental task of problem solving in design, I keep coming back to the ideal of fluency as a solid principle on which to base the decision. You can’t write poetry in a language you don’t speak. Similarly, you can’t craft design using tools you’re not fluent with. Read part two of the article here. Missed part one? Read it here. What tools do you and your team find most efficient and effective in solving design problems?  Tell us about it...