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.
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.
UX teams are responsible for creating desirable experiences for users. Yet many organizations fail to include users in the development process. Without customer input, organizations risk creating interfaces that fail.
Agile teams are more proficient in executing the development process, but the compressed timescale forces some to abandon user research and degrade the resulting user experience.
Design charrettes inspire design sketches and ideas, include more people in the design process, explore and expose goals and objectives of colleagues in multiple functional roles, and drive off designer’s block.
Agile projects aren't yet fully user-driven, but new research shows that developers are actually more bullish on key user experience issues than UX people themselves.
Simple user testing with 5 participants, paper prototyping, and heuristic evaluation offer a cheap, fast, and early focus on usability, as well as many rounds of iterative design.
Agile methods aim to overcome usability barriers in traditional development, but pose new threats to user experience quality. By modifying Agile approaches, however, many companies have realized the benefits without the pain.