1 / 22

Agile User Experience

Agile User Experience. May 2011. Agenda. Executive Summary. Agile – An Overview. User Experience – An Overview. Case Study. Integration of UX into Agile teams. Success Factors. Executive Summary.

janus
Download Presentation

Agile User Experience

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile UserExperience May 2011

  2. Agenda Executive Summary Agile – An Overview User Experience – An Overview Case Study Integration of UX into Agile teams Success Factors

  3. Executive Summary • User experience is such a challenging art of inducing positive emotions on the consumer, not through words or flora, but by highly thought out software applications • According to NNG Report ‘Agile, Scrum, and the like, simultaneously poses an opportunity and a threat to achieving a quality user experience’ • Balancing agile process and user experience is the key to success. Case study highlights the practical tiffs in the balancing act. • Success factors gathered through real time experience is prescribed.

  4. Agile – An Overview Create tested build to meet a defined set of objectives Create tested build to meet another defined set of objectives Create tested build to meet another defined set of objectives Requirement Requirement Requirement Release of Customers Demo of Release Demo of Release Implementation Implementation Implementation Integration Test Integration Test Integration Test Customer Inspection and Acceptance Customer Inspection and Acceptance

  5. Agile – An Overview….contd As a _________________ <user type> I want ________________ < a goal > So that ____________ <reason/benefit> • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration • over contract negotiation • Responding to change • over following a plan STORY Manifesto _______ story points AGILE • User Stories • Backlog • Whole Team • Sprint • Scrum • Burn down Chart • Continuous Integration • Conditions of satisfactions (Success / acceptance criteria), often built around the “so that” value statement is written on the back of the card Criteria Elements

  6. Agile – An Overview….contd Copy right information - agilescrum.biz

  7. Benefits of Agile Testing • Faster time to market and continuous integration • Enhanced customer experience • Ease of managing change even late in development • Working software is the primary measure of progress • Business and developers work together daily

  8. User Experience – An Overview • How a person feels about product, system or service • Affective, meaningful and valuable aspects of human-computer interaction • Perception on utility, ease of use and efficiency of system • Subjective in nature • About individual feelings and thoughts about the system • User experience is dynamic

  9. User Experience – An Overview….contd Copy right information - montparnas.com

  10. Case Study – Working Model Project Charter Onsite Huddle Sprint Review & Retrospective Virtual Task board & Online collaboration tools Offshore Huddle 2 Weeks Product Backlog Sprint Potentially shippable Product Increment Sprint Backlog Sprint Planning

  11. After 2 Iterations…. • Open communication encouraged • Planning, Huddle and Retrospective meeting spirit is reiterated • More time spent on code integration • Agility is not rush, but project control. This philosophy is getting imbibed • Manager finally figures the role he has to play for the team

  12. After 5 Iterations…. • Success criteria met • Stuck to commitment • Unit and Integration test passes • Improved team dynamics • Better level of automation • Auto build tools for seamless integration • Automated acceptance test tool deployed • XP Practices enforcing quality of code • Agility Assessment • Agile maturity models deployed

  13. Voice of Users • “Words are barely legible” • “I am not sure if this is what I was looking for” • “Ok, I am waiting for some text to tell me what I must do next” • “Has the page finished loading ?” • Test users used it differently from how the developers intended • Attempts to improve always raised fundamental questions • Debate on scope, audience, purpose and functionality suddenly aroused within the team • What seemed certain suddenly became precarious • No understanding of the audience made the product appear bad

  14. Missing Factors • Identification and quantification of usability issues • Ability to understand what is / isn’t an issue • Knowledge on both domain and usability • Impatience to fix previous errors and the eagerness to move forward • Insufficient business perspective adoption Solution: An UX Practitioner was brought into the team

  15. Contributions of an UX Practitioner • Knowledge enhancement • Enabled good communication between management, developer and end users • Knowledge on lessons learnt proved vital • Outcome of User research techniques • Which group of people want the product • What they want the product to do • What is crucial for them to know and remember • Part of Scrum • Ensures every user research findings are considered in the product backlog • Priority of stories revised better • Works for one or two sprints ahead in parallel

  16. Process of Agile UX Integration • Rudimentary model was built based on existing UX knowledge and tested with users • Conceptualization prior to development based on the above feedback and user research inputs • Prepared to iterate based on the lessons of previous iterations • Domain knowledge proved a big help • Complex Interfaces handled as design only sprint • Management understanding that something may not be right the first time. Iterate to perfection

  17. Typical day of an UX Practitioner

  18. Agile UX Challenges • Lack of time for upfront research • Dependency on historical research data User Research • Definition of users loosely defined • Mixed interpretations of user from business and IT community • Representation of users in discussions Who are the users ? • Focus on writing and testing code ? • Developer seems to have a upper hand when compared to UX practitioners • Influence of non-developers minimal Development Centric Approach • Centralized UX team • Not able to get the right input at the right time • Lack of deep integration considering the matrix environment Availability of UX practitioners

  19. After 10 Iterations….. • Achieved reasonable Time on task with test users • Improved efficiency leading to user’s delight • Better levels of success achieved with the test users / participants • Product contained very minimal error opportunity • Product contained exactly what the user must know and remember

  20. Integration of UX into Agile Teams • UX practitioners are catalysts • UX work can be planned and done up-front • Light weight approach • UX work can happen in parallel • Voice of User – Fast and Effective

  21. Success Factors • UX practitioners need to go Agile way and Agile team needs to understand and appreciate the role of UX team • Full time UX practitioners especially for new start-up projects • Entire team understands the agile model and collaborates for client success • Large teams need to be planned and handled differently • Always have room to learn and grow

  22. Thank you

More Related