The document discusses integrating user experience (UX) design into an Agile/SCRUM development process. It outlines some key Agile values and principles, such as prioritizing customer satisfaction, welcoming changing requirements, and delivering working software frequently. It notes some common pain points that both UX and Agile aim to address, such as impossible estimates, missed deadlines, unusable software, and frustrated users. Finally, it provides some guidelines for integrating UX into Agile, such as researching first, designing second, collaborating closely across teams, and prioritizing features based on user needs, business goals, and technical feasibility.

1. Integrating UX and Agile /SCRUMA work in progress

2. Agile ValuesIndividuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan

3. Agile PrinciplesOur highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

4. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

5. Agile and UX start with the same problems:Estimating scope is impossibleDeadline aren’t being metCode needs to be rewrittenSoftware is unusableUsers aren’t part of the equationBudgets run overEverybody is frustratedInsert your favorite painpoint here

8. Some things that neither UX nor Agile can FixExecutives that change their mind every weekPoor judgment of people in controlLack of corporate strategyInadequate skill setToo many developers, not enough designers

9. Iteration Cycle Hierarchy

14. Some GuidelinesResearch firstDesign secondCollaborate closely with business ownersCollaborate closely with developersPrioritize features based on user needs (research), business goals, and technical feasibilityHave a meeting with designers, developers, and business owners in one roomUsers and customers are represented by designers and product managers

15. More GuidelinesDocument the designKeep design documentation currentDon’t code too soonDon’t let developers talk to customersRe-evaluate your process periodically and see what works for you and what doesn’t.Make it betterLet me know what works for you and what doesn’t.

16. Daniel JaegerInteraction Design & Strategydaniel@citizenbrain.comwww.citizenbrain.com

17. ?