Agile for UX Practitioners<br />Anders
Ramsay, Delve Conference, August 2009<br />

About Me<br />

UX + Agile:What Changes?What Stays
the Same?Agile for Traditional Teams?<br />

Agile?<br />

Planning Poker<br />Agile Coach<br />Spikes<br
/>Extreme Programming<br />Backlogs<br />Scrum<br />Test-Driven Development<br />Story Cards<br />Customer<br />Sprints<br />Product Owner<br />Velocity<br />Standups<br />Daily Standups<br />Refactoring<br />Burndown<br />Pair Programming<br />Crystal Methods<br />Feature-Driven Development<br />Scrum Master<br />Adaptive Software Development<br />Dynamic Systems Development<br />Lean Development<br />

Agile is a DesignMindset<br />Specific
to Software <br />From a Developer Perspective…<br />

Two Perspectives<br />UX<br />DEVELOPER<br />

Sample Project<br />Two-week Vendor Bake-Off<br
/>Contrasts Traditional/Agile<br />

Sample Project<br />Traditional<br />Agile<br />

Traditional Lifecycle<br />We can’t start
building anything in two weeks…<br />BUILD<br />DESIGN<br />Time<br />

Agile Lifecycle<br />What is the
Earliest Responsible Moment we can start building?<br />DESIGN<br />BUILD<br />Time<br />HUMAN/TECHNICAL INFRASTRUCTURE<br />

UX: Really? Let’s discuss how
we can simplify it…<br />Dev: This is more complex than we thought…<br />Agile is People-Centered<br />

Project Narrative<br />UX<br />2 weeks<br
/>1-2 Days<br />

Agile is Open, Visible<br />

You can start building sooner
than you think<br />

Project Narrative<br />Reflect, Adjust<br />UX<br
/>UX<br />Build 1<br />2 weeks<br />1-2 Days<br />2-3 Days<br />

Agile Documents<br />

Asking a Different Question…<br />

Comprehensive<br />What is everything developers
need to know?<br />

Just Enough<br />etc.<br />What is
the minimum needed to start building?<br />

Specification Sketch<br />

Designing is Building is Designing<br
/>

Evolving the UI in Tandem
with the Software<br />

Document Cost-Benefit<br />

Agile Documents<br />Yes, you can
keep doing wireframes!but…<br />Design the delta.<br />For conversation.<br />As a means, not an end.<br />

Project Narrative<br />REALITY<br />Reflect, Adjust<br
/>Reflect, Adjust<br />Build 2<br />Build 3<br />UX<br />UX<br />UX<br />Build 1<br />2 weeks<br />

Adaptive<br />Lean<br />There is Only
Us<br />Self-Organizing<br />Reality-Driven<br />Conversation-oriented<br />Iterative<br />Autonomous<br />Agile Mindset<br />Visible<br />People-Centered<br />Focused<br />Software-specific<br />Sustainable<br />Open<br />Solution-oriented<br />Technical Excellence<br />Light-weight<br />Safe<br />

Getting Started<br />

Step Zero: You and Your
Team<br />

Process is a Secondary Effect
of People<br />—Alistair Cockburn<br />

Beware Agile Orthodoxy and Ritual<br
/>From HenrikKniberg’s Blog at blog.crisp.se<br />

The BigCorp Factor<br />

Iterate the Transition<br />

Takeaways<br />

Agile + UX?<br />

Agile <br />UX<br />

Agile<br />UX<br />Mutually Empowering Opposites<br
/>

Takeaways<br />Start with an Agile
Mindset and all else will follow.<br />Develop your Developer Perspective.<br />Same UX Principles, New artifacts and methods.<br />

Thanks!<br />@andersramsay<br />AndersRamsay.com<br />AgileExperienceDesign.org<br />http://ia.meetup.com/14/<br
/>http://www.meetup.com/agile-experience-design<br />rosenfeldMedia.com/books/agile-experience/<br />