The best user experiences are backed by research, but sometimes we move more quickly than our research does. How can we best use and track assumptions as we go through design iterations?
Pursuing a "minimum viable product" (MVP) as a design strategy may work for startups, but usually leads to poorly integrated user experience for established design team working in traditional product categories.
As part of an Agile team, UX professionals should participate in all Scrum events in order to maintain open communication, influence product success, and productively contribute to the team.
Retrospectives are a dedicated time to come together, reflect, and collaboratively improve your design team’s process. In this video, we'll walk through the four components of a retrospective and how to use this meeting effectively.
Retrospectives help teams reflect on their process, identify strengths and areas to improve, and turn insights into actionable plans for better future work.
Like tech debt, UX debt piles up over time and, if left unaddressed, leads to compounding user problems and costly cleanup efforts. Agile teams can modify their processes to track and resolve UX debt.
UX practitioners who feel inept at their job usually face far greater challenges than improving their design, craft or research prowess. Rather, addressing development schedules, Agile, Scrum, Lean, and team members’ roles can create the greatest challenges.
Tips to help clarify the role of UX and how to navigate the relationship dynamics between UX and the rest of the team within an Agile development process.
There will always be constraints that we have to work in, whether it's not having enough time or not having dedicated researchers on our UX projects. This video offers tips on how to do user research without feeling stuck.
UX professionals often receive poorly defined design requests. When saying no is not an option, a more productive way of addressing the request is to focus on the outcome goals and the Return On Investment (ROI) of proper UX effort.
To make UX activities visible, break user stories into UX and development subtasks, add UX to Kanban boards, and include UX acceptance criteria and story points.
