The Emergence of UX in an Agile World


Published on

2010 YOW Australia talk on the emergence of UX in an Agile world based on the experience at Cochlear Limited.

Published in: Design
1 Comment
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

The Emergence of UX in an Agile World

  1. 1. Agile & UX 1Welcome everyone. We’re here today to share our story of the emergence of UX in an Agileworld.Before we get into it let’s introduce ourselves.Image:
  2. 2. Victor Rodrigues 2I’m Victor Rodrigues.
  3. 3. Born somewhere over here 3I’m originally from South Africa.Images: &
  4. 4. 4Although I am 1st generation South African, being of Portuguese extraction.Image:
  5. 5. 5You see my parents were one of those who ventured to Mozambique from Portugal.Images: &
  6. 6. 6And for those of you that don’t know where Mozambique is, it’s that country on the eastcoast of Africa.Image:
  7. 7. December 2000 7In December 2000
  8. 8. 8I moved to Sydney Australia and I have to say...Image:
  9. 9. 9I have never felt so comfortable in a country as I have been in Australia.Image:
  10. 10. 10I have two daughters, Addison & Ashlin (born 7 weeks ago).
  11. 11. 11My day job is running a software development department at Cochlear based in at our headoffice in Sydney.Image:
  12. 12. 12We’ve actually just moved into our brand spanking new building on the Macquarie Unicampus.
  13. 13. 13And it’s pretty awesome
  14. 14. 14With lots of natural light, something we’re not really used to.
  15. 15. Xerxes Battiwalla 15And I’m Xerxes...
  16. 16. 16I was born in Australia, and grew up in an erawhen...Image:
  17. 17. 17...a good moustache looked like this...Image:
  18. 18. 18...people had hair like this...Image:
  19. 19. 19...when the king of pop looked like that...Image:
  20. 20. 20...and wearing your pants backwards wasn’t at allweird.Image:
  21. 21. 21I’ve had a passion for computing since I was a littlekidImage:
  22. 22. 22eventually working my way through to this uglybuilding - (the University of Technology, Sydney)where I studiedImage:
  23. 23. C# TDD 23 ...(and now teach)...Computer Science, but actuallyspent most of my time...Image:
  24. 24. 24here. The bar.
  25. 25. 25winning look-a-like competitions
  26. 26. <boring_lob_apps /> 26After working through a number of projects...
  27. 27. 27...i found myself here in 2008...
  28. 28. 28...working with an incredibly talented team ofdevelopers...
  29. 29. 29...on software that changes people’s lives, whichis....
  30. 30. 30awesome!Image:
  31. 31. 31So a little about Cochlear.
  32. 32. “The cochlear ear implant is the first and only device produced by mankind which effectively restores the use of one of the human senses” Sir Gustav Nossal, Australian of the Year (2000) 32I think Sir Gustav Nossal probably says it best.
  33. 33. 33Back in 1980 we had what we called the “Portable Speech Processor”.
  34. 34. 34Last year we released our new implant system which now includes a wireless remote controlfor our recipients...
  35. 35. 35and our smallest processor ever.
  36. 36. 36And by the way, we’re hiring.Image:
  37. 37. 37Okay let’s get back to why are we here today!
  38. 38. I write I design software experiences 38We’re here because we want share our story of how we married UX with Agile in ourdevelopment process.Image:
  39. 39. 39There are some that previously believed that User Experience Designers and Agilepractitioners just don’t mix. But before we explore UX and why it’s important, let’s look atwhere Agile came from.
  40. 40. 40According to Jeff Patton “Agile development originated from a place where user experiencepractice was weak”This chart (courtesy of Jeff Patton) shows on the y-axis user adoption scale and the x-axispurpose. Bottom left is synonymous with internal IT projects which is where Agile, accordingto Jeff, originated. On the top right you have consumer commercial stuff where UX is vital andusually determines the success of your product.Reference:
  41. 41. 41But then you ask yourself: but hang isn’t Agile all about user centredness?Image:
  42. 42. Individuals and Interactions over processes and tools 42If you recall the phrases of the Agile Manifesto. The first one emphasises Individuals andInteractions. That’s user centred!
  43. 43. Customer Collaboration over contract negotiation 43The third one talks about Customer Collaboration. The mere fact that the word Customer isthere makes it user centred.
  44. 44. 44Then there are the practices such as the Customer Role...Image:
  45. 45. 45Usability testing.
  46. 46. Not Enough 46The problem is that it’s not enough.
  47. 47. Experience needs to be Designed 47Experience needs to be designed.
  48. 48. 48Allow me to elaborate. And this is where I get on my soap box and talk about what I call...Image:
  49. 49. Total User Experience 49Total User Experience.
  50. 50. The Problem! 50I usually begin this speech by talking about the problem. Think about the world you live inand the things that you interact with every day.
  51. 51. 51You get road signs that make you stop to read them in order to get what you need
  52. 52. 52Parking pay stations that make you wonder if they were designed by...
  53. 53. 53politicians.Image:
  54. 54. 54User interaction choices that make you do unnatural things.
  55. 55. 55Then there are the excessive options and the confronting choices that we have to make.Image:
  56. 56. 56And there are others.Image:
  57. 57. 57But I think the one thing major problem we’re faced with today is...Image:
  58. 58. 58information overload!
  59. 59. 59Now think about your average user, they still like the simple pleasures in life such as...Image:
  60. 60. 60Reading a book!
  61. 61. 61Or dining out!
  62. 62. Can’t escape User Experience 62But even those things have some level of user interaction encompassing them.
  63. 63. 63You still have to stand in a queue to purchase a book.
  64. 64. 64Or read a menu before you can order and enjoy your food.
  65. 65. 65Pay for your food with one of your many credit cards.
  66. 66. 66I think you get the picture.Image:
  67. 67. 67Thus the total customer experience is not only about how you use a product or service, it’show you:- go about finding it- how your perceive it’s value- how easy it is to purchase- how easy it is to fix if it’s broken... and so on
  68. 68. 68The problem is that most of the time us software people forget this.Image:
  69. 69. 69Why, perhaps because there are too many technologists in technology.
  70. 70. 70The technology is only half the equation.
  71. 71. 71The other half is the human, thatirrational,impulsive,impatient,power-hungry gratification machine.
  72. 72. Examples 72I’m merely touching the surface of User Experience Design. There is a lot more that we cancover. But before we get to the Cochlear experience I’d like to do share with you a fewexamples of what Seth Godin refers to as things that are...
  73. 73. Broken! 73Broken! Products that we interact with in our world that have lacked that user experiencedesign.
  74. 74. 74These are parking pay stations used throughout Sydney.I always have to read the instructions before doing anything on this thing.
  75. 75. 75Here is the American Airlines website.Some of you may have heard of Dustin Curtis. He hated the experience you get frominteracting with the American Airlines website that he sent them a design to help them out alittle...
  76. 76. 76I’m not going to get into the specifics of why this is a better user experience but it certainly isa lot more inviting?
  77. 77. 77Here’s one from American Airlines that I have personally experienced.Wanted to lodge a complaint about a bad flight experience and couldn’tStates that there are “errors” but I couldn’t find any.
  78. 78. 78While I was doing some research for this presentation I tried Frontier airlines’ website.Even though I have not flown with them I tried their customer support.Easy enough to find.
  79. 79. I am giving a demonstration of your website user experience and how it compares to other airlines... 79And this is what their customer relations form looks like.Much simpler, much more inviting. It only requires you to fill in 4 fields.This is the gist of what I wrote...
  80. 80. Your kind words will be shared with staff, and I am sure they will be delighted. 80And I actually go a response that was addressed to me personally ANDdealt with my comment!
  81. 81. Book next trip on Frontier 81And how do I feel after this experience?I want to fly Frontier.Image:
  82. 82. 82This is a pet peeve of mine as I use MS Excel as lot. A dialog box that forces you to read everylittle bit of text before you hit either Yes or No.The problem with this dialog is that because the buttons are labelled Yes/No you always haveto read the text before your selection is made.
  83. 83. Some content in “N5 Recipients Americas.xls” will not be saved. This is due to compatibility differences between the newer .xlxs and the older .xls file formats. Cancel Save as .xlxs Save as .xls 83Here’s my attempt at redoing the dialog and conveying the same information.In fact you will probably read all of it the first time but because the button text contains theactual action you will not have to next time around.I’m sure I could have done a better job here but I only spent a minute on this one.
  84. 84. The Good Ones 84There are however beautifully designed products and here are a few that I think are goodexamples.Image:
  85. 85. 85Of course I would not go through a presentation without mentioning an Apple product. Thething about Apple products is that they have inspired...
  86. 86. 86the most amazing applications ever seen on any platform (in my humble opinion of course).
  87. 87. 87The guys at RunKeeper I think are an example of how you can design a great user experiencewithout spending a bucketload of cash.
  88. 88. 88Anyone use Rushfaster before?I particularly enjoy the customer experience when using this online store.
  89. 89. 89But it’s not only Apple does can design awesome user experiences. This is the launch site forthe Google’s Nexus S Android phone and it’s superbly designed.Reference:!/index
  90. 90. 90It even gets Dustin Curtis’ seal of approval.Reference:!/dcurtis/status/11962698954711040
  91. 91. 91I’m going to finish “the good guys” with this one. It’s a free web-based book done by thesame team from Google that brought you Chrome.Not only is it the perfect layman’s explanation of what web browsers are and how the webworks, it is also wonderfully executed.It certainly gives you a glimpse of what we have in store in the near future for web-basedexperiences.Reference:
  92. 92. Summary... 92So a quick mid presentation summary...What is becoming more and more obvious is that people are looking for things that are...
  93. 93. 93Simple...I love this quote and I think it should become engrained in all of us.
  94. 94. Familiar 94We want things that are familiar.Image:
  95. 95. Obvious 95Obvious.
  96. 96. Really Obvious 96Really obvious.
  97. 97. Choice limited 97And limited in the number of choices to make.
  98. 98. 98Time for me to get off my soapbox and talk about our one of our projects at Cochlear wherewe attempted to put into practice this preaching.Image:
  99. 99. 99So this is our story. It’s the story of a recipient’s journey.Once a recipient is implanted with one or more of our devices they will undergo...
  100. 100. Fitting 100A series of fitting sessions in which the device is configured for their specific physiology.
  101. 101. Fitting Habilitation 101A recipient may undergo habilitation to ensure they get the most out of their implant system.
  102. 102. Fitting Habilitation Upgrades 102In their lifetime they will upgrade some of their system components to the latest model orcompliment their existing model.
  103. 103. FittingHabilitation UpgradesTroubleshooting 103They will troubleshoot problems or situations with their implant system.
  104. 104. Fitting Habilitation UpgradesTroublesh...Service & Repair 104Which may or many not result in servicing or repairing their implant system.
  105. 105. 105There is a bottleneck in our industry, the lifetime support for programming and maintenanceof the implant system juxtaposed by a staggering increase in recipient numbers notcomplimented by an equal increase in the number of professionals.Image:
  106. 106. 106Not only is it labour-intensive... but the current flexible software is not ideal.To make cochlear implants accessible to more people we needed a solution that wouldinvolve the development of a user experience that can be used with embedded intelligenceto...
  107. 107. 107allow unskilled programmers to optimise CI at the same level as highly experienced CIprogrammers.Image:
  108. 108. Challenge! 108To draw out this challenge...
  109. 109. 700 million by 2015 109There are more than 700 million will be hearing impaired by 2015.
  110. 110. 110We have an ageing population whose life expectancy is constantly increasing.Image:
  111. 111. 1110 – 14 years olds are becoming more and more aware of and actively using technology.Image:
  112. 112. <10% 112Estimated less than 10% of the people that need cochlear implants are receiving them and weknow that the number of recipients will increase exponentially.
  113. 113. 113Software plays an extremely important role in ensuring that we meet this challenge.Image:
  114. 114. 114Ultimately we would like to go from this (extremely flexible software but only necessary by afraction of recipients that are programmed through it) to...
  115. 115. I don’t need software. I’m self configuring. 115To this.
  116. 116. 116But before we get there we need to make the most of what our software products do for thehere and now, taking on those customer centric characteristics I have spoken about.Image:
  117. 117. How did you do it, fool? 117So given this background over to my world famous colleague who will dissect our UX & Agilestory on this particular project.So how did we bring out the best of UX in our agile project?Image:
  118. 118. 118Just like any other agile project, it started with a full story backlog.“What features do we want in this application?”.Our team get together and work out exactly what broad functionalitywe wanted in the final product.
  119. 119. 119The UX team then went off and started drawing up a holistic view ofwhat the application might look and feel like.Image:
  120. 120. 120Although agile development works brilliantly when performed usingsmall, baby steps. Improving, piece by piece...Image:
  121. 121. 121...UX needs to work at a higher level, taking the whole applicationinto consideration, devising a very low-fidelity imagination for whatthe application would look like from the point of view of the peopleusing it.Images:
  122. 122. 122This also meant building up a series of personas to identify who willbe using our application, and what role they play in the wholesystem
  123. 123. Going separate ways 123So given the very different ways these two teams work, both go intheir own separate direction. The UX team start kicking around ideasand prototypes and putting them to test audiences, and thedevelopment team start working out technical implementationdetails, and report to an internal customer while the real customer isstill trying to work out their direction.Every now and then, the two teams...
  124. 124. 124...come back together to reconcile where they’re at and then worktogether when it comes to the actual implementation.
  125. 125. 125So once the features were identified, we then took the entire productbacklog and split it out into releases. “What do we think isachievable in the time-frames we have for Release 1?”So far this is just standard agile - nothing new here. Where thingsget interesting is next.Image:
  126. 126. 126For each release, we then worked out exactly what UI detail wewanted to go down to. In fact, we took this a step further, andwithin Release 1, we identified 5 primary “drops” each representinga different stage of development for the first release.Image:
  127. 127. DROP 1 DROP 3 DROP 5 Core Clinical Back Office Release DROP 2 DROP 4 Clinically Complete Help & Guidance 127Each drop has a specific purpose, so there are UX considerations foreach stage. Some upfront IA helps us better understand what eachspecific drop is capable of.
  128. 128. DROP 1 Core clinical functionality 128DROP 1: Specifically intended to test and validate the corecomponent of the underlying principle behind programming ourrecipients.UX was not a major consideration here. Why? We have enoughtechnical challenges to overcome alone without the UI/UX cominginto it. We’re dealing with electrodes in people’s heads! The lastthing we want to do...
  129. 129. put the wrong amount of electricity into someone’s head!Getting this right is critical!Image:
  130. 130. DROP 2 Clinical verification 130DROP 2: First real-world user-experience test. The clinical aspectwas complete from a technical standpoint...
  131. 131. 131...and now we were focusing on the usability of the clinicalcomponent. Giving it to our clinicians and actually using thesoftware to give people back their hearing.
  132. 132. DROP 3 Back-office operations 132DROP 3: Up until this stage the only UX consideration had been froma clinical standpoint, but now we needed to look at all the back-office operations, and ensure that the system stores and presentsinformation such as recipient details with databases and existingsystems - and does so intelligently.
  133. 133. DROP 4 Help and guidance 133DROP 4: Help and Guidance. This drop introduces contextual helpinto the system and assistance for when the clinician doesn’t knowwhat to do. How do you assist the user without being too intrusive?
  134. 134. 134Microsoft made mistakes - we’re taking advantage of thoselearnings...Image:!_1.jpg
  135. 135. 135...and yet don’t forget - UX isn’t restricted purely to the Englishlanguage. All along, the designers have been crafting the UI with theintention that non-English character sets will be used as the displaylanguage for the software. This particular drop also validates thatour application functions in Hebrew, Hindi or Hungarian.Image:
  136. 136. DROP 5 Product release 136Finally DROP 5: Ready for production.Any UX changes happening at this stage are minor alterations. Allthe major decisions have been made upfront, with the application asa whole taken into consideration.
  137. 137. UX Evolution 137Once our releases were determined and we had a rough idea of whatuser interfaces will be in each release, we were in a position to startdefining the UX and the UI. Lets just consider the UX flow at themoment, and we’ll come back to look at development. Later on we’llgo through the two side-by-side to see the progression.
  138. 138. 3 stages of UX evolution 138We found that there were 3 stages of UX evolution in our project
  139. 139. STAGE 1 Idea storming 139Stage 1 - idea-storming
  140. 140. 140Firstly knowing what information should be displayed, the challengefor UX was to define the most effective way of communicating thatto the user. This stage involves cycling through many ideas, withmost likely to end up here:Image:
  141. 141. 141in the bin.Image:
  142. 142. 142and for one good reason - if you’re not dismissing options, thenyou’re not considering them all. The first answer might not be thebest one!Image:
  143. 143. how do you go through this with minimal friction?Image:
  144. 144. 144Start sketching ideas on paper...Image:
  145. 145. 145...or find a program to help you do it.Images:
  146. 146. STAGE 2 Prototyping 146Stage 2 - prototyping
  147. 147. 147Once a solution was identified as a good candidate for a particularscreen, our designers started developing a working prototype of theUI based on the interaction model identified from the previousstep...Image:
  148. 148. 148...and what tool do you use for the prototyping job? In ametaphorical world filled with nails, which hammer is the right one?This one?Image:
  149. 149. 149...this one?Image:
  150. 150. 150I doubt it’s this one.Image:
  151. 151. 151We found that the right toolset for prototyping was the one whichallows...Image:
  152. 152. 152...our UI/UX designer to do their job effectively. At the end of theday, its important to acknowledge that this is only a UI prototypeand it is intended to be junked after its developed. Even if it’s not inyour company’s core technology, this tool should be as frictionlessas possible for your UX team.
  153. 153. Our experience 153Just quickly - a little on our experience with prototypesWe started with SketchFlow. Our designer was brought in with theintention of creating a working prototype in SketchFlow. The toolitself works, and does a good job...
  154. 154. 154...Yay! Rainbows and sunshine, everyone’s happy...Image:
  155. 155. 155...except for our designer. What didn’t work, was that our designer isan experienced Flash developer, and he felt that his natural workpace was being held back because he wasnt experienced in the toolhe was using.Image:
  156. 156. 156He started doing the prototype in Flash, and was able to turn outchanges to a flash prototype inordinately faster than for SketchFlow,with a much higher level of quality, too.Image:
  157. 157. 157So the lesson learned was to let the team pick the right tool for thejob. Sounds obvious, but it’s an easy trap to fall into given yourorganisation’s situation.
  158. 158. STAGE 3 User testing 1583rd Stage of ux evolution - user testing
  159. 159. 159Given a working prototype, we were now in a position to test thisidea using our clinicians. We ran several rounds of UX testing, and infact we still continue to, so that we’re always refining the application- it goes back to the agile adage:
  160. 160. 160...continuous improvementImage:
  161. 161. ☑ Ease of use ☑ Makes sense ☑ Sketchy UI 161...and when testing these prototypes, we assessed each functionagainst a series of criteria, a few of the most important of whichwere
  162. 162. ☑ Ease of use ☑ Makes sense ☑ Sketchy UI 162First asessment - ease of use. Did the user understand what theywere to do on this screen? Were they able to find their way throughthe interface without requiring prompting? Was it intuitive?
  163. 163. 163Take this interface, as an example. This is an ATM in Japan.It’s far from being considered “easy to use”.
  164. 164. ☑ Ease of use ☑ Makes sense ☑ Sketchy UI 164Second assessment - does the solution make sense? Does thedesign help the user solve the problem they needed to.
  165. 165. 165...sounds obvious, doesnt it? but it’s easy to unintentionally design aUI in a manner which doesnt make sense for the information beingpresented...Image:
  166. 166. Example! 166Example?If i asked you to add a series of numbers on the screen, whichdesign makes it easier?
  167. 167. 23 53 77 127 343 232 443 39this? 167 2
  168. 168. 23 39 53 77 127 232 343 443 1337 168or this?
  169. 169. 169Again, it sounds like common sense, right? But the same UI mistakeskeep getting made over and over as we saw earlier.Image:
  170. 170. ☑ Ease of use ☑ Makes sense ☑ Sketchy UI 170and the third criteria for usability testing - did the UI specifically*lack* the right level of detail.I want to stress here the importance of user-testing againstincomplete-looking user interfaces. It’s widely recognised that whenyou present a person with a highly refined user-interface...
  171. 171. 171...they start getting bogged down in details, often unnecessary tothe problem at hand.
  172. 172. 172...sketchy or hand-drawn user interfaces separate the details of howa screen looks from the fundamentals of how a user intends tointeract with the system. It frees them to think about problems, andnot what shade of mauve a button is.Image:
  173. 173. Dev Evolution 173So we’ve seen what happens in a UX/agile process. Lets look at thedevelopment side of it and see how they fall into place
  174. 174. 174Development of any product usually involves a little plumbing andSDUF (what I coin “small design up-front”) to understand the featureand how it fits into the existing codebase. Just because its agile withTDD didn’t mean there was no we devs started working on some plumbing code or bits andpieces which were superfluous to the interaction experience of theuser. Why? Because completely changing the way a user interactswith a feature involves a lot of re-work...
  175. 175. which point the whole thing explodes in our faces.With UX, devs are best left to wait a little while until the maininteraction model has been defined, and THEN commence work onareas of the system closer to user interaction.Image:
  176. 176. 176Given a particular direction for a feature, the development teamstarted dipping our toes in the UI water, and invested a little timecreating the interface, but didn’t invest too much - we were makingsure our user can interact with the system, but we abstracted awayany *real* UI task until laterImage:
  177. 177. How? 177how did we do that?
  178. 178. 178We architected the solution with clear separation between the visualrepresentation of the UI and the underlying interaction model.Image:
  179. 179. 179In our world, we develop on top of Microsoft’s .NET platform,building our application using WPFImage:
  180. 180. Designers Markup Developers 180which allows developers and designers to work using tools fromtheir own worlds, but helps bring the two together by allowing themboth to speak a common markup-language to define the UI
  181. 181. MVVM Model - View - ViewModel 181...for the interaction model, we then have the Model-View-ViewModel design pattern. (Originally known as Martin Fowler’sPresentationModel pattern).Roughly, we know that MVVM allows us to separate the way that a UIlooks, and the way our user’s interact with the system. This is a verycommon design pattern in the .NET space...
  182. 182. BUT! 182...BUT! It’s not just limited to .NET.This separation pattern can be found in frameworks in a number ofother languages...
  183. 183. JGOODIES 183For example,Knockout in JavaScriptJGoodies in JavaMate in Flex/Flashjust to name a few.Images:
  184. 184. UI Implementation 184the next phase in the development process commenced once the UXteam had completed a large portion of their testing and haddesigned the screens...
  185. 185. 185...development started and a first-pass implementation of the UIwas built. It was low-fidelity, but started marking the applicationcoming aliveImages:
  186. 186. 186and lastly once all the decisions had been made, hi-fidelity assetswere rendered and integrated into the application...and thus we hadsuccessfully brought the best of agile and UX togetherImage:
  187. 187. Lets see it in action 187
  188. 188. What’s the problem? 188The problem i’m about to discuss is a task ofmaking a series of sounds have the same volume.*Split the frequency range of bass/deep sounds upto treble/high-pitch sounds into 8 bands*user uses volume adjustment to make each soundthe same
  189. 189. STAGE 1 UX Dev 189STAGE 1: < UX guys start working out what is the best wayto perform the task > Developers did what we do best - buildinginfrastructure to perform the necessary core task(ie: stimulation) (Getting developers to start thinking about UI atthis stage is guaranteed to result in lots ofunnecessary re-work which we know somethingevery developer *loves*)
  190. 190. STAGE 2 UX Dev 190STAGE 2: < UX works through another possibleimplementation. Sometimes throwing away entireideas and mockups > Devs are still keeping the world a safe place tolive
  191. 191. STAGE 3 UX Dev 191STAGE 3: < UX believes they have solidified a concept - 8bars. Actual design is still very fluid > There’s actually a lot of plumbing code tofacilitate electrocuting someone, believe it or not.
  192. 192. STAGE 4 UX Dev 192STAGE 4: < UX start refining the idea of 8 bars.Terminology also defined (“bands”). Control UXnutted out. All the pretty colours still to come, butthe workflow and core behaviour is worked out > Development took a cautious step - OK/Canceland a slider to control Volume. (Notice we picked low-risk, high impactfeatures early on. Final design wont affect the factthat these items will need to exist on this screenanyway)
  193. 193. STAGE 5 UX Dev 193STAGE 5: < UX have the idea worked out - now starting todetail how the controls will appear and interact withthe user > Devs start embracing the band idea andimplemented a single band version. Theoretically, ifyou get one band to work, then making 8 is alogical extension of the first. Not concerned aboutnailing the UX so early on. Goal is to deliver 80% ofthe UX upfront and refine over time
  194. 194. STAGE 6 UX Dev 194STAGE 6: < UX continue refining/prototyping usability andinteraction of the 8-band concept > Dev started working on the underlyingimplementation for 8-bands
  195. 195. STAGE 7 UX Dev 195STAGE 7: < UX now start looking at high fidelity designand testing. Working prototype becoming moreadvanced. At this stage, UX team are freeing upmore time to look at other parts of the system. > Dev pull together the most crummy lookinguser interface. As a bonus, it’s 100% functional andserves its purpose completely.
  196. 196. STAGE 8 UX Dev 196STAGE 8: < UX finalise high-fidelity design and tune basedon testing results. Assets are starting to get cut-upfor integration with development. By now, mainlyworking on another part of the system - comingback to assist with integration with app. > Dev start integrating hi-fi assets. Because theinteraction points have been defined upfront, thedevelopment task should mainly involve skinningcontrols.TRUTH: We forgot about some interaction pointslike stimulation indication - required re-work tounderlying mechanism.
  197. 197. STAGE 9 UX Dev 197STAGE 9: UX and development work closely (YES -PAIRING!) to finalise the screens to match as muchas possible given time constraints and other goalsrequired of the planned release. Incrementalimprovements will be made ongoing.
  198. 198. FINAL RESULT UX Dev 198...with our final result looking like this.Close (not exact) but close to the original design,with successive refinements planned in future.
  199. 199. 199So there you have it. That’s our story condensed into 45 minutes.
  200. 200. 200At this point we thought of providing a summary checklist of things to do when bringing UXinto Agile but...Image:
  201. 201. References: ๏ emerging_best_agile_ux_practice.html ๏ ๏ videos-that-are-worth-your-time/ ๏ ๏ ๏ 201there are several excellent web references and these are but a few and include some whichhave been a source of inspiration.We can conclude however that in our experience...
  202. 202. 202UX and Agile are very compatible and in fact...Image:
  203. 203. 203and actually bringing UX into Agile makes Agile fun and builds a new found respect for eachother’s disciplines.Image:
  204. 204. Thank youVictor Rodrigues Xerxes BattiwallaHead of Audiological Software Development Senior Software DeveloperCochlear Limited Cochlear LimitedEmail Email xbattiwalla@cochlear.comTwitter @jeunj Twitter @xerxesb We’ll post slides up on Slideshare after Brisbane conference using hashtags #yowoz & #cochlearux 204