Nexon seminar: getting to know agile UX and lean UX
Common ground: iteration through feedback.
agile: the build process — speed, optimization for the service (prototype) → Refine
regular iteration, tight collaboration, incremental build: agile manifesto 200
ux: concept, design, direction, quality (research, analysis, wireframes) → Define
agile UX: agile + UX
tight collaboration, each person owns their work
one sprint ahead
lean UX: design thinking + agile dev + lean startup
fused into one team
parallel sprint
lean → measure (idea + data + code) → build
Identify the MVP: pick based on facts (needs, pain points), user research, build fast and test.
Define a shared goal — make the service goal concrete (service concept, specific users).
Sketch (UI + communication).
Co-creation workshop — pool thoughts and solve problems.
Make all work visible and open for feedback.
Whenever anyone starts first, that's when it starts.
Focus on the goal; plan iterations and write deliverables based on decision criteria.
To-do (iteration plan) + progress + communication (everyone shares what they're doing in the overall schedule; visible = traceable).
Break tasks down small where possible to build flexibility.
Work in the same space if possible (bonus: have walls).
Set up and review regular feedback (deliverables vs. service validity).
Build just enough — 'this feels like enough.' (Keep a buffer to recover from mis-steps, drop excessive UI obsession, and split design development into separate time windows.)
Small teams communicate more efficiently.
Building a prototype fit for purpose is the core. Cram in too many features and you'll have just as many fixes (things to throw away).
The importance of retrospectives (maintain context via daily scrum — issue-driven, casual delivery, share wiki URLs).
Shared goal: project name, concept (one sentence), keyword (concept-related expression words → design work), persona (behavior).
Empathy map (what users think), product canvas.
Story card: from the perspective of (role), I want to (behavior) in order to gain (value).
feature < who will use it.
Set priorities: cards → arranged by rank.
Retrospective (prepare, gather data, categorize the records, discuss, pick action items).
\"Good decisions come from experience.\"
books: Lean Startup, Learning Lean, Lean UX, Agile Retrospectives, Gamestorming
